docs: preserve domain-independent facilitator principles

This commit is contained in:
2026-08-19 18:39:35 +01:00
parent 85204f96ac
commit 601e46e4b7
5 changed files with 167 additions and 8 deletions
+8 -4
View File
@@ -141,18 +141,22 @@ The next phase starts from the workspace/methodology question, not from a presel
### Required methodology-continuity context (read first)
> **Before continuing any Confidence Engine reasoning development, load this document:**
> **Before continuing any Confidence Engine reasoning development, load these in order:**
>
> `docs/Confidence_Engine_Return_to_Origin_Methodology_Context_2026-08-18.md`
> 1. `docs/current-working-principles.md` §0 (Axiomatic Principles A1A12)
> 2. `docs/Confidence_Engine_Return_to_Origin_Methodology_Context_2026-08-18.md`
This is the durable methodology anchor. It covers:
**The axiomatic principles in current-working-principles.md are now the durable methodological anchor.** They codify delivery-platform independence, meaning-over-dictionary reasoning, user-directed non-linear investigation, provisional closure, and progressive disclosure. All future work must be evaluated against these 12 axioms.
The RTO methodology context document covers:
- What Confidence Engine is (reasoning method, not software or LLM)
- What it is not
- The granular answer-fragment hypothesis (working — not architecture)
- RTO.1417 learning and why they did not define the next architecture
- The memory/graph separation principle
- Memory/graph separation principle
- Optional capability: "Help me answer" / "Answer for me"
- Methodology test for future development
- Recent experimental evidence (RTO.18, RTO.20RTO.22) supporting durable principles
**Do not begin reasoning development from the latest experiment apparatus.** Always load this methodology continuity context first. Without it, a new session will reconstruct the project from recent technical experiments and lose sight of the method the application is meant to embody.