Projection bundles

What a projection bundle is

GARPedia renders public-safe projection bundles downstream of governance. A projection bundle is the read-only descriptor a downstream reader or agent consumes when they want to know what the public projection of an admitted record looks like: the record reference, the page-model reference, the projection and source/citation summaries, the custody, render, and operator owner triad, the public/private boundary, the readiness posture, and any receipt or export references.

The bundle is metadata about a projection, not the projection itself. It carries references and summaries, never the projected body and never the source text. It is downstream of the admission gate and the renderer authority list, the same way a rendered record page is, and it adds no path back into the record.

The custody, render, operator owner triad

A projection bundle names three accountable owners, in order, and treats them conjunctively. The bundle is public-safe only when the custody owner has admitted the material, the render owner has authorized the projection, and the operator owner has recorded the continuation decision — in that order. A bundle missing any one is blocked, not partially rendered.

• custody ownerowns the record and its admission. The bundle reports that the material is fit to exist in the pool; it does not perform admission.
• render ownerowns the projection and the renderer authority list. The bundle reports whether projection is authorized; it can record a hold even when the record is admitted.
• operator ownerowns the moderation and continuation loop. The bundle reports whether a publication decision was recorded; it never makes one.

Eligible and blocked, on the read surface

Two synthetic fixtures back the read-only surface at /projection-bundles. They are fictional: no real Counterpose signal id, title, slug, publisher, source name, or signal text appears in either, and no absolute or private operator path is referenced.

• eligibleSYN-PB-RW-0001 projects the synthetic reverse-wiki record at SYN-REC-RW-0001. Every owner has acted in order and the public boundary is confirmed, so it is safe for the public renderer and carries page-model, export, and receipt references.
• blockedSYN-PB-HELD-0001 describes a synthetic Counterpose-shaped record held back from the renderer authority list. The custody owner has acted, but the render owner has not authorized projection and the operator owner has not recorded a publication decision, so the bundle carries a renderer_authority_hold blocker. It remains inspectable here precisely so the surface stays honest about what the hold refuses; it never produces a rendered record page.

What this page does not claim

This is an explainer for a read-only model, not a shipped publication capability. The following are explicitly not claimed and must not be inferred from it.

• This page does not approve, admit, mutate, or publish records. It renders synthetic projection bundle metadata and changes no admission state and no renderer authority list.
• Private source text and private operator paths are excluded. The bundle carries summary counts and references only, never the projected body, the source text, or a private path.
• CP-SIG renderer authority holds remain holds unless separately lifted by governance. The blocked fixture demonstrates the hold with a synthetic stand-in and does not weaken or revisit it.
• No backend wiring. The fixtures are in-repository TypeScript modules; the surface does not fetch, call a backend, run an import, or implement an upstream substrate.
• No receipt or verification claim. Referencing a receipt makes no issued, verified, or cryptographically validated claim.

• Back to /method
• Continue to the reverse-wiki owner triad
• Open the read-only projection bundle registry