This map separates inherited AutoQA claims, the authoritative limits analysis, and manager-facing planning values introduced by the redesign.
Part of Provenance
- Format
- MD
- Lines
- 51
- Size
- 4.3 KB
- SHA-256 (v2)
ec6b86d59eff257397429613044054c3f169926cfeff21f51901a3b00594bbac
Claims carried forward from the foundation
| Manager-facing statement | Foundation source |
|---|---|
| The decision currently requested is approval of a bounded scoping pass, not approval of the pilot. | site/index.html, site/decide.html |
| The pilot, if later approved, is one-project shadow measurement and does not authorize automated rejection, pay, account, or production-enforcement decisions. | site/index.html, site/decide.html, site/pilot.html |
| A later pilot should return one of four outcomes: stop, narrow, human-assist only, or consider a separately approved limited-automation proposal. | site/index.html, site/pilot.html |
| QA disagreement can reflect unclear instructions, reviewer error, missing expertise, or legitimate differences in judgment. | site/proposal.html, site/research.html |
| The architecture is centered on a versioned evaluation contract, with models treated as replaceable components. | site/architecture.html, site/guide.html, KERNEL.md |
| A pilot must measure the human baseline, build expert-adjudicated test data, compare the exact configured instrument, run in shadow mode, and return a recommendation. | site/pilot.html, site/decisions.html |
| Published results do not establish accuracy on the exact task or deployment configuration. | site/research.html, site/evidence.html |
| The evidence ledger is the system of record for graded research findings and source-level caveats. | site/evidence.html |
Limits carried forward from the authoritative attachment
attachments/THEORETICAL_LIMITS.md is represented on the site by site/limits.html. The manager layer may summarize it, but may not weaken it.
| Limits statement | Site location |
|---|---|
| Master identifiability limit: when the same observable record is compatible with different correct answers, no record-only evaluator can decide both correctly. | site/index.html, site/limits.html#l0 |
| The permanent ceilings include construct definition, rule interpretation, absent intent or counterfactual truth-makers, local-versus-global evidence, pipeline error, authorization, and incentive effects. | site/limits.html#l1 through site/limits.html#l8 |
| Existential support and universal absence are asymmetric; long-record coverage must be measured rather than presumed. | site/limits.html#l4, site/limits.html#l5 |
| Capability never grants authority. Consequence-bearing use requires independently measured error bounds and explicit authorization. | site/limits.html#l7 |
| A deployment beyond the limits is identifiable through the violation checklist. | site/limits.html#checklist |
Planning values (withdrawn 2026-07-19)
Person-hour, role, and calendar planning values were removed from the site at the owner's direction. The manager layer now requests one decision only: define and adopt the limits of AutoQA use (verdict vocabulary, criterion standing, adverse-authority rule, standing audit). Any measurement effort is sized in a separately approved scoping pass; no effort figures appear on the site until that pass produces them.
Evidence-currency treatment
- Manager and technical display prose uses model-independent results, dated 2025–2026 measurements, measured gaps, or entries graded as current-generation confirmed.
- Superseded-generation capability figures remain only inside
site/evidence.htmlas graded archival records; they are not repeated as current claims elsewhere. - Changed display claims point to the existing ledger or to
site/limits.html. The protected data layers—site/evidence.html,site/library.html,site/assets/claims.json, andsite/assets/search-index.json—remain unchanged.
Information architecture
site/index.htmlis the manager decision brief and introduces the limits before the pilot case.site/limits.htmlis the full limits document and is one click from the homepage.site/decide.htmlrecords the bounded scoping decision; routing remains intentionally unwired.site/guide.htmlis the task-oriented entry to implementation, evaluation, and the system-of-record pages.- Proposal, pilot, architecture, research, decision register, evidence ledger, library, and
KERNEL.mdremain reachable at their existing URLs.