KB-3591
70000x · 09 — Final readiness matrix (6/6 LIVE_READY, 6/6 runnable, 6/6 PASS)</title> <parameter name="tags">["iu-core","70000x","readiness","matrix","live-ready","capability"]
4 min read Revision 1
70000x · 09 — Final readiness matrix (six user flows)
Source of truth for "is flow X ready for the next user test?"
| # | Flow | Substrate | DOT/operator path | Test runnable | Evidence | Rollback | Remaining gap |
|---|---|---|---|---|---|---|---|
| 01 | Autocut & reconstruct | LIVE_READY (fn_iu_reconstruct_source) |
./run_six_flow_tests.sh test_01 |
YES — PASS | test_01_*.log (3 verdict rows) |
n/a (read-only) | none |
| 02 | Axis B filter | LIVE_READY (iu_metadata_tag_registry, 3 axis-B kinds) |
./run_six_flow_tests.sh test_02 |
YES — PASS | test_02_*.log (3 verdict rows) |
n/a (read-only) | none |
| 03 | Parent/child/grandchild | LIVE_READY (fn_iu_subtree + iu_tree_path) |
./run_six_flow_tests.sh test_03 |
YES — PASS | test_03_*.log (3 verdict rows) |
n/a (read-only) | none |
| 04 | Create/edit piece document | LIVE_READY (fn_iu_compose + 8 lifecycle fns) |
./run_six_flow_tests.sh test_04 |
YES — PASS | test_04_*.log (5 verdict rows) |
BEGIN/ROLLBACK + actor='iu-core-70000x-test-runner' | live-mode lifecycle proof → 80000x |
| 05 | Piece trigger in/out | LIVE_READY (fn_iu_piece_emit_event + trigger, 6 piece.* event_types) |
./run_six_flow_tests.sh test_05 |
YES — PASS | test_05_*.log (3 verdict rows) |
BEGIN/ROLLBACK + actor-tagged | live-mode emit → 80000x |
| 06 | SQL bridge piece ↔ DB | SUBSTRATE_LIVE (table + view + 2 fns) | ./run_six_flow_tests.sh test_06 |
YES — PASS | test_06_*.log (6 verdict rows) |
BEGIN/ROLLBACK + actor='iu-core-70000x-test-runner' | inbound_capture trigger wiring → 80000x |
Aggregate status
- 6/6 flows are runnable and PASS as of 20260525T081115Z.
- 6/6 flows are rollback-clean — post-rollback DB byte-equivalent at data layer to pre-TX.
- 6/6 flows have documented evidence in
_reports/<ts>/test_NN_*.log. - 6/6 flows have identified gaps packaged as 80000x carry-forward.
What "test-ready" means
The next user test (DOT command → PASS/FAIL evidence) can be run by:
cd ops/iu-core-six-flow-test-readinessSSH_HOST=contabo ./run_six_flow_tests.sh- Inspect
_reports/<latest>/summary.jsonfor the verdict. - Inspect any specific test log for per-step detail.
That is the test-readiness deliverable.
Capability matrix (vs the user's six requested capabilities)
| User capability | Code path | State |
|---|---|---|
| Auto-cut documents | fn_iu_reconstruct_source (read); upstream cut already done |
LIVE_READY |
| Reconstruct by original source order | fn_iu_reconstruct_source — monotonic source_position |
LIVE_READY |
| Axis B (professional) filter | iu_metadata_tag × iu_metadata_tag_registry (tag_kind ∈ axis-B) |
LIVE_READY |
| Parent / child / grandchild filter | fn_iu_subtree (relative_depth ∈ {0,1,2}) |
LIVE_READY |
| Create new document from pieces | fn_iu_compose (with new_piece minting) |
LIVE_READY |
| Add piece | fn_iu_collection_add_piece |
LIVE_READY |
| Remove piece | fn_iu_collection_remove_piece |
LIVE_READY |
| Merge pieces | fn_iu_piece_merge (dry_run + live) |
LIVE_READY (live needs review_decision_id) |
| Split piece | fn_iu_piece_split (dry_run + live) |
LIVE_READY (live needs review_decision_id) |
| Verify trigger in/out per piece | fn_iu_piece_emit_event + lifecycle trigger |
LIVE_READY (dry_run); live-mode flag exists |
| Bridge piece ↔ DB SQL data | iu_sql_link + validator + resolver |
LIVE_READY (outbound); inbound trigger TBD |