BurnLens — Release governance and evidence system

Field case / 01

Release governance / evidence system

BurnLens

BurnLens asks how one bounded experimental computer-vision-to-geospatial intelligence release can become understandable, inspectable, citable, and responsibly interpretable as a coherent whole.

It is an experimental portfolio project for technical and technical-adjacent reviewers, not an operational wildfire tool.

Authority

Authority map

D / Human decisions

Drew set the portfolio thesis, target audience, use boundaries, owner stop conditions, and publication direction, and owned the human decisions; Codex was assigned technical, product, and reliability direction within that owner-defined envelope.

C / Public constraint

The public release had to remain useful while excluding credentials, private owner responses, private logs, and machine-local paths, without implying official or operational capability.

Assembly

Reviewer path

When the story was fragmented across correct artifacts, the project chose one canonical reviewer entry point around them rather than rewriting them.

R / Release record

BurnLens reached a public, complete Phase Six portfolio release: v0.56.0-baseline-first-portfolio-release at commit e2e0b778; the later evidence snapshot is a741111d, four commits after the release.

Boundary

Use boundary

BurnLens is experimental portfolio evidence, not official wildfire information, emergency guidance, or operational decision support.

Reliability includes recognizing when evidence is insufficient and making that stop reproducible.