[P2-018] Align repository instructions with the delivery model

AGENTS.md

@@ -18,6 +18,18 @@ The accepted architecture lives in [ArcForges-Design](https://github.com/ArcForg
 - Record what actually ran. A successful package-policy smoke does not prove native capability AOT,
   product behavior, release signing or NuGet publication. Run the checks documented in the README.
 
+## 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.
+
+- Baseline: WP00–WP02 are accepted (build governance, dependency admission, lockstep NuGet publication and the design-policy exports). Building blocks are placeholders and native families are probe-level; every platform, native, assistant and updater capability is an open task. This repository's tasks are in the [platform](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/lanes/platform.md), [native](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/lanes/native.md), [foundation](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/lanes/foundation.md), [assistant](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/lanes/assistant.md), [execution](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/lanes/execution.md), [updater](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/lanes/updater.md), [app-composition](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/lanes/app-composition.md), [device-bridge](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/lanes/device-bridge.md), [extensions](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/lanes/extensions.md), [runtime-proofs](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/lanes/runtime-proofs.md), [governance](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/lanes/governance.md) lanes and parts of the Cloud-core, policy and release lanes.
+- Start only a task that Plan-B's `python tools/delivery.py ready --claims` lists and whose `claims/<task-id>` branch you hold. A task here becomes ready only after the adoption slice for its lane (`ADOPT.02.<lane>`) is recorded.
+- Several workers may work here at once, each on a different claimed task in its own retained worktree and `task/<task-id>` branch, inside the task's write scope. Each native family adds its own CMake targets, wrapper project and workflow entries, and each managed mechanism its own project, so families and mechanisms 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, `Directory.Packages.props` 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; `eng/packaging/packages.json` gains one entry per producer task and every merge to main publishes all packages at one version; the vcpkg baseline and overlay ports change only through a dependency-admission change; generated policy data is regenerated from its pinned source and the reason-code registry is append-only; assistant store migrations are numbered at merge. The DesktopPlatform integration owner orders merges and merges only pull requests of the claimant at the current claim epoch.
+- Title pull requests `[<TASK-ID>] <summary>`; a bundle of compatible ready tasks lists each ID, and planning alignment uses `[P2-018]`.
+- The design-policy check still validates the retired package graph at the pinned Design commit. Keep `eng/policy/design-source.json` at a pre-P2-018 Design commit until the governance task `GOV.14` replaces that check with delivery-graph validation; see [design policy](docs/design-policy.md).
+- Earlier `docs/` records named after work packages or substeps describe their original scope; they are evidence, not execution instructions.
+
 ## Validation policy (P2-017)
 
 Follow the [current CI/local authority](https://github.com/ArcForges/ArcForges-Design/blob/47db6670a727317939b91245e8c0b288834acf99/docs/assurance/ci-and-local-validation-policy.md).

docs/design-policy.md

@@ -73,6 +73,17 @@ failure exit/report. A current-corpus pass alone is insufficient.
 The Linux policy job runs these platform-independent fixtures and verifies the pinned corpus before
 package creation. Their full reports are retained as `design-policy-*` artifacts.
 Native/managed compilation, package and publication checks remain required under P2-017;
-package consumers and native execution are local opt-in only. Local immutable export verification passed; PR CI, merge and publication
-remain pending until the corresponding run artifacts are reviewed. Policy checks
+package consumers and native execution are local opt-in only. Local immutable export verification passed before merge; WP00 is accepted in the Design
+[WP00 stage acceptance](https://github.com/ArcForges/ArcForges-Design/blob/7e56614ced01a12c84eb2047071d14399249ee90/docs/assurance/wp00-stage-acceptance.md). Policy checks
 establish no provider, device, product behavior or commercial activation evidence.
+
+## Delivery model (P2-018)
+
+[P2-018](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/decisions/phase-2-specification-decisions.md#rule-p2-018) replaces the numbered serial
+sequence with the [delivery graph](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/README.md). This checker still validates the
+retired package-level forward and reverse graphs, package header dependencies, topological order and serial
+execution line, so it cannot accept a Design commit that contains P2-018. Keep the pin at a pre-P2-018 commit,
+which remains valid for the glossary and invariant exports, until the governance task `GOV.14` replaces the
+graph check with the delivery-graph validation specified in the
+[design policy export](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/architecture/29-design-policy-export.md). DesktopPlatform then moves the pin
+through the normal reviewed refresh above. The P2-018 alignment changed no checker code, pin or export.