CAS-Native Agent Work Order

Purpose

Make exact inputs, authority leases, dependency graphs, proposed patches, evidence, conflict, receipt, replay, and rollback concrete.

Mechanism

A Work Order references immutable input objects and a scoped lease. A worker returns exact artifacts and a patch. The coordinator detects dependency drift, validates evidence, and separates completion, verification, and acceptance.

Deterministic fixture

A repository documentation task with two exact input files, one policy dependency, a lease expiry, a concurrent edit, and a test artifact.

The fixture must live in content/demos/d07-cas-native-work-order/fixture.json, validate before the demo renders, and be resettable without a network call. A future live adapter may be added behind a visibly separate mode.

Required controls

• Open Work Order
• Inspect exact inputs
• Expire lease
• Run worker fixture
• Inject concurrent edit
• Verify Return
• Accept/revise/reject
• Replay
• Rollback

Visible states

• DRAFT
• AUTHORIZED
• RUNNING
• RETURNED
• CONFLICT
• VERIFIED
• ACCEPTED
• REJECTED
• ROLLED_BACK

Every state must have text, iconography, and a non-color-only distinction. State transitions are logged in an in-memory demo receipt visible in the inspector.

Core assertions

1. Worker sees only scoped inputs.
2. Dependency drift creates conflict instead of silent overwrite.
3. Return is not Verification; Verification is not Acceptance.
4. Replay resolves the same accepted head from exact records.

Layout

The page contains:

1. a concise mechanism explanation;
2. the interactive stage;
3. a state and evidence inspector;
4. a reset control;
5. a “what this proves / what it does not prove” panel;
6. links to the related paper and benchmark contract.

On narrow screens the inspector becomes a bottom sheet. The stage must remain usable at 360 CSS pixels.

Accessibility

• All operations are keyboard reachable.
• Pointer gestures have button or keyboard equivalents.
• Animated transitions honor prefers-reduced-motion.
• Focus remains visible and returns predictably after sheets close.
• Diagrams expose concise text alternatives.
• Status is announced through a polite live region only when the user initiates the transition.

Instrumentation

Record locally:

demo_id
fixture_version
action
prior_state
result_state
validation_result
timestamp_relative

Do not send telemetry. Provide “Export demo trace” as JSON for debugging and reproducibility.

Automated tests

• fixture schema validation;
• deterministic reset;
• every required control transition;
• every assertion above;
• invalid and stale fixture handling;
• keyboard path;
• 360 px and 1440 px screenshots;
• zero critical console errors;
• no request to a paid API in default mode.

Publication boundary

The demo uses a local deterministic worker fixture and performs no real external write.

The interface must never convert illustrative values into a benchmark claim. A measured result appears only when linked to a versioned run receipt.