ChiralityChirality Agent User Manual · Edition 4 · Accepted 10 October 2026 · Source 22dd62a7f0 ↗ · Markdown
1. Select the active work
The conversation supplies the intended result, scope and authorization. A new session does not cancel prior direction or prove that earlier work is complete. Recover the relevant unfinished work before replacing it.
| Scope | Repository-relative entry | Current use |
|---|---|---|
| Root | execution/_Coordination/LOOP_INIT.md |
Shared instructions, workflows, skills, tools, CI and reference documents, as steered. |
| App v4 | projects/chirality-app-v4/loop/LOOP_INIT.md |
The current App and application-host integration work. |
| SWBPIPE | projects/chirality-piping/loop/LOOP_INIT.md |
Piping design and stress-model authoring. |
| Frozen products | projects/FROZEN.md |
Historical recovery of App v3, Runtime and PEC; no development or verification without explicit reactivation. |
| Domain engines | Owning instructions under _DomainEngines/ |
Work only under a steer covering that scope. |
Resolve the checkout before using paths. A linked worktree has its own root. The following observations do not change files:
git rev-parse --show-toplevel
git status --short --branch
git rev-parse HEAD
Read Root AGENTS.md, the project entry and the active role when a role is selected. Then locate the affected deliverable or shared component. Read the PRD and companions for the requirements and interfaces involved, rather than reading the entire governance history.
A useful first return identifies the work already available, the next authorized step and any specific missing input. Do not reconstruct a standing backlog from archived plans.