SILVER/NODEDC_MISSION_CORE
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

docs(lab): keep blocked gates out of the catalog

Browse Source
This commit is contained in:
DCCONSTRUCTIONS
2026-07-26 18:27:16 +03:00
parent 2ffaf94052
commit a44d7627fd
2 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/13_LIDAR_WORKER_PRODUCT_AND_ROADMAP.md
+1 -1
View File
@@ -640,7 +640,7 @@ with a complete `missioncore.laboratory-method/v1` manifest.
| **E33 — recorded-source-paced fusion shadow** | Can the complete camera-first + geometry pipeline keep up with the recorded source stream on the worker? | Replay E32 at original host pace through bounded latest-wins queues. Record sensor-to-result p50/p95/max, deadline misses, queue depth, replacements, drops, stale results, recovery, CPU, RSS, GPU/VRAM, runtime/container and exact model-weight identities. Commands remain impossible. | Admit a replay-shadow candidate only when accounting is closed, resource bounds are declared and every late/missing result becomes explicit health state. |
| **E34 — temporal occupied layer** | Can occupied geometry remain stable enough for a local world model without polluting the persistent reconstruction? | Build a separate short-TTL layer over accepted E32/E33 evidence. Measure component continuity, re-association, ghost lifetime, stale expiry, map-frame jumps and geometry-only persistence. Visualize track history and expiration; retain raw/map evidence unchanged. | Accept only bounded occupied/unknown telemetry. Dynamic class, free space and planner authority remain unavailable unless independently proved. |
| **E35 — deterministic degradation and recovery** | Does the accepted pipeline fail safely when one source degrades? | Derive immutable replay variants for camera loss, LiDAR loss, pose staleness, delayed frames, bounded drops and timing offset. Preserve the original source and record every injected transformation. Measure status transitions, recovery time, queue accounting and false confidence. | Pass only if missing evidence becomes camera-only, geometry-only, stale or unknown; never guessed class, false free space or hidden success. |
| **E36 — second-source transfer gate** | Does the result survive another real capture rather than only RAVNOVES00? | First audit the source catalog for a second recording with the required camera, LiDAR, pose, time and calibration identities. Run the accepted E32–E35 profile unchanged when such evidence exists. Public GOOSE/RELLIS data may qualify an algorithm but cannot substitute for this K1 transfer gate. | Compare the frozen profile without retuning. If no eligible source exists, publish a blocked LAB record naming the missing modalities; do not fabricate a result or collect new data by default. |
| **E36 — second-source transfer gate** | Does the result survive another real capture rather than only RAVNOVES00? | First audit the source catalog for a second recording with the required camera, LiDAR, pose, time and calibration identities. Run the accepted E32–E35 profile unchanged when such evidence exists. Public GOOSE/RELLIS data may qualify an algorithm but cannot substitute for this K1 transfer gate. | Compare the frozen profile without retuning. If no eligible source exists, keep the gate blocked only in the roadmap/Ops plan: do not publish an empty LAB page, fabricate a result or collect new data by default. |
Execution is strictly sequential through E33: E30 determines what E31 is
allowed to change; E31 determines the E32 profile; E32 determines the E33
docs/15_LABORATORY_RUN_CANON.md
+4 -3
View File
@@ -170,9 +170,10 @@ A planned LAB number is not a placeholder page. Before execution it must name:
After execution, the planned definition is retained in the immutable result.
Changing the source, algorithm, model weights, preprocessing, thresholds or
runtime creates a new LAB run. A failed or blocked experiment remains useful
only when its missing evidence and failure reason are explicit; an empty
viewer or invented metric is never a laboratory result.
runtime creates a new LAB run. A failed experiment is publishable only when
real input and failure evidence exist. A gate blocked before execution remains
in the roadmap/Ops plan and does not create a LAB catalog item. An empty viewer
or invented metric is never a laboratory result.
The accepted E30–E36 camera-first/K1 research sequence is maintained in
`docs/13_LIDAR_WORKER_PRODUCT_AND_ROADMAP.md`. It deliberately starts with the