Developers
Give developers a dedicated Ghost surface for protocols, public APIs, manifests, and attestation-aware integration guidance.
Spotlight
Ghost already exposes rich discovery and protocol artifacts; the missing piece is a polished public developer experience that explains how to use them.
Constitutional commitments
Who this surface is for
Need a proof-native protocol surface that can be integrated without sacrificing explainability or bounded authority.
Need to understand manifests, endpoints, and trust semantics before choosing how Ghost fits into a larger system.
Need a public technical destination that makes Ghost legible to builders without repo archaeology.
What a pilot produces
A concrete pilot document covering which protocol surfaces, manifests, and APIs the team will use first.
An agreed build sequence for integrating Ghost while preserving attestation, evidence, and governance boundaries.
A pilot-ready collection of contracts, examples, and verification expectations tailored to the selected integration path.
Signature operating module
This visual module gives the surface its own product-specific logic and rhythm instead of reusing a single generalized storytelling block.
Protocol discovery grid
Indexed by GET /api/public/protocols. Follow links to live HTTP surfaces and published manifests.
Discovery manifests
Developer path
Read manifests and public contracts to understand what Ghost exposes.
Map proof, protocol, and runtime boundaries before integrating.
Choose the right surface, stream events, and preserve attestation context.
Operating surface
Three lanes — boundaries, proof, control — per surface.
These sections translate Ghost's constitutional operating model into a specific surface with clear boundaries, visible proof, and institutional-grade control.
Bring protocols, manifests, public APIs, and proof-aware integration guidance into one human-readable surface.
Show developers how Ghost already exposes protocol and public endpoint surfaces without making them reverse-engineer the repo.
Position Ghost for teams who want AI systems that are explainable, bounded, and protocol-complete from day one.
Protocol-native build path
This surface is not just another page in the Ghost IA. It has a different operating rhythm, a different set of lenses, and a different scenario shape inside the constitutional system.
Developers should be able to move from `agent.json` and `llms.txt` into real protocol understanding without reverse-engineering the repo.
Ghost's public APIs and protocol endpoints become easier to trust when they are documented as an opinionated operating model, not just endpoints.
The developer story should teach how to build with attestation and governance from the start, not after the prototype ships.
Scenario rail
An engineering team discovers Ghost, inspects the available contracts, and connects to the platform without losing the proof story.
Discover Ghost through public manifests, protocol pages, and search surfaces.
Inspect MCP, A2A, OASF, AG-UI, and public API capabilities with human-readable context.
Integrate against the right protocol surface while preserving trust, evidence, and operating boundaries.
Program focus
These are the sovereign programs most responsible for how this flagship surface behaves in production.
Translate institutional law into machine-operable constitutional rules with simulation-gated activation and sealed version history.
Replace simple authentication with standing, scope, evidence obligation, and revocation paths for every machine and human actor.
Run constitutional foresight through institutional digital twins before risky law, memory, delegation, or emergency changes go live.
Doctrine emphasis
Related surfaces
Cross-link enterprise, command, trust, and developer journeys.
These destinations connect this surface back into the wider Ghost operating model so the site stays coherent across enterprise, command, trust, and developer journeys.