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

AGENTS.md

@@ -24,6 +24,17 @@
   reflection-based System.Text.Json. `eng/check_serialization.py` and the Native AOT
   `tests/public/SerializationProbe` enforce this in the build.
 
+## 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: WP03.00–WP03.02 are accepted and WP03.03 has not started. Its closures and every later contract area are open tasks in the [contracts lane](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/lanes/contracts.md); this repository also owns tasks in the extensions, governance 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. No task here is ready until its adoption slice (`ADOPT.03.contracts`, `ADOPT.03.extensions`, `ADOPT.03.governance` or `ADOPT.03.release`) 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. Closures are authored concurrently in their own domain proto or HTTP-schema, constraint and fixture files.
+- Shared files follow their [declared protocols](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/shared-resources.md): the package inventory, foundation inventory and constraint aggregate are append-only per closure; a proto file with several contributing tasks has one designated author task; generated sources and descriptor baselines are regenerated after rebase, never hand-edited or hand-merged. The Contracts integration owner merges closure pull requests one at a time, and each merge to main publishes all packages at one candidate version.
+- Title pull requests `[<TASK-ID>] <summary>`; a bundle of compatible ready tasks lists each ID, and planning alignment uses `[P2-018]`. The integration owner merges only pull requests of the claimant at the current claim epoch.
+- Dated `docs/wp03-*` and `docs/implementation/wp00-*` records 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).

README.md

@@ -7,11 +7,14 @@ Handwritten protobuf contracts and generated C#/TypeScript/Java/Kotlin packages
 ArcForges product family. Consumers install versioned packages; they do not clone
 this repository, run protoc, use Git submodules or depend on sibling source.
 
-**Current scope:** WP03.00 establishes source-bearing contract boundaries with
-selected complete Foundation/error, event, private product/helper, operator and
-extension records, HTTP definitions, validators and an offline inventory CLI.
-Hello compatibility remains; complete business services and product integration
-remain later WP03 substeps. The exact producer inventory is
+**Current scope:** WP03.00–WP03.02 are accepted. WP03.00 establishes source-bearing
+contract boundaries with selected complete Foundation/error, event, private product/helper,
+operator and extension records, HTTP definitions, validators and an offline inventory CLI;
+[WP03.01](docs/wp03-01-foundation.md) adds the foundation value records and
+[WP03.02](docs/wp03-02-serialization.md) the generated-only serialization posture. Hello
+compatibility remains. Capability and resource descriptors (WP03.03), the complete business
+operation registries and the package-level gates are open delivery tasks in the
+[contracts lane](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/lanes/contracts.md). The exact producer inventory is
 [`eng/contract-packages.json`](eng/contract-packages.json).
 
 | Package family                                                                             | Contents                                                                                          |

docs/implementation/wp00-00-naming.md

@@ -25,8 +25,8 @@ spoofed remote owners, malformed policy and provenance exception abuse. These ar
 source-policy tests, not product or provider runtime evidence.
 
 CI runs the naming scan and retains its JSON receipt, then the existing tooling test
-suite, package/consumer and security gates. Applicable CI and main publication remain
-pending until the corresponding actual run completes. WP02/WP05 own continuing
+suite, package/consumer and security gates. This record was written before its CI and main
+publication ran; WP00 is accepted in the Design [WP00 stage acceptance](https://github.com/ArcForges/ArcForges-Design/blob/7e56614ced01a12c84eb2047071d14399249ee90/docs/assurance/wp00-stage-acceptance.md). WP02/WP05 own continuing
 family-wide build enforcement. WP30 owns the already selected Android prerelease
 identity migration; WP33/WP36/WP53 own real native association/installer behavior.
 

docs/implementation/wp00-01-derived-policy.md

@@ -26,6 +26,6 @@ declaration mutations, unknown nested fields, escaped forbidden values, copies,
 invalid owner/path/digest registrations and duplicate JSON keys. The complete
 tooling suite, locked producer build, packaged consumers and security checks remain
 required. `artifacts/evidence/wp00-01-family.json` records the actual local nine-root
-scan and the consumed declaration. PR CI and post-merge registry publication are
-pending until their run-specific evidence is verified; no product-readiness gate
+scan and the consumed declaration. This record predates its PR CI and post-merge registry
+publication; WP00 is accepted in the Design [WP00 stage acceptance](https://github.com/ArcForges/ArcForges-Design/blob/7e56614ced01a12c84eb2047071d14399249ee90/docs/assurance/wp00-stage-acceptance.md); no product-readiness gate
 closes from this policy change.

docs/wp03-01-foundation.md

@@ -1,5 +1,8 @@
 # WP03.01 foundation contracts: implementation and evidence
 
+Accepted: the Design [WP03.01 completion receipt](https://github.com/ArcForges/ArcForges-Design/blob/7e56614ced01a12c84eb2047071d14399249ee90/docs/assurance/wp03-01-implementation-evidence.md)
+records the merged source, required CI and normal publication. The pre-merge status below is historical.
+
 Status: pre-merge implementation record. Source, targeted local validation and
 independent provenance review are complete. Applicable PR CI, merge and normal
 publication remain required acceptance gates. This record does not establish a

docs/wp03-02-serialization.md

@@ -1,5 +1,8 @@
 # WP03.02 serialization posture: implementation and evidence
 
+Accepted: the Design [WP03.02 completion receipt](https://github.com/ArcForges/ArcForges-Design/blob/7e56614ced01a12c84eb2047071d14399249ee90/docs/assurance/wp03-02-implementation-evidence.md)
+records the merged source, required CI and normal publication. The pre-merge status below is historical.
+
 Status: pre-merge implementation record. Source and targeted local validation are
 complete. Applicable PR CI, merge and normal publication remain required acceptance
 gates; this record does not establish a released WP03.02 candidate.