Project 33

C2 — Deployment timing

Field	Value
Status	UNRESOLVED — An open question, conflict, or missing measurement blocks a stronger statement.
Strongest accepted evidence	IMPLEMENTATION ONLY
Evidence classes cited	IMPLEMENTATION, SYNTHETIC, TEST PROCEDURE
Gate reached	SYNTHETIC TEST (next: INERT BENCH SETUP)
Last review	CURRENT — snapshot recorded 2026-09-28 by tooling snapshot (no human review)

Question. Does the hardware-timed deploy output fire at the requested delay with sub-millisecond jitter, without blocking the control loop?

Current statement. Firmware schedules the deploy output with a one-shot esp_timer at a requested 50 ms delay. No hardware timing has been measured; the only timing data is a 21-row synthetic fixture that exercises report arithmetic.

Requirements

ID	Requirement	Check	Bound	Observed	Result
R-C2-JITTER	Deploy-output timing jitter is below 1 ms relative to the trigger.	physical measurement	≤ 1000 us	NOT MEASURED	NOT MEASURED
R-C2-NONBLOCKING	Scheduling the deployment does not block the control loop.	human review	none stated	judgement, not a value	REQUIRES HUMAN REVIEW

Predictions and measurements

ID	Quantity (condition)	Predicted	Model uncertainty	Measured	Abs. error	Rel. error	Criterion	Result
PRED-C2-DELAY	delay from deploy trigger call to GPIO 33 rising edge (rocket firmware as committed; inert bench; no load on GPIO 33)	50000 us [implementation]	not quantified	NOT MEASURED	—	—	not pre-registered	NOT MEASURED

Known contradictions

• None on record.

Open questions

• No hardware timing capture exists.

Discrepancies

• D-017 (OPEN) Ignition requires deployed fins, but deployment requires a boost-level acceleration
• D-018 (OPEN) Live telemetry timestamps are launcher relay times, not rocket sample times
• D-024 (OPEN) The deploy bench sketch measures a timer with the same timer
• D-016 (RESOLVED) Architecture diagram omitted the rocket’s fins-deployed ignition gate

Assumptions

• The requested delay in firmware is the intended deployment delay.
• Jitter means the spread of output-edge time relative to the trigger, measured by an instrument independent of the ESP32 clock.

Limitations

• Synthetic values do not demonstrate timer, scheduler, or actuator behavior.
• Twenty-one rows cannot bound a tail latency even if they were real.
• The existing bench sketch times the callback with the clock it is measuring (D-024).

Measurement needed to close the next gate

• Inert GPIO 33 edge timing against an external trigger reference, per proposed pre-registration P-001.

Pre-registered experiments

• P-001 (proposed)

What this claim does not establish

• Any inert physical measurement: none has been accepted for this claim.
• Physical performance of any hardware.
• Flight readiness or safety for live propulsion.

Evidence

Artifact	Class	SHA-256 (first 12)	What it is
Firmware/Rocket/src/deploy_isr.cpp	IMPLEMENTATION	013cb6614c2c	One-shot esp_timer callback that latches the deploy output on GPIO 33.
Firmware/Rocket/src/deploy_isr.h	IMPLEMENTATION	cd28abe0e40b	Deploy-timer interface and threshold constants.
Firmware/Rocket/src/main.cpp	IMPLEMENTATION	4a14aac55f7f	Rocket loop: 15 g egress trigger, 50 ms requested deploy delay, arming and ignition gates, telemetry.
docs/EVIDENCE/C2_latency.csv	SYNTHETIC	8cf6f0fe7a94	Synthetic timing fixture with the bench sketch’s column layout. Every row carries origin=synthetic-fixture.
tests/test_deploy_latency.py	TEST PROCEDURE	2012e20b2348	Checks fixture labeling and summary arithmetic; not a timing benchmark.
tests/test_firmware_safety.py	TEST PROCEDURE	ff5e17217ea2	Source-level checks of deploy-trigger units, arming gates, refusal logging, and protocol substring hazards. Reading source is not observing hardware.
Firmware/Rocket/tests/bench_deploy_isr.ino	IMPLEMENTATION	add4c75d552e	Bench sketch that times the deploy callback with the same esp_timer clock it is measuring.

Earlier versions (failure archive)

• evidence/archive/notes-v1/C2_latency.md — Historical C2 note.

A change to any of these files makes the last review insufficient

• Firmware/Rocket/src/deploy_isr.cpp
• Firmware/Rocket/src/deploy_isr.h
• Firmware/Rocket/src/main.cpp
• Firmware/Rocket/tests/bench_deploy_isr.ino
• docs/EVIDENCE/C2_latency.csv
• tests/test_deploy_latency.py
• tests/test_firmware_safety.py

---

All claims · Traceability · Discrepancies · Evidence Observatory

This site is open source. Improve this page.