/method/projection-readiness

Projection readiness

What projection readiness reports

Projection readiness is the reverse-wiki function that reports whether a projection path is ready, blocked, held, unavailable, or not_authorized for public projection, with a separate malformed diagnostic posture reserved for an untrusted response or descriptor. It is a reporting posture over the path an admitted record would travel from custody, into a Workbench-side review surface, and out to a public projection surface.

The function is intentionally narrow: it names a state, it names the stable blocker code when a precondition has not been met, and it stops there. The public explanation surface — this page — describes the grammar; it does not render a live readiness state, and it does not stand in for the upstream read model or the operator cockpit.

Posture: what readiness is and is not

Readiness is a reporting posture only. The following non-claims are durable: they hold whether the inventory row is partial, live, or deprecated, and they hold on every surface that renders readiness.

Projection readiness is not admission.
Projection readiness does not verify model output.
Projection readiness does not mutate public admission state.
Projection readiness does not lift renderer authority.
Projection readiness does not authorize publication by itself.
A GARPedia page is not the source of truth.

The readiness states

Five reporting states cover the eligible-to-render question, and one diagnostic posture covers the case where the response or descriptor itself cannot be trusted. The states are deliberately distinct so the absence of ready cannot be silently re-read as anything other than what the function says.

readyThe backend read model and the operator surface both report no blocker for the projection path. ready is an eligibility report; it is still not admission, and it does not authorize publication by itself.
blockedA value-free, stable blocker code names a precondition that has not been met. blocked is a precise non-ready signal: it says which named precondition is outstanding without leaking any private payload or operator path.
heldA render-owner governance hold remains in force on the projection path. The path is not eligible until the hold is resolved upstream by the render owner; the public surface never lifts the hold.
unavailableThe read model or the projection path itself cannot be evaluated honestly — there is no admitted record, no Workbench-side review action, or no public surface through which the path could render. unavailable is reported, not silently coerced into ready.
not_authorizedThe viewer or operator is not authorized for the underlying read model. not_authorized is a posture about the reader of the read model, not a claim about the underlying material; the public surface does not infer admission state from it.
malformedDiagnostic posture in the unavailable class for an untrusted response or descriptor. malformed signals that the substrate response cannot be parsed or trusted as a readiness report; it is never rendered as ready and never collapsed into another state.

Stable blocker vocabulary

When the reported state is blocked, a value-free blocker code names the precondition that has not been met. The closed vocabulary on the public-facing inventory row today includes, but is not limited to, the following codes. Each is a descriptor; none reveals a private payload, source path, or operator action.

synthetic_fixtures_only — the projection path on the public surface reports against synthetic projection-bundle fixtures rather than a live read model.
garp_local_read_model_unstable_or_absent — no documented, versioned, read-only projection-readiness read model exists upstream yet, or the one that exists is still in flux.
workbench_cockpit_absent_or_fixture_only — the Workbench-side cockpit either does not exist yet or renders only synthetic fixtures with no fixture-vs-live distinction.
public_explanation_missing_or_overclaims — the public-facing method/projection explanation is missing, or it exists but claims admission, renderer authority, or model verification.

After the upstream garp-local read-model substrate and the garp-workbench cockpit landed, the remaining inventory blocker on the projection_readiness row is public_explanation_missing_or_overclaims. This page is the public explanation; the inventory row stays partial until that blocker is separately reconciled in its own PR, alongside any boundary-and-overclaim audit a future flip PR must record.

Ownership: who owns what

Projection readiness has a three-way owner split. Each owner renders a different surface of the same posture; no owner subsumes another, and the public-facing surface in this repo does not stand in for the substrate or the cockpit.

garp-local owns the read-model substrate. It publishes the read-only shape over which the readiness states are computed deterministically. There is no write path; readiness does not mutate the admitted pool.
garp-workbench owns operator rendering and cockpit display. The cockpit visualizes readiness over a projection path for the operator and distinguishes fixture data from live read-model data so no reader mistakes one for the other.
garpedia_org owns the public explanation and the projection grammar. This surface explains what readiness reports, names the states and the blocker vocabulary, and pins the durable non-claims in plain view.
Public GARPedia explains the posture; it does not mutate the posture. The page describes the function; it is not the substrate, not the cockpit, and not the operator surface.

Public-safety boundary

The page is public-safe by construction: it describes a reporting posture, names a closed vocabulary, and excludes the private operator path. The following are explicitly excluded from this page and from the public projection.

No live readiness state is rendered on this surface. The page describes the grammar; the cockpit and the read model render state.
No admitted fixture is introduced by this page. The admitted pool manifest is unchanged, the renderer authority list is unchanged, and the CP-SIG renderer-authority hold stands in full.
No public write, admission control, or moderation surface is added or implied. The Workbench remains the operator surface; GARPedia remains a public read surface.
No FSI determination, compliance determination, or legal determination is made by this page. Readiness is a reporting posture; it does not adjudicate.
Private prompts, private source text, tool arguments, transcripts, raw model output, and private operator paths are excluded. None of these appear on this page or on any GARPedia public projection.
A GARPedia page is not the source of truth. The page renders the explanation; the substrate lives upstream in garp-local, with operator visualization in garp-workbench.