Decision Drivers

• A developer should complete a task without reconstructing hidden product boundaries from source code.
• Humans, agents, CI, documentation, and support surfaces should project the same structured facts.
• The capability that implements behavior must continue to own its semantics.
• Human explanations and translations must retain an identifiable author and must not be overwritten by deterministic generators.
• Fixture, package, native-host, installed-application, browser, deployed-site, and release evidence must remain distinguishable.
• Failure, partial success, empty results, unsupported scope, missing authority, and unobserved state must not collapse into one value.
• Default operation must remain local-first, privacy-preserving, read-bounded, and cross-platform.
• Adoption must be incremental, reversible, and useful before every target component exists.
• Public support and release claims must become weaker automatically when their required evidence is absent or stale.
• DX improvement must be measured through task completion and recovery, not artifact counts or a single vanity score.