docs: clarify industrial evidence continuity - #18
Merged
imran-siddique merged 1 commit intoJun 12, 2026
Merged
Conversation
Signed-off-by: Carlos Hernandez <carloshvp@gmail.com>
imran-siddique
approved these changes
Jun 12, 2026
imran-siddique
left a comment
imran-siddique
left a comment
Member
There was a problem hiding this comment.
Accurate throughout: the diagram correction is right (the current preview loads policy/catalog directly and does not ingest the Agent Manifest -- offline hash comparison is the honest representation), the evidence-continuity claim matches what cmcp verify actually proves offline, and the trust-chain table is careful about what the preview does not yet bind. Thanks for keeping the example honest as it evolves.
imran-siddique
added a commit
that referenced
this pull request
Jun 12, 2026
PRs #11, #13, and #14 were stacked on #10. When #10 squash-merged and its branch was deleted, GitHub closed/merged the rest of the stack into the deleted feature branches, so their content never reached main: financial and healthcare shipped the unparseable advice{} Cedar policies, agents called endpoints that do not exist, the mock servers and the cmcp verify tamper demo were missing. This restores the verified stack tip for the four original examples plus .gitignore, with em dashes scrubbed per repo style, and merges the root README: corrected table and 3-terminal quickstart from the stack, plus the industrial-embodied-ai row with the #18 wording. Verified before commit: all Cedar bundles parse and produce the documented decisions (workflow-scoped allow, escalation/HITL deny, default deny), and all catalog entries validate against the cmcp schema. Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Clarifies the lifecycle and evidence boundaries of the merged industrial embodied-AI example.
Why
The example supports the broader AgentTrust framing that permission alone is insufficient and governance evidence must survive beyond a single agent process. The wording also needs to remain precise about the current developer-preview implementation: policy and catalog hashes are compared offline, but the Manifest identity is not yet cryptographically bound to the runtime session, and controller responses are not yet hashed into the TRACE audit record.
Validation
python validate_artifacts.pypython -m unittest discover -s tests -v(7 passed)cmcp verifyagainst the committed TRACE claim and signed audit bundle with pinned policy and catalog hashesgit diff --checkThe committed fixture remains intentionally software-only and does not claim hardware provenance.