Alloy First Steerable Arc

Timeline

1. 1

   Contract

   Turn-boundary steering chosen

   Each direction became a separate Execution under one Arc-scoped provider session.

2. 2

   Control

   Durable authority added

   Arc fences, lineage, idempotency, runner leases, attempts, and terminal arbitration moved control into Neon.

3. 3

   Forge

   Operator conduct became real

   Forge exposed state-derived follow-up, cancellation, history, interruption, and recovery controls.

4. 4

   Hostile proof

   Browser-to-provider acceptance passed

   Refresh, stale tabs, double submission, cancellation, runner loss, and recovery were exercised against one live Arc.

5. 5

   Close

   Crucible passed Milestone 2

   The final review found no blocking contradiction and authorized milestone closure.

What shipped

• products/alloy/runner/providers/claude-cli.ts now supports explicit opaque-session resume and verified process-tree cancellation.

• products/alloy/lib/db/schema.ts and products/alloy/lib/db/queries.ts provide durable Arc conduct fences, provider bindings, commands, attempts, leases, lineage, and terminal arbitration.

• products/alloy/runner/index.ts claims target-scoped commands under generation/token fencing and streams attempt-owned evidence while retaining cancellation control.

• products/alloy/components/LiveArcPanel.tsx and products/alloy/app/forge/page.tsx expose truthful state-derived conduct, execution history, stale-tab errors, and explicit recovery.

• products/alloy/scripts/prove-runner-control.ts, products/alloy/scripts/prove-runner-lease-arbitration.ts, products/alloy/scripts/prove-real-runner-conduct.ts, and products/alloy/scripts/prove-forge-conduct.ts preserve hostile-path proofs.

• products/alloy/docs/milestone-2-browser-acceptance.md records the authenticated five-turn acceptance Arc and final Crucible PASS.