Runtime Projection and Readback
Use this page when you need to understand how Helpifyr publishes projected runtime state, what readback must confirm, and why projection never replaces owner-owned runtime materialization.
What this concept means
- projections make shared state readable without moving runtime ownership away from the owner repo or runtime lane
- readback proves whether the projected view still matches the real materialized surface
- missing, stale, or partial projection should fail closed rather than being treated as good enough
- a green-looking summary is still only a claim until the required readback path says otherwise
Why it exists in the Helpifyr stack
Helpifyr relies on projections so operators, agents, and docs consumers can read consistent state across repos and runtime lanes. That is useful only if the projection keeps its owner, source revision, and readback posture explicit.
The stack therefore separates publication from verification: Fabric can project, but readback must still prove that runtime and reviewed artifact truth agree.
What it is not
- not runtime mutation ownership
- not a shortcut around live readback
- not permission to claim deployment or auth success from projection visibility alone
Core objects and boundaries
Projection
A projection is a typed, readable representation of current state or contract posture. It exists to be consumed safely by operators and downstream systems.
Readback
Readback is the check that compares projection and reviewed artifact truth against the actually materialized runtime or published surface.
Source revision and field ownership
When multiple systems participate, the projection still needs source revision, field-owner, and sync-conflict evidence so readers know which part is authoritative and which part still needs followthrough.
Relationship to other concepts
- Platform Truth explains where shared contracts and projections are published.
- Validation and Readback Workflow explains the operational verification order.
- Mission Control and Operator Context explains how human-facing shells consume projections without becoming owners.
Source truth and evidence
helpifyr-fabric/docs/contracts/HELPIFYR_AGENT_BOOTSTRAP_TRUTH_LAYER.mdhelpifyr-fabric/contracts/acp/tool_execution_evidence_v1.jsonhelpifyr-fabric/contracts/work_operating_model/work_sync_truth_contract_v1.jsonhelpifyr-fabric/docs/contracts/HELPIFYR_PLATFORM_VERSION_TRUTH.md