Field case / 01
Release governance / evidence system
BurnLens
BurnLens
It is an experimental portfolio project for technical and technical-adjacent reviewers, not an operational wildfire tool.
My contribution
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.
One decision I owned
For BurnLens, I bounded the release to one repository and directed it to Codex Sites. Codex assembled a canonical reviewer path, rechecked source and claim boundaries, and verified the production result. A local preview and two social-card attempts failed their gates, so they stayed rejected.
This demonstrates a bounded human–Codex workflow—not autonomous authorship, independent user testing, or universal design superiority.
Frame
One canonical reviewer entry point
BurnLens asks how one bounded experimental computer-vision-to-geospatial intelligence release can become understandable, inspectable, citable, and responsibly interpretable as a coherent whole.
When the story was fragmented across correct artifacts, the project chose one canonical reviewer entry point around them rather than rewriting them.
Release
Release record
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.