docs: checkpoint return to Confidence Engine origin

2026-08-18 08:33:05 +01:00
parent 55b7551739
commit 8339b6849a
3 changed files with 380 additions and 0 deletions
@@ -125,3 +125,20 @@ The override was produced by fixed `actor_match` keyword scoring: node n65sgyd's
 **What this establishes:** On fresh Start calls, deterministic keyword signals can override model-inferred investigation priority when node labels differ in dictionary-match patterns. The final investigation target is not the model's contextual judgment but the highest-scoring candidate under fixed scoring rules.

 **What this does NOT prove:** Whether the deterministic selection is better or worse than the model's suggestion; consistency across scenario types; or downstream investigation quality impact.
+
+
+---
+
+## RETURN-TO-ORIGIN CHECKPOINT
+
+**selector-led compulsory next-question optimisation is PAUSED**
+
+**semantic-selector replacement is also PAUSED**
+
+Recent work is preserved as valuable experimental learning. The graph/reconstruction/decomposition/invariant work remains potentially reusable. No replacement architecture has been selected.
+
+The next phase starts from the workspace/methodology question, not from a preselected technical solution.
+
+See:
+- `docs/methodology-checkpoint-return-to-origin.md` — repository-facing checkpoint summary
+- `docs/Confidence_Engine_Return_to_Origin_Methodology_Context_2026-08-18.md` — full methodology context (source)