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

2.6 KiB
Raw Blame History

31 — Implementation Order

Status

IMPLEMENTATION_ORDER=DEPENDENCY_DRIVEN
IMPLEMENTATION_AUTHORIZATION=NO
STEP_0_USER_FACING_LANGUAGE_NORMALIZATION=PASS
CURRENT_NEXT=CALIBRATION_V2_HETEROGENEOUS_CALIBRATION_PUBLICATION

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 Science/Tooling/Bootstrap/Workflow v1 compatibility path — PASS/FROZEN;
  3. Calibration Science v2 design for heterogeneous cameras/lenses/focals, adaptive capture settings and autofocus — PASS/FROZEN;
  4. Calibration v2 heterogeneous-optics persistence foundation — PASS/FROZEN;
  5. Heterogeneous calibration publication / Tooling / Bootstrap evolution — CURRENT;
  6. physical autofocus/optical applicability validation and dedicated calibrated real campaign;
  7. real Sparse SfM proof;
  8. durable Dense/OpenMVS orchestration;
  9. mesh / refinement / texturing / export;
  10. viewer foundation;
  11. offline Coverage Analysis scientific contract and implementation;
  12. multi-campaign registration / fusion;
  13. generic live acquisition adapter foundation;
  14. A6000 HDMI integration;
  15. S21 integration;
  16. live camera localization;
  17. live coverage overlay;
  18. actionable Capture Guidance;
  19. video ingestion / deterministic keyframes;
  20. final integration, UX, restart and performance proof;
  21. 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.

The calibration-v2 insertion before the physical campaign is dependency-driven, not feature creep: real acquisition evidence established that the v1 locked-focus single-optical-state path would make normal engine-bay capture impractical and would contradict the already-FROZEN product requirement for multiple optical configurations per project. Science v2 must be defined before collecting the physical evidence intended to validate it.