diff --git a/AGENTS.md b/AGENTS.md index 3ba19c4..1d818a8 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -11,4 +11,15 @@ - Validate only affected behavior once. Do not install or reinstall vcpkg, SDKs, emulators or toolchains to expand coverage. Hooks must not rebuild or test implicitly. Serialize CPU-heavy local work and reuse existing caches. - Never describe unrun local/macOS/runtime checks as passed. Historical evidence is not a command to repeat it. Documentation-only changes need consistency review, not product builds. - Use the normal network; no proxy 7890, other proxy configuration, wsl.exe or WSL wrappers. Stop and report the exact failing operation on a network failure without retries. -- Use retained worktrees/branches and PR titles prefixed with the current work package/substep. Review the full latest PR head and merge only after applicable reduced CI succeeds when merging is user-authorized. Post-merge checks stop after expected commit, required publication result and clean primary fast-forward; do not begin another validation cycle. +- Use retained worktrees/branches and PR titles prefixed with the delivery task ID (see below). Review the full latest PR head and merge only after applicable reduced CI succeeds when merging is user-authorized. Post-merge checks stop after expected commit, required publication result and clean primary fast-forward; do not begin another validation cycle. + +## 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: 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. +- 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.