Build, prove, publish

Turn successful work into
reusable capability

Start without a domain package, keep the successful evidence path, distill bounded candidates, and publish only what survives replay and shadow evaluation.

One path from exploration to Release

  1. Run real CasesAn Agent explores only inside the current Case boundary. Successful terminal receipts and effective proof paths become private Episodes.
  2. Distill CandidatesCandidate Vocabulary, Rules, and board-local Actions are generated from eligible Episodes without becoming installable.
  3. Replay and shadowCounterexamples must remain green under deterministic replay. Shadow evaluation runs against a detached Case snapshot and cannot mutate customer state.
  4. Open a private DraftA current Shadow report can become an ordinary private Draft for human editing. It is still unpublished and cannot affect an Agent.
  5. Review and publishA human chooses the final Capability or Constitution content. Publishing separately creates an immutable Release under a durable Publisher identity.

User and Publisher stay separate

Developer

The signed-in persona that drafts packages, inspects Candidates, and acts through Publisher membership.

Publisher

The durable namespace that owns Releases, Offers, team roles, statements, and any future payout destination. It grants no access to customer Agents or data.

Create a Publisher identity

Public beta publication and zero-rated usage records are available before payments activate.

Open DeveloperRead the Capability reference