diff --git a/docs/roadmap/roadmap.md b/docs/roadmap/roadmap.md index 74792cb..52e9cc7 100644 --- a/docs/roadmap/roadmap.md +++ b/docs/roadmap/roadmap.md @@ -22,7 +22,9 @@ Real A6000 Dense/MVS NOT EXECUTED DOCUMENTATION_FINDING_REMEDIATION PASS SOURCE_COMMENT_AUDIT PASS PRODUCT_DEFINITION PASS/FROZEN -PROMPT_TREE NEXT +PROMPT_TREE CURRENT +USER_FACING_UI_LANGUAGE_NORMALIZATION PASS +CURRENT_NEXT FINAL_USABLE_CALIBRATION_WORKFLOW ``` The current Project DB head is additive: @@ -523,38 +525,43 @@ No calibration component silently turns metadata into scientific calibration. The current repository-maintenance sequence is: ```text -Documentation Inventory Audit PASS_WITH_FINDINGS -Documentation Finding Remediation PASS -Source Comment Audit PASS -Source Comment Remediation PASS -Product Definition v1 PASS/FROZEN --> prompt.md / prompt/ contract tree NEXT --> implementation only after explicit human authorization +Documentation Inventory Audit PASS_WITH_FINDINGS +Documentation Finding Remediation PASS +Source Comment Audit PASS +Source Comment Remediation PASS +Product Definition v1 PASS/FROZEN +Prompt execution contract tree CURRENT +User-facing UI/control normalization PASS +-> final usable calibration workflow CURRENT NEXT +-> each implementation tranche requires explicit human authorization ``` -This work is documentation and contract preparation. +The repository contract phase is complete and the implementation cursor has moved to the final usable calibration workflow. -It does not authorize: +This cursor does not itself authorize: - scientific threshold changes; - new Project DB schema versions; - new Task kinds; -- Sparse SfM execution; +- real Sparse SfM execution; - Dense/MVS execution; - Viewer implementation; - live-capture implementation; - Capture Guidance implementation. +Those boundaries require their own explicitly authorized tranche when reached. + ## Scientific next dependency -After documentation/product-definition work, the next real scientific dependency for a new -known-calibration campaign is a dedicated physical calibration acquisition that satisfies -Calibration Science v1. +The current implementation dependency is the final usable calibration workflow around the already acquired Calibration Science / Tooling / Bootstrap boundaries. + +The first new real scientific evidence after that workflow exists is a dedicated physical calibration acquisition that satisfies Calibration Science v1. The dependency order is: ```text -dedicated physical calibration acquisition +final usable calibration workflow +-> dedicated physical calibration acquisition -> external solver evidence -> Calibration Tooling v1 -> L3DCALB1 v1 @@ -606,8 +613,9 @@ configuration and optional SSD controls. The canonical repository and UI language is English. -The remaining non-English executable UI strings are remediation work and must be changed only in an -explicitly scoped UI-language pass. +The direct TUI/control surface and user-facing project/import/catalog/runtime-session messages have completed their scoped English normalization and validation pass. + +Historical persisted labels, path names and deliberate UTF-8 fixtures remain unchanged where translation would alter historical meaning or test purpose. Persistence-sensitive/internal diagnostics are changed only in an explicitly owned scope rather than by mechanical repository-wide replacement. The TUI remains ncurses/main-thread owned according to its canonical contract. diff --git a/prompt/02_CURRENT_FROZEN_STATE.md b/prompt/02_CURRENT_FROZEN_STATE.md index e6b0086..23e79f7 100644 --- a/prompt/02_CURRENT_FROZEN_STATE.md +++ b/prompt/02_CURRENT_FROZEN_STATE.md @@ -5,6 +5,8 @@ ```text CURRENT_PROJECT_DB_SCHEMA=v25 PRODUCTION_TASK_KINDS=16 +USER_FACING_UI_LANGUAGE_NORMALIZATION=PASS +CURRENT_IMPLEMENTATION_CURSOR=1_FINAL_USABLE_CALIBRATION_WORKFLOW ``` ## Authority @@ -21,6 +23,7 @@ Visual Index IMPLEMENTED Candidate Pair IMPLEMENTED Matcher IMPLEMENTED TUI operational observatory VALIDATED +User-facing TUI/control language PASS External SSD controller VALIDATED Calibration Solver Preflight v1 PASS ``` diff --git a/prompt/17_TUI.md b/prompt/17_TUI.md index f56bf1d..0960379 100644 --- a/prompt/17_TUI.md +++ b/prompt/17_TUI.md @@ -5,6 +5,7 @@ ```text TUI=PRIMARY_CONTROL_SURFACE USER_INTERFACE_LANGUAGE=ENGLISH +USER_FACING_TUI_LANGUAGE_NORMALIZATION=PASS ``` ## Authority @@ -60,7 +61,9 @@ Diagnostics must distinguish at least: A generic unowned `failed` state is insufficient for final-product workflows. -Remaining non-English executable UI text converges to English only in explicitly scoped implementation work. +Direct TUI/control labels and the user-facing project/import/catalog/runtime-session surface have been normalized to English and validated. + +Historical persisted labels, path names and deliberate UTF-8 test fixtures are not renamed merely to satisfy a text scan. Internal subsystem diagnostics are not to be mechanically rewritten across FROZEN or persistence-sensitive boundaries; any diagnostic intentionally exposed to the final user-facing product must converge to English when its owning subsystem is explicitly scoped. ## Canonical-reference rule diff --git a/prompt/27_TESTS_VALIDATION.md b/prompt/27_TESTS_VALIDATION.md index 01012ef..3d9640a 100644 --- a/prompt/27_TESTS_VALIDATION.md +++ b/prompt/27_TESTS_VALIDATION.md @@ -28,6 +28,8 @@ For each tranche: Do not claim blanket TSan validity for Vulkan unless explicitly proven. +Historical schema downgrade fixtures must be structurally truthful. A fixture targeting schema version N must remove every schema object introduced after N before rewriting `schema_version`; changing metadata alone is not a valid historical fixture. In particular, v25-aware downgrade fixtures must account for the additive v24 `raw_development_batch_tasks` and v25 `feature_extract_batch_tasks` overlays when targeting earlier versions. + Do not rerun full historical A-to-Z qualification merely for confidence theater. ## Canonical-reference rule diff --git a/prompt/31_IMPLEMENTATION_ORDER.md b/prompt/31_IMPLEMENTATION_ORDER.md index ce3780f..97ddb63 100644 --- a/prompt/31_IMPLEMENTATION_ORDER.md +++ b/prompt/31_IMPLEMENTATION_ORDER.md @@ -5,6 +5,8 @@ ```text IMPLEMENTATION_ORDER=DEPENDENCY_DRIVEN IMPLEMENTATION_AUTHORIZATION=NO +STEP_0_USER_FACING_LANGUAGE_NORMALIZATION=PASS +CURRENT_NEXT=1_FINAL_USABLE_CALIBRATION_WORKFLOW ``` ## Authority @@ -17,8 +19,8 @@ Implementation remains unauthorized until the human explicitly authorizes a tran Default dependency order: -0. remaining repository/UI language normalization where appropriate; -1. final usable calibration workflow; +0. user-facing repository/UI language normalization where appropriate — PASS; +1. final usable calibration workflow — CURRENT NEXT; 2. dedicated physical calibrated real campaign; 3. real Sparse SfM proof; 4. durable Dense/OpenMVS orchestration; @@ -40,4 +42,6 @@ Default dependency order: Change this order only when current repository inspection proves a real dependency difference. Preserve product intent and document the dependency. +Step 0 closure does not authorize mechanical rewriting of historical persisted labels, path names, deliberate UTF-8 fixtures or persistence-sensitive internal strings. Such text is changed only when its owning scope requires it. + Do not jump to A6000 live work merely because it is visually interesting. Reconstruction/viewer/coverage foundations required for truthful guidance come first.