Starlight Intelligence Protocol (SIP v1.1.1) Spec
Open Specification for Portable Agent Instructions, Vaults, and Receipts
Vendor-neutral file contracts for AGENTS.md, append-only memory vaults, loop budgets, and build attestations.
Operational scope
Keep your agent constitutions, skills, and memory portable across Claude, Codex, Gemini, and local open-weight runtimes.
Key outcomes
- Adopt a single AGENTS.md and repo-profile contract readable across multiple CLI coding harnesses
- Structure portable JSONL memory logs with provenance hashes and privacy-tag boundaries
- Emit machine-verifiable run receipts recording scope, test exit codes, and human approval gates
Included modules
- 01
Layer 1 · File & Repo Contracts
Standard layout for AGENTS.md, .agent-harness.json, and deterministic skill metadata.
- 02
Layer 2 · Memory & Vault Schema
Event-sourced JSONL record format with confidence decay and contradiction links.
- 03
Layer 3 · Loop Budgets & Receipts
Contract format for maker-verifier loops, spend fail-safes, and terminal verification receipts.
Coming soon
Join the waitlist
Inspect the file tree below now, and join the waitlist to get a note when delivery opens.
Join the waitlistInspect 4 package files ↓Planned scope preview
Planned module outline (illustrative preview)
This item is on the launch list and does not have a downloadable file archive yet. Entries below summarize the planned module scope under review.
Illustrative scope summary for Starlight Intelligence Protocol (SIP v1.1.1) Spec. Downloadable package files are not published yet; join the launch list for release updates.
1Planned product: Starlight Intelligence Protocol (SIP v1.1.1) Spec2Release state: Waitlist preview (not yet packaged for download or checkout)3Waitlist route: /waitlist?intent=starlight-spec45Keep your agent constitutions, skills, and memory portable across Claude, Codex, Gemini, and local open-weight runtimes.67Target outcomes under review:8- Adopt a single AGENTS.md and repo-profile contract readable across multiple CLI coding harnesses9- Structure portable JSONL memory logs with provenance hashes and privacy-tag boundaries10- Emit machine-verifiable run receipts recording scope, test exit codes, and human approval gates- You work in Git, Markdown, and CLI agent tools and want portable, inspectable configurations.
- You value explicit verification gates and clear file boundaries over black-box automation.
- You want a hosted no-code SaaS subscription rather than local workflow specifications.
- You need an immediately downloadable archive today rather than joining the launch list.
Questions and scope notes
Does adopting SIP lock me into a hosted service?
No. SIP is a plain-file convention built on Markdown, JSON, and Git so your repository remains sovereign.