Context
SocioProphet/socioprophet#498 tracks the overall KAIROS↔CHRONOS alignment thread. sociosphere/docs/integration/neurosymbolic-chronos-alignment.md's authority-plane table assigns AgentPlane the "Evidence/action/replay surface" role. Its "Definition of done" requires a downstream follow-on item here. This is that item.
What already exists in this repo
AgentPlane already runs a real evidence/replay pipeline that structurally matches the shape CHRONOS carriers would need:
docs/receipt-lifecycle.md — MAIPJ run receipts assembled from a normalized event stream (workspace.locked, context.pack.selected, policy.evaluated, placement.selected, run.started, run.completed, evidence.sealed), joined by trace_id, fail-closed if any required event is missing.
docs/replay-boundary.md — defines the current ReplayArtifact contract precisely, including what it does not promise yet (no cryptographic attestation, no full authority/delegation reconstruction, no complete version-set pinning).
docs/sociosphere-bridge.md — a narrow, already-implemented seam where sociosphere emits normalized workspace artifacts and a Bundle, and agentplane "consumes the bundle and preserves execution-plane evidence (ValidationArtifact, PlacementDecision, RunArtifact, ReplayArtifact)" — i.e. the exact "evidence/replay surface" role named in the alignment doc, already wired for the sociosphere/workspace case.
The concrete gap
None of evidence.sealed, ReplayArtifact, or the sociosphere-bridge artifacts currently carry a method-family tag or the neuro-symbolic carrier-boundary fields (grounding status, validation status, explanation trace reference, owning authority plane, non-authority declaration) that neurosymbolic-chronos-alignment.md requires on any carrier referencing neuro-symbolic reasoning. If a candidate governed carrier produced via, say, a NeurASP-style adjudication or a dILP-style rule proposal needs to flow through AgentPlane's evidence/replay surface the way a sociosphere Bundle does today, there's currently no analogous bridge doc or artifact shape for it — sociosphere-bridge.md is scoped to workspace/task artifacts, not neuro-symbolic carriers.
Ask
Look at whether the receipt/ReplayArtifact model (or a new bridge doc analogous to sociosphere-bridge.md) should be extended so a CHRONOS neuro-symbolic carrier's explanation-trace and replay-reference fields can pass through AgentPlane's evidence/replay surface, the same way sociosphere workspace evidence does today. This is a request to look at the connection, not a mandate for a specific artifact schema.
Non-goals
- AgentPlane does not take on carrier-schema or method-family taxonomy authority — that stays with Ontogenesis /
sourceos-spec.
- Per
docs/replay-boundary.md's own stated limits, this issue does not ask AgentPlane to promise cryptographic attestation or full authority reconstruction for neuro-symbolic carriers beyond what it already promises for any other replay input.
- No canonical-schema authority moves into
sociosphere.
Refs: SocioProphet/socioprophet#498, sociosphere/docs/integration/neurosymbolic-chronos-alignment.md, docs/receipt-lifecycle.md, docs/replay-boundary.md, docs/sociosphere-bridge.md (this repo).
Context
SocioProphet/socioprophet#498tracks the overall KAIROS↔CHRONOS alignment thread.sociosphere/docs/integration/neurosymbolic-chronos-alignment.md's authority-plane table assigns AgentPlane the "Evidence/action/replay surface" role. Its "Definition of done" requires a downstream follow-on item here. This is that item.What already exists in this repo
AgentPlane already runs a real evidence/replay pipeline that structurally matches the shape CHRONOS carriers would need:
docs/receipt-lifecycle.md— MAIPJ run receipts assembled from a normalized event stream (workspace.locked,context.pack.selected,policy.evaluated,placement.selected,run.started,run.completed,evidence.sealed), joined bytrace_id, fail-closed if any required event is missing.docs/replay-boundary.md— defines the currentReplayArtifactcontract precisely, including what it does not promise yet (no cryptographic attestation, no full authority/delegation reconstruction, no complete version-set pinning).docs/sociosphere-bridge.md— a narrow, already-implemented seam wheresociosphereemits normalized workspace artifacts and aBundle, andagentplane"consumes the bundle and preserves execution-plane evidence (ValidationArtifact,PlacementDecision,RunArtifact,ReplayArtifact)" — i.e. the exact "evidence/replay surface" role named in the alignment doc, already wired for the sociosphere/workspace case.The concrete gap
None of
evidence.sealed,ReplayArtifact, or the sociosphere-bridge artifacts currently carry a method-family tag or the neuro-symbolic carrier-boundary fields (grounding status, validation status, explanation trace reference, owning authority plane, non-authority declaration) thatneurosymbolic-chronos-alignment.mdrequires on any carrier referencing neuro-symbolic reasoning. If a candidate governed carrier produced via, say, a NeurASP-style adjudication or a dILP-style rule proposal needs to flow through AgentPlane's evidence/replay surface the way a sociosphereBundledoes today, there's currently no analogous bridge doc or artifact shape for it —sociosphere-bridge.mdis scoped to workspace/task artifacts, not neuro-symbolic carriers.Ask
Look at whether the receipt/
ReplayArtifactmodel (or a new bridge doc analogous tosociosphere-bridge.md) should be extended so a CHRONOS neuro-symbolic carrier's explanation-trace and replay-reference fields can pass through AgentPlane's evidence/replay surface, the same way sociosphere workspace evidence does today. This is a request to look at the connection, not a mandate for a specific artifact schema.Non-goals
sourceos-spec.docs/replay-boundary.md's own stated limits, this issue does not ask AgentPlane to promise cryptographic attestation or full authority reconstruction for neuro-symbolic carriers beyond what it already promises for any other replay input.sociosphere.Refs:
SocioProphet/socioprophet#498,sociosphere/docs/integration/neurosymbolic-chronos-alignment.md,docs/receipt-lifecycle.md,docs/replay-boundary.md,docs/sociosphere-bridge.md(this repo).