/getting-started/projectionPlanned

Public projection

Which data classes can ever be public, how the approved-projection pipeline decides what ships, and how projections stay fresh.

Contract unavailable

This docs section is listed in the spine so readers can see the planned boundary, but it is not a published integration contract yet. Do not build against this page as a complete API, MCP, auth, mirror, no-leak, projection, or route-boundary reference.

The projection gates run in the product today; the public contract page describing them is not started.

The section is scoped for the spine and the behavior it describes is live in the product, but no public doc content exists yet.

Expected coverage

Listed for orientation only until the contract is reviewed and versioned.

Public data classes
Approved-projection pipeline
Freshness + staleness labels
Revocation propagation

Actions stay gated

Reading docs is public. Issuing keys and managing a twinlet stays in Studio.

Open access keys

If you are signed out or lack permission, the product route will show the supported access state. Docs never display or manage key values.

What lives where

The ownership boundary this docs site depends on. If a fact is on the wrong surface, it drifts: docs hold contracts, the homepage holds the product story, Studio holds the creator's private workspace copy.

Docs

/getting-started · publicDevelopers and agent builders

Technical contracts and integration facts.

Owns

Projection, auth, API, and MCP contracts
Mirror and discovery file contracts
The public no-leak statement
Route classes and 403 semantics
Versioned changelog for all of the above

Never hosts

Marketing hero or product story copy
Join-the-beta and onboarding flows
Key issuance UI or key values
Creator workspace copy from Studio

Homepage

/ · creator-gatedInvited creators

The product story and Join-the-beta.

Owns

Creator value proposition
Product story and demo framing
Join-the-beta call to action

Never hosts

Endpoint tables or rate limits
Key scoping and issuance rules
Integration contracts of any kind

Studio

/studio · signed-in creatorThe creator-owner of a twinlet

The creator's private workspace copy.

Owns

Source, readiness, and publishing states
Key issuance, scoping, and revocation UI
Private per-twinlet guidance and copy

Never hosts

Public contract text (docs link in, never copy)
Public marketing copy

Routing rule: a sentence that promises behavior to an integrator lives in Docs. A sentence that sells the product lives on the Homepage. A sentence that operates one creator's twinlet lives in Studio. Docs link to Studio for actions like key issuance — they never duplicate its copy.