Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 12 additions & 1 deletion AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -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 ArcNotes capability is an open task. This repository's tasks are in the [arcnotes](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/lanes/arcnotes.md), [app-composition](https://github.com/ArcForges/ArcForges-Design-B/blob/fd16c5f285de0bda2d0320cdff4d52c34c9098ed/docs/planning/delivery/lanes/app-composition.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/<task-id>` branch you hold. A task here becomes ready only after the adoption slice for its lane (`ADOPT.04.<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. Feature tasks register their services and capabilities through their own modules, so editor, storage, search, portability and sync work proceed in parallel against the one canonical document writer.
- 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; the composition root only lists modules; store migrations are numbered at merge and never edited after merge; format and import fixtures are added per task with append-only manifests and golden fixtures are never regenerated to pass a test. The ArcNotes 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]`.
- Earlier dated bootstrap and provenance records under `docs/` describe their original scope; they are evidence, not execution instructions.
Loading