sindoring
d233a41ce8
Work-Package: M00-QAR-TERRAIN-HEIGHT-001 Agent: sindo-main-codex Tests: five-point terrain probe, coordination and documentation gates Fidelity: four cameras confirmed above terrain; waterfall tile missing terrain mesh recorded
2.8 KiB
2.8 KiB
M00-QAR-TERRAIN-HEIGHT-001 — Terrain height diagnostic
Ownership
- Target: M00
- Program: QAR
- Owner/Agent ID: sindo-main-codex
- Branch:
work/sindo-main-codex/m00-terrain-height - Lease expires UTC: 2026-07-13
- Integrator: milestone integrator
Outcome
Measure rendered terrain height and camera clearance at the five build 12340 golden checkpoints without changing renderer behavior.
Non-goals
- Adding a runtime terrain-query API or collision system.
- Changing terrain geometry, coordinate mapping, placements, or cameras.
- Implementing the M01 CoordinateMapper.
Paths
- Exclusive:
src/tools/probe_render_terrain_height.gd - Shared/hotspots: renderer baseline documentation and runner
- Generated/ignored: local JSON probe reports
Contracts and data
- Public API/events: headless diagnostic CLI only
- Schema/format version: report schema 1
- Migration/compatibility: none
- Consumers: M00 fidelity diagnosis
Dependencies
- Requires: calibrated renderer manifest and active terrain meshes
- Blocks: classification of under-terrain camera gaps
- External state: local extracted/cache data
Verification
- Commands: terrain probe, M00 dry-run, coordination and documentation gates
- Fixtures: five calibrated manifest checkpoints
- Fidelity evidence: camera clearance against rendered OpenWC terrain
- Performance budget: offline diagnostic only
Documentation deliverables
- Inline public API docs: script CLI header
- Module specification: verification/source map
- Data-flow diagram: terrain probe flow
- Sequence/state/dependency diagrams: synchronous diagnostic; not applicable
- Source map/status updates: baseline and renderer module
Simplicity and naming
- Important names introduced:
terrain_height,camera_clearance - Simplest considered solution: CPU ray against already loaded mesh
- Rejected complexity/abstractions: new parser, physics collision, runtime query service
- Unavoidable complexity and justification: tile-local ray transform is required by mesh ownership
- Measured optimization evidence: not applicable
Status
- State: ready
- Done: active-mesh terrain probe, four clearance measurements, isolated waterfall missing-mesh confirmation and documentation
- Next: integrator review; placement/composition diagnosis for four points and tile 30_49 ownership diagnosis remain separate packages
- Blocked by:
Handoff
- Commit: branch HEAD
- Results: four cameras are 12.034..90.178 units above terrain; waterfall tile has no accessible terrain mesh after 10-second settle
- Remaining risks: mesh ray does not measure WMO/M2 occlusion; waterfall missing mesh requires streaming ownership investigation
- Documentation updated:
docs/RENDER_BASELINE.md,docs/modules/world-renderer.md