From 0d05c771106ef5712c5045f6fa4a97993d4a61a1 Mon Sep 17 00:00:00 2001 From: sammiller Date: Fri, 25 Sep 2026 16:13:56 +0800 Subject: [PATCH] [P2-018] Re-pin the delivery model to the repaired claim and handoff rules Point the P2-018 section at Design-B f8dff2d (ArcForges-Design-B#3) and the Plan execution entry at Plan-B ec88207 (Plan-B#3), which replace the earlier prompt revision. Describe the Windows-safe claim and branch keys (claims/, task/), resumption from the claim's handoff record, and merges by the integration role holder at the reviewed head commit with the task IDs kept in the merge title. Documentation only; no source, dependency, package or workflow change. Co-Authored-By: Claude Opus 5.5 --- AGENTS.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 1d818a8..7142df9 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -15,11 +15,11 @@ ## Delivery model (P2-018) -Work is scheduled as delivery tasks in the [delivery graph](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/README.md) and executed through the [Plan execution entry](https://github.com/ArcForges/Plan-B/blob/0cb637d1bfbf64d7db22a96a2b7370a409a25d8e/arcforges-implementation.md). There is no Current task, numbered substep order or single main context. +Work is scheduled as delivery tasks in the [delivery graph](https://github.com/ArcForges/ArcForges-Design-B/blob/f8dff2d0144c7db020d35711d606334639dd078b/docs/planning/delivery/README.md) and executed through the [Plan execution entry](https://github.com/ArcForges/Plan-B/blob/ec8820732486464e92df89788edb89eafac86afb/arcforges-implementation.md). There is no Current task, numbered substep order or single main context. -- Baseline: The accepted bootstrap is the Native AOT application with the WP02 build identity, dependency and provenance baselines; there is no product domain code yet. Every ArcScope capability is an open task. This repository's tasks are in the [arcscope](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/lanes/arcscope.md), [simulator](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/lanes/simulator.md) lanes and parts of the governance, release and runtime-proof lanes. -- Start only a task that Plan-B's `python tools/delivery.py ready --claims` lists and whose `claims/` branch you hold. A task here becomes ready only after the adoption slice for its lane (`ADOPT.05.`) is recorded. -- Several workers may work here at once, each on a different claimed task in its own retained worktree and `task/` branch, inside the task's write scope. Acquisition, visualisation, analysis, reporting and portability tasks work in their own modules against the one acquisition owner, so they proceed in parallel. -- Shared files follow their [declared protocols](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/shared-resources.md): solution and project lists, central package versions and CI job lists are appended by the task that adds a project, dependency or job, and lock files are regenerated after rebase, never hand-merged; store migrations are numbered at merge and never edited after merge; format fixtures are added per task with append-only manifests. The ArcScope integration owner orders merges and merges only pull requests of the claimant at the current claim epoch. +- Baseline: The accepted bootstrap is the Native AOT application with the WP02 build identity, dependency and provenance baselines; there is no product domain code yet. Every ArcScope capability is an open task. This repository's tasks are in the [arcscope](https://github.com/ArcForges/ArcForges-Design-B/blob/f8dff2d0144c7db020d35711d606334639dd078b/docs/planning/delivery/lanes/arcscope.md), [simulator](https://github.com/ArcForges/ArcForges-Design-B/blob/f8dff2d0144c7db020d35711d606334639dd078b/docs/planning/delivery/lanes/simulator.md) lanes and parts of the governance, release and runtime-proof lanes. +- Start only a task that Plan-B's `python tools/delivery.py ready` lists and whose claim you hold (`python tools/delivery.py claim --worker `, recorded as `claims/`, the ID in lower case with dots replaced by hyphens, such as `claims/scope-02`); continue interrupted work from its handoff record (`python tools/delivery.py show `) rather than restarting it. A task here becomes ready only after the adoption slice for its lane (`ADOPT.05.`) is recorded. +- Several workers may work here at once, each on a different claimed task in its own retained worktree and `task/` branch, inside the task's write scope. Acquisition, visualisation, analysis, reporting and portability tasks work in their own modules against the one acquisition owner, so they proceed in parallel. +- Shared files follow their [declared protocols](https://github.com/ArcForges/ArcForges-Design-B/blob/f8dff2d0144c7db020d35711d606334639dd078b/docs/planning/delivery/shared-resources.md): solution and project lists, central package versions and CI job lists are appended by the task that adds a project, dependency or job, and lock files are regenerated after rebase, never hand-merged; store migrations are numbered at merge and never edited after merge; format fixtures are added per task with append-only manifests. The ArcScope integration owner (the holder of `roles/integration-arcscope`) orders merges and merges only at the head commit reviewed for the claimant at the current claim epoch, keeping the task IDs in the merge title. - Title pull requests `[] `; a bundle of compatible ready tasks lists each ID, and planning alignment uses `[P2-018]`. - Earlier dated bootstrap and provenance records under `docs/` describe their original scope; they are evidence, not execution instructions.