Manifesto
Context is infrastructure
Six principles · the reasoning behind every line of the spec
Software ate the world; agents are eating software. Yet every agent session still starts from zero, relearning what yesterday's session already knew. The cost shows up as tokens, hours and wrong turns — and you pay it again every single morning.
We standardized how agents call tools. We standardized how they receive instructions. We never standardized the thing that makes them effective: what they know. CTXPKG exists to close that gap.
Context is infrastructure
Knowledge about a system is as load-bearing as the system itself. It deserves versioning, review, signing, dependency resolution and an owner — the same rigor we learned to give code.
Knowledge must outlive the session
An insight discovered once should never need rediscovery. Every context window that closes without exporting what it learned is an asset written off at 100% loss.
Trust is not optional
What an agent knows shapes what it builds. Knowledge nobody can verify is a way to smuggle in instructions — so every package must prove it is genuine and untouched before a single line is loaded.
Portability over lock-in
Knowledge captured in one tool must be loadable in the next one. A format owned by one vendor is a product; a format anyone can implement, with governance shared among implementers, is infrastructure.
Composability is the multiplier
One package helps one project. Packages that combine cleanly and predictably — disagreements shown, never swallowed — compound into something larger: an economy of trustworthy knowledge.
Creators own their context
A package is a file. Keep it private, share it with your team, sell it, or publish it to the world — the choice belongs to whoever distilled it, not to a platform.
The endgame
Success looks unremarkable: "ships as .ctxpkg" appearing in third-party READMEs the way "npm install" does. Framework maintainers publishing official context alongside official docs. Teams onboarding agents the way they onboard engineers — with a curated, signed body of knowledge instead of a cold start. A market where distilling expertise is paid work.
The standard is open, the registry protocol is open, the reference implementation is shipping. Read the spec, implement a level, and help make context the last layer of the agent stack to be standardized — properly.