feat: finalize corrected-route planning and Rerun recording review
This commit is contained in:
@@ -6,9 +6,11 @@ Status: accepted, 2026-07-26
|
||||
|
||||
Mission Core has two different catalogs over related evidence:
|
||||
|
||||
- **Data → Sessions and records** contains only original physical captures.
|
||||
- **Data → Sessions and records** contains independent original physical captures.
|
||||
Examples: `RAVNOVES00`, `TEST007`, `TEST009`. A source record is immutable
|
||||
evidence received from a device or recording adapter.
|
||||
evidence received from a device or recording adapter. Per the 2026-09-21
|
||||
owner decision, physical passes acquired by the planner are shown with their
|
||||
studies in **LAB → Planner**, not in Data or the reference selector.
|
||||
- **Test contour → Laboratory contours** contains derived experimental runs.
|
||||
Examples: LAB E24, E25, E26, E28 and E29. A LAB run references an original
|
||||
record and never becomes another original capture.
|
||||
@@ -16,7 +18,10 @@ Mission Core has two different catalogs over related evidence:
|
||||
The backend may keep both entities in one durable SQLite catalog, but every
|
||||
consumer must request an explicit catalog scope:
|
||||
|
||||
- `scope=source` for original records;
|
||||
- `scope=standalone` for Data and planner reference choices: original records
|
||||
excluding explicit planner-acquisition bindings;
|
||||
- `scope=source` for all original records, including planner passes needed for
|
||||
recorded comparisons and scientific inspection;
|
||||
- `scope=laboratory` for LAB projections;
|
||||
- `scope=all` only for internal joins that must resolve both a derivative and
|
||||
its source.
|
||||
@@ -24,6 +29,12 @@ consumer must request an explicit catalog scope:
|
||||
Deleting, renaming or moving source payloads to make the UI look clean is
|
||||
forbidden. Product separation is expressed by typed projections.
|
||||
|
||||
A planner pass remains a physical source, not a synthetic LAB projection.
|
||||
Classification uses exact run/session acquisition bindings, never names or
|
||||
registration success. Hiding it from Data does not remove its raw evidence or
|
||||
its historical planning report. See
|
||||
[the full-reference/catalog audit](audits/2026-09-21-whole-reference-and-capture-catalogs.md).
|
||||
|
||||
## Current reference-source policy
|
||||
|
||||
RAVNOVES00 is the sole active physical reference source for the current
|
||||
|
||||
Reference in New Issue
Block a user