Goal
Design a mock robotics/device scenario that demonstrates CaPU's commit-before-effect invariant.
Context
A future CaPU device/robotics path needs simple demos that show why CaPU is different from an ordinary policy check.
Example scenario:
robot arm movement request
-> causal record
-> Gate checks permission/safety context
-> Incubate waits for sensor confirmation
-> Commit records authorization
-> Execute allows actuator motion
Suggested work
Start with documentation and testable pseudo-flow before implementing real robotics integration.
Suggested file:
docs/examples/robot_arm_commit_before_effect.md
Acceptance criteria
- Describe one concrete mock actuator scenario.
- Include at least one allowed path and one blocked path.
- Show where Gate, Incubate, Commit, and Execute happen.
- Explicitly show no actuator effect before commit_ok.
- Do not claim production robotics safety.
Contributor level
Intermediate / robotics or safety scenario design.
Why this helps community
This gives robotics-minded contributors a concrete narrative and future test target for CaPU's causal co-processor vision.
Goal
Design a mock robotics/device scenario that demonstrates CaPU's commit-before-effect invariant.
Context
A future CaPU device/robotics path needs simple demos that show why CaPU is different from an ordinary policy check.
Example scenario:
Suggested work
Start with documentation and testable pseudo-flow before implementing real robotics integration.
Suggested file:
Acceptance criteria
Contributor level
Intermediate / robotics or safety scenario design.
Why this helps community
This gives robotics-minded contributors a concrete narrative and future test target for CaPU's causal co-processor vision.