# Region and district reference completion protocol R02

Current pointer: `docs/reference-standard/current.json`. R02 supersedes the
reference-desk R01 standard and supplements the current District Protocol (R05) / Spatial Imagery R01.
It does not supersede their measured-world or construction acceptance gates.
One existing generator covers all D01–D21 and all issued region entries in the
R01 discovery register (West Coast, Southwest, Northwest). Discovery associations
are not approved boundaries. Every page visibly links this protocol and CHECKLIST.json.

## Exact five-view set and scale

Every scope requires **clean layout, street map, verified overhead, southeast
aerial and southwest aerial** as five distinct slots. Five arbitrary files do
not qualify. All derive from the same geometry revision/hash, metre units and
scale. Clean/street/overhead share map extents, target and registration; the first
three SW images intentionally share the same physical mesh projection. The street
map adds canonical route IDs. A concept image cannot satisfy verified overhead.

SW R07 uses 1512 × 940 projection viewports, a 7,000 m vertical span and
0.13428571428571429 px/m in all five images. SE/SW mean eye positions in those
quadrants relative to the target in the candidate grid (+X east, +Y north, +Z up).
They use the same target/elevation and orthographic scale. Oblique ground-plane
foreshortening remains; a projection-plane scale bar is not a claim of identical
ground distances in every screen direction. Geographic north/world registration
remain unresolved. The manifest records all cameras, units, hashes and evidence.
Existing R07 connections-oblique is not relabelled southeast.

## Four distinct readiness states

| State | Evidence required |
| --- | --- |
| Published | A separately verified live-release receipt; generator output alone remains pending_live_verification. Incomplete references may publish honestly. |
| Reference-complete | Every scoped reference requirement is complete with available artifact IDs, source revision/provenance, integrity/validation evidence, or a justified recorded N/A scope decision. No planned card qualifies. |
| Test-import-ready | Reference-complete plus a documented isolated import preflight and reproducible package/dependency evidence. ZIP existence, a successful deploy or an importer script alone is insufficient. This is readiness to test, not a claim the engine test passed. |
| Construction-ready | Test-import-ready plus named creator layout, measured world registration, actual engine import, collision, navigation and connection acceptance evidence. |

Reference completion is separate from later world registration and engine/runtime
acceptance. Publication never grants a higher state. The evaluator rejects missing
evidence, stale hashes/revisions, planned artifacts, unjustified N/A and contradictory
higher-state flags. Actual engine captures require native scene hash and tool/version;
concept, historical reference and deterministic geometry projection remain distinct.
A required N/A records reason, reviewer, scope revision and an existing hashed decision
record. N/A is not silently inferred from a missing file or empty gallery.

## Common visible sections and handoff

Every page has source gallery; exact five slots; clean/labelled/verified maps;
streets; topography/shoreline; capture requirements; geometry/views/downloads;
readiness gaps/checklist; and Quik start instructions. Each artifact has a content
revision, provenance, status, byte hash and validation evidence. SOURCE_EVIDENCE.json
pins all 65 existing source derivatives at main e96de208. Content revisions use
SHA256 identities where no historical author revision was issued. This proves
source availability/integrity, not visual or engineering approval. Existing source
catalog paths remain visible for original provenance.

Required completion items are in CHECKLIST.json. The fourteen native capture tasks
remain separate from the five deterministic reference views. Regional assets may
be shown as context but cannot complete a district-specific requirement. SW has
five actual geometry projections and 38 source references; NW has four source
references and no invented metric model. Topography/shoreline and other missing
scope work stay visible. All scopes currently remain reference-incomplete.

The interrupted owner's reported Blender scene/captures are not published in the
recoverable repository head and are not asserted as delivered here. Quik should
use the R07 start document/package only for isolated proposed review; preserve
existing Crown/Quik sources, current world and D03 construction pause. Return the
actual native scene/camera/tool details and measured evidence before advancing gates.

## Enforcement and regression checks

The existing `tools/verify_reference_standard.py` CI entry verifies deterministic
page bytes, coverage, internal links/anchors, artifact hashes/evidence and readiness
through `tools/reference_readiness.py`. The generator consumes the independently
verified five-view manifest rather than making new geometry. Run:

```
python tools/build_reference_standard.py --check
python tools/verify_reference_standard.py
python tools/reference_five_views/build.py --check
python -m unittest discover -s tools/reference_five_views -p 'test_*.py'
python -m unittest discover -s tools/tests -p 'test_reference_readiness.py'
```

The standalone five-view CI workflow addition was denied and remains stopped;
it is not recreated here. The existing shared verifier already runs in Verify
and enforces the integrated guards. Regression suites and full raster regeneration
are run locally for this release; automatic execution of those separate test
commands remains a documented CI coverage gap. This is not branch-protection or
administrator enforcement, and it does not invent acceptance decisions.
