Open registry · free public packs
Specs your coding agent can build from. And proof that it did.
A spec pack holds the decisions a builder could not guess, each with a check. Point any coding agent at one, build in any stack, and attest the result with signed, re-checkable evidence.
# fetch the spec, checked against its digest $ symbolon pull kausalflow/lightkone # hand it to Claude Code, Codex, Cursor… $ claude "build what packs/lightkone specifies" # run the pack's checks and sign the result $ symbolon attest contract/ impl/ ✓ PASSED · attestation.json signed
Pull a pack
A brief, the obligations a build must meet, the assumptions it rests on, and the examples and property tests that pin each one down.
Build in any stack
The pack is the source of truth, not the code. Your agent reads pack.md, writes the implementation in whatever language you use, and flags gaps instead of guessing.
Attest the build
symbolon attest runs every check in a sandbox and signs the result. Anyone can re-verify it, and passing builds show up as evidence on the pack.
Packs
Ranked by independent evidence: components with a passing build, then builds, then runners.
Lightkone core: search, BibTeX, keys, filing, merge, tidy and the library file
symbolon pack init, write down the decisions, release. Built for agents to read
Every page has a plain-text twin. Start an agent at llms.txt and it can find, read and pull any pack without scraping HTML.