Source map and terminology

The version and repository revision identify this guide's documentation basis. The v3 source manifest records actual consulted origins and hashes, the current book candidate, and byte comparison of the inherited v2 operational source manifest. Unchanged operational material is retained from v2; changed operating sources were re-examined against the merged development-loop amendment. The comparison does not claim new execution of example commands or a project census. The source comparison records the updated basis, resolved prior differences and remaining adoption limits. The linked live project entries govern recovery and selection; dated project reports supply evidence of their own inspection scope. No project-wide status census, consumer adoption, or production activation is established by this guide. These source records support navigation and explanation, not new project authority.

Need	Primary navigation
Runtime entry, roles, authority, permission intersections	Root entry, role registry, Runtime contract, CONTRACT
Paths, lifecycle, dependency representation	SPEC, TYPES, cycle doctrine
Formation and setup	decomposition standard, workflow index, project setup
Production and examination	Scope-of-Work standard, software profile, concordance method
Repeated development	v7 route and adoption boundary, construct local graph, bounded reconciliation, each project's live loop
Run indexing and conditional intake	Runs entry, Task Management, human manual §5.6
Change, integration, residual concerns	scope change, Task Management, Chirality change
Professional and domain limits	DIRECTIVE, the actual project rules, accepted domain sources and responsible human's decisions

Undertaking means an identified body of work with a purpose and completion conditions; it can span sessions and Packages. Session means an interaction period in its actual host. Candidate means the particular source/artifact state being examined. Snapshot preserves identified material at a governed boundary. Derivative is a generated or interpreted view whose sources and status must remain explicit. Hold is a restriction on a named act; ordinary progress does not dissolve it. Acceptance is the applicable human act about an identified subject. Root entry · CONTRACT · Runtime contract

The human-facing manual uses reckoning for agent interpretation, comparison, inference, and selection, reserving judgment for the accountable human. Some operational role files use “judgment” in its ordinary task-performance sense. Read both without attributing professional or acceptance authority to the agent. Verification examines conformity to stated criteria; validation examines fitness for the intended use. State exactly what each check supports, who examines its adequacy, and what remains. Human manual, preface and §1.5 · DIRECTIVE §3