Skip to content

Clarify manifest and runtime evidence boundary - #297

Merged
imran-siddique merged 2 commits into
mainfrom
agent/clarify-manifest-trace-boundary
Aug 13, 2026
Merged

Clarify manifest and runtime evidence boundary#297
imran-siddique merged 2 commits into
mainfrom
agent/clarify-manifest-trace-boundary

Conversation

@imran-siddique

Copy link
Copy Markdown
Member

What changed

  • Defines artifact 7 as the decision-log baseline captured at manifest issuance
  • States that later decisions are separate TRACE or OCSF evidence records
  • Documents the identity, key, and chain-continuity join between deploy-time and runtime evidence
  • Removes claims that a deploy-time manifest proves decisions produced later
  • Clarifies that a signed runtime record proves integrity, not completeness or behavioral correctness

Why

The previous overview blurred deployment identity with runtime evidence. That contradicted the boundary developed through CoSAI RFC #149 review: the manifest proves what was authorized to run; linked evidence records describe what happened afterward.

Validation

  • 95 focused binding and verification tests passed
  • Documentation build completed content generation but strict mode reported 12 pre-existing link/nav warnings unrelated to this change
  • Ran git diff --check

@imran-siddique
imran-siddique marked this pull request as ready for review August 12, 2026 23:05
@imran-siddique
imran-siddique merged commit 6a97a7c into main Aug 13, 2026
13 checks passed
@imran-siddique
imran-siddique deleted the agent/clarify-manifest-trace-boundary branch August 13, 2026 00:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant