robbond/confidence-engine
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: clarify Confidence Engine context authority

Browse Source
This commit is contained in:
robbond
2026-08-19 11:49:30 +01:00
parent 5b43c1b8f9
commit a12f9555af
5 changed files with 99 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.claude/project-context.md
+37 -10
View File
@@ -19,6 +19,18 @@ It:
6. updates the graph from the answer;
7. repeats until action is justified or the remaining uncertainty is clear.
> **NOTE:** The flow above describes historical/current implementation mechanics.
> It does not represent current Confidence Engine methodology direction.
> See `docs/Confidence_Engine_Return_to_Origin_Methodology_Context_2026-08-18.md`
> for the current working hypothesis (granular answer-fragment inquiry).
The linear selector-led flow described above is a **historical capability**, not
an automatic architecture to continue. Under Return-to-Origin:
- The Engine facilitates inquiry; it does not compel a single-question route.
- The user owns which unresolved investigation/question to pursue.
- Accumulated reasoning memory does not necessarily belong inside repeated LLM calls.
A chatbot remembers the conversation.
The Confidence Engine preserves the state of the reasoning.
@@ -50,15 +62,23 @@ The engine should help a user reach one of these states:
## Current development stage
The deterministic reasoning architecture reached a stable alpha checkpoint.
> **Version lineage note:** The Confidence Engine uses two distinct version
> lineages that must not be conflated:
> - **Reasoning-engine experimental lineage** (v0.8+): reasoning-fidelity,
> investigation-state assessment, semantic selectors — under RTO pause.
> - **UX/product development lineage** (v0.7): workspace layout, user views,
> loading feedback — also paused.
> These are independent tracks; do not assume they describe one product version.
Current work is primarily improving:
The deterministic reasoning architecture reached a stable alpha checkpoint
(reasoning-engine v0.8). UI/product work reached v0.7 staging. Both have
paused under Return to Origin while the granular answer-fragment hypothesis
is evaluated as working methodology context.
- usability;
- presentation;
- loading feedback;
- plain-language explanations;
- separation of user and developer views.
Current work is paused. The next step begins from the methodology question:
given the useful investigation structure the Engine can already derive, how
should that structure be surfaced so a person can see, choose, defer, and
return to open questions while the Engine continues to guide their thinking?
Do not resume broad reasoning architecture work unless a repeated observed
failure clearly requires it.
@@ -93,7 +113,11 @@ The interface should minimise cognitive load by presenting the current state fir
The engine may contain hundreds of reasoning nodes; the user should only see the information required to take the next meaningful action.
## Why workspace layout matters (v0.7)
## Why workspace layout matters (v0.7 — UX/product lineage)
> **This section documents paused UX design intent.** It belongs to the v0.7
> product development lineage, not the reasoning-engine lineage. UI work is
> currently paused under Return to Origin.
This phase optimises for simultaneous visibility instead of sequential scrolling.
Related panels — Understanding alongside Investigation Map, Situation alongside History — can appear side-by-side on wide screens while mobile continues to stack everything vertically. The reasoning engine is completely unaware of these changes; only the presentation layer is affected.
@@ -104,7 +128,10 @@ Read `docs/current-working-principles.md` for current guidance. Treat `docs/arch
For UI mock work, read `docs/ui-mock-reference.md`. Do not load
`docs/archive/deferred-ux-backlog.md` unless a named past UX idea is being reviewed.
Engine and UI experiments are paused. First file to inspect when resuming:
`docs/current-project-state.md`, then `docs/project-knowledge-inventory.md`.
Engine and UI experiments are paused under Return to Origin. First file to inspect when resuming:
**`docs/current-handoff.md`** (methodology continuity anchor), then `docs/current-project-state.md`, then `docs/project-knowledge-inventory.md`.
> After reading `docs/current-project-state.md`, choose the relevant minimal pack from `docs/task-context-packs.md`. Do not combine packs unless a specific task genuinely crosses boundaries.
>
> **Historical experiment families are evidence to load only when a specific question requires them; they are not default architecture context.**