fy59/lardon3d
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
lardon3d/prompt/31_IMPLEMENTATION_ORDER.md

1.8 KiB
Raw Blame History

31 — Implementation Order

Status

IMPLEMENTATION_ORDER=DEPENDENCY_DRIVEN
IMPLEMENTATION_AUTHORIZATION=NO
STEP_0_USER_FACING_LANGUAGE_NORMALIZATION=PASS
CURRENT_NEXT=1_CALIBRATION_WORKFLOW_COORDINATOR

Authority

docs/product/product_definition.md, current roadmap and dependencies confirmed on current main.

PLANNED ORDER

Implementation remains unauthorized until the human explicitly authorizes a tranche.

Default dependency order:

  1. user-facing repository/UI language normalization where appropriate — PASS;
  2. final usable calibration workflow — IN PROGRESS; current next sub-boundary: workflow coordinator;
  3. dedicated physical calibrated real campaign;
  4. real Sparse SfM proof;
  5. durable Dense/OpenMVS orchestration;
  6. mesh / refinement / texturing / export;
  7. viewer foundation;
  8. offline Coverage Analysis scientific contract and implementation;
  9. multi-campaign registration / fusion;
  10. generic live acquisition adapter foundation;
  11. A6000 HDMI integration;
  12. S21 integration;
  13. live camera localization;
  14. live coverage overlay;
  15. actionable Capture Guidance;
  16. video ingestion / deterministic keyframes;
  17. final integration, UX, restart and performance proof;
  18. Product Definition v1 Definition-of-Done closure.

Adjustment rule

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.