Expand description
The workspace realizer (PSP-9 system 10, Paper I Definition 12.2).
The gate is evaluated on the candidate workspace that would actually be
checkpointed, never on the model’s account of it. WorkspaceState is a
cheap content-addressed handle — hashes and identifiers, never file
contents — because the kernel clones every attempt into its trace.
The kernel’s srbn::Realizer is synchronous, while Perspt’s
realization re-reads an overlay on a tokio runtime. The split is
deliberate: snapshot_workspace does the I/O first, and
SnapshotRealizer is a pure sync adapter over already-materialized
snapshots, used by the stabilize_realized conformance oracle. The live
tool loop calls snapshot_workspace directly at its measure boundary.
Coding claims no numeric ‖r_k‖: the fraction of denied or rewritten
edits is ProjectionMismatch telemetry, recorded but never summed into
V and never labeled a realizability residual.
Structs§
- Projection
Mismatch - Projection telemetry (PSP-9 system 10): denied, stale, ambiguous, or
normalized edits. Operational telemetry about the projection — not
Paper I’s
‖r_k‖, which requires a proxy geometry coding does not have. - Snapshot
Realizer - Sync adapter over pre-materialized snapshots for the kernel’s
stabilize_realizedconformance oracle. Coding realization is unmeasured: the structural Definition 12.2 property holds (the barrier sees the realized state), but no numeric residual is claimed. - Workspace
State - Content-addressed view of the files a node generation touched.
Functions§
- snapshot_
workspace - Re-read the named paths from the overlay root and hash what is actually on disk. This is the realization boundary: whatever the model claims, measurement runs against this snapshot.