Requirements closeout checklist
Open the 17 June 2026 RFS-011 closeout checklist, with JSON data, naming the locked requirements decisions, the remaining stakeholder asks, and the criteria for closing the item.
Technical file bundle
EmberScope technical files
Downloadable files behind the optical design work: the optimized prescription, the earlier packaging study's source spec, validation gates, CAD, Blender geometry, review metrics, and diagrams for deeper technical review.
What is included
A stable file bundle tied to the current optical design.
Stakeholder answer pack
Open the 18 June 2026 RFS-011 answer pack, with JSON data, turning the remaining target-area, altitude, payload-branch, airframe, and sign-off decisions into recordable answer rows.
Sign-off readiness matrix
Open the 19 June 2026 RFS-011 sign-off matrix, with JSON data, mapping likely stakeholder answer sets to requirements closeout, COTS quote work, prescription restart, or required replanning.
Mission decision packet
Open the 14 June 2026 decision packet translating the F-number / aperture trade into the survey-vs-spotter, target-class, fleet, and detector choices needed before the next prescription pass.
Coverage sizing grid
Open the 15 June 2026 sizing grid, with JSON data, translating target area into payload count, max unit cost, and the COTS/custom decision boundary.
COTS payload screen
Open the 16 June 2026 COTS screen, with JSON data, testing COTS and camera-only payload paths against the same 3 cm target, coverage, raw-data, and quote-ceiling gates.
COTS quote packet
Open the 20 June 2026 COTS quote packet, with JSON data, turning the COTS screen into vendor evidence fields, candidate quote order, and acceptance gates for RFS-011.
COTS quote comparison
Open the 21 June 2026 COTS quote comparison register, with JSON data, scoring returned vendor quotes against hard stops, weighted evidence gates, and branch decision rules for RFS-011.
Requirements evidence ledger
Open the 3 July 2026 RFS-011 evidence intake ledger, with JSON data, tracking missing stakeholder decisions, vendor quote evidence, validation samples, sign-off source notes, and the source-note contract before closeout.
Payload capability and coverage
Open the per-drone coverage model, with JSON data, recalculating fixed-wing coverage and payload cost from the current optics assumptions.
Optimized four-mirror prescription (current reference design)
Surface prescription CSV (positions, tilts, radii, conics, clear apertures), with field metrics CSV and metrics JSON from the 10 June 2026 optimization. This is the design described on the optics hub and in the evidence summary.
Optimized design geometry exports
Generated from the committed design source with a traceable hash: layout SVG, OpenSCAD CAD, Blender geometry JSON with scene script, validation gates, and manifest. The site renders are produced from this geometry during the raksasa deployment build; committed PNG refreshes are only needed for review in git.
Mission survey video
Narrated video page and MP4 file summarize scan-mirror and pushbroom mission heritage for systems engineers.
Mission survey storyboard
Storyboard page records the ten-panel manga handoff and links the tracked assembler while leaving generated art/PDF outputs local.
Manifest and summary
Manifest JSON and summary markdown describe the file contents and current-design choice.
Metrics and diagrams
Source-derived metrics CSV, validation gates, and layout SVG are regenerated from the committed component spec.
Current design parameters
Starter-freeform parameters and prescription JSON expose the current design state in a machine-readable form.
Geometry handoff
Blender geometry JSON, Blender scene script, and OpenSCAD CAD preserve the same source-spec geometry.
Source of truth
Component source JSON, validation gates, Blender JSON, and OpenSCAD CAD are generated from one committed design spec.
Build structure
The website build is mapped as source files, programs, generated artifacts, and deploy flow.
projects/rural-fire-service-camera/build-structure.v1.json, not drawn by hand.| Program | Reads from | Generates for the site |
|---|---|---|
render_build_structure.py |
build-structure.v1.json plus the build script path map. |
site/assets/rfs/build-structure/emberscope-build-structure.svg and .json. |
rfs_design_source_of_truth.py |
designs/emberscope-starter-freeform.v1.json. |
site/assets/rfs/design-source/* and the source-derived site/assets/rfs/review-package/* bundle. |
rfs_multi_mirror_candidate_checkpoint.py |
Architecture branch builders and shared proof-of-concept ray-trace primitives. | site/multi-mirror-candidates.html plus site/assets/rfs/multi-mirror/* CSV/JSON artifacts. |
rfs_fleet_coverage_model.py |
The F-number / aperture radiometry model plus fixed-wing platform and payload-cost assumptions. | site/fleet-coverage.html plus site/assets/rfs/fleet-coverage.json. |
rfs_coverage_sizing_grid.py |
The generated per-drone coverage model and the AUD 100k payload-budget constraint. | site/coverage-sizing-grid.html plus site/assets/rfs/coverage-sizing-grid.json. |
rfs_cots_payload_screen.py |
The F-number/aperture radiometry model, the generated per-drone coverage model, and the committed COTS baseline evidence. | site/cots-fleet-screen.html plus site/assets/rfs/cots-fleet-screen.json. |
rfs_cots_quote_packet.py |
The generated COTS payload screen rows plus RFS-011 quote and evidence-gate policy. | site/cots-quote-packet.html plus site/assets/rfs/cots-quote-packet.json. |
rfs_cots_quote_comparison.py |
The generated COTS quote packet plus RFS-011 scorecard, hard-stop gates, and branch decision rules. | site/cots-quote-comparison.html plus site/assets/rfs/cots-quote-comparison.json. |
rfs_requirements_closeout_checklist.py |
The generated coverage sizing grid, COTS payload screen, and locked mission-decision evidence. | site/requirements-closeout.html plus site/assets/rfs/requirements-closeout.json. |
rfs_requirements_answer_pack.py |
The closeout checklist payload plus coverage, altitude, COTS, and airframe decision evidence. | site/requirements-answer-pack.html plus site/assets/rfs/requirements-answer-pack.json. |
rfs_requirements_signoff_matrix.py |
The answer pack payload plus coverage, altitude, COTS, airframe, and sign-off consequences. | site/requirements-signoff-matrix.html plus site/assets/rfs/requirements-signoff-matrix.json. |
render_diary_feed.py |
daily-diary/*.md. |
site/diary.html, site/rss.xml, and site/feed.xml. |
render_todo_page.py |
TODO.md. |
site/rfs-todo.html for local/internal status review; the public build removes it from dist/. |
build_static_site.sh |
The generated site/ tree and static assets. |
dist/ and dist/build.json, then the deploy workflow rsyncs that tree to emberscope.symmachus.org. |
Traceability checkpoint
The current reference has one component source and repeatable exports.
Component-level design JSON
Mirrors, aperture, window, baffle allowance, detector, electronics, bench, and payload envelope have stable IDs and explicit units.
Blender and CAD files
The same spec writes Blender geometry, a runnable Blender scene script, an OpenSCAD CAD handoff, and a source-hashed manifest.
Feasible package, unresolved image quality
Automated checks pass the package, mass, throughput, focus, and freeform screens, while edge blur and detector-energy gates keep the design in maturation status.
Two design generations
The optimized four-mirror prescription is the reference design; the starter-freeform bundle is the earlier packaging study.
The starter-freeform files (source spec, CAD, Blender geometry, renders) remain useful as the traceable packaging study, but its image quality was never close to detector-ready: blur at the field edge was multi-millimetre against a 17 um detector pitch.
The optimized prescription of 10 June 2026 replaces it as the design of record, with its own traced-geometry exports: layout SVG, OpenSCAD CAD, Blender geometry and scene script, validation gates, and renders, all hash-traced to the committed design JSON.
Why these files matter
The concept is inspectable instead of decorative.
Stable file paths
Stable URLs provide metrics, parameters, prescriptions, and geometry.
Machine-readable exports
The current-design JSON files can feed decks, comparisons, or future browser-side viewers without manual transcription.
Performance limit stays attached
The validation gates still show that the present optical geometry is a baseline to improve, not a closed optical prescription.