docs: propose embodied action evidence profile#339
Conversation
|
Ready for review. This is docs-only and scoped to evidence semantics for the Embodied Action Evidence Profile. It does not change the audit schema or runtime behavior, and it does not claim physical completion, controller safety, or functional-safety certification. Current validation:
Note: I attempted |
|
Updated the profile to align explicitly with The new section clarifies that, for embodied AI, required action receipts mean offline-verifiable evidence for externally consequential action handoffs below the session-level TRACE Claim. It also keeps the boundary explicit: a valid receipt is not proof of physical completion, controller safety, or functional-safety certification. Added verifier guidance for:
Local validation:
|
Welcome to Codecov 🎉Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests. ℹ️ You can also turn on project coverage checks and project coverage reporting on Pull Request comment Thanks for integrating Codecov - We've got you covered ☂️ |
Summary
Refs #337.
Adds a draft v0.1 Embodied Action Evidence Profile for physical-action traces. The profile is intentionally docs-only in this first PR: it defines a producer/verifier convention on top of the existing
external_execution_evidenceenvelope without changing the audit schema or runtime behavior.What changed
docs/spec/embodied-action-evidence.mdwith a concrete profile for embodied-action evidence.external_execution_evidenceenvelope, and detached embodied-action payload.linked_call_idbound to the cMCP audit entrycall_idand separates it from controller-nativeaction_refvalues.action_refcomputation, receipt state classifications, Agent Manifest identity comparisons, verifier flow, and explicit non-goals.Validation
git diff --checkdocs/spec/embodied-action-evidence.mduv run --with-requirements requirements-docs.txt mkdocs build --strict, but the current repo MkDocs config fails before page rendering becausedocs_dir: .is rejected by current MkDocs as the parent directory of the config file. This appears unrelated to this PR.Notes for review
This PR does not claim physical completion, controller safety, or functional-safety certification. It only scopes the evidence semantics needed to bind a physical-action request, governance decision, controller handoff, and optional downstream receipt into the existing cMCP audit model.