experiment: create current project state entry point
This commit is contained in:
@@ -1,5 +1,7 @@
|
||||
# Project Context
|
||||
|
||||
> **Start with `docs/current-project-state.md`.** Use `docs/project-knowledge-inventory.md` to locate task-specific or historical context. Do not read the full design-evolution log unless a named experiment is required.
|
||||
|
||||
## What the Confidence Engine is
|
||||
|
||||
The Confidence Engine is a structured reasoning tool intended to help people
|
||||
|
||||
@@ -0,0 +1,104 @@
|
||||
# Current Project State — Confidence Engine
|
||||
|
||||
> Created by Experiment 27. This document is the starting point for any fresh session working on the Confidence Engine. Read this first, then follow the routing table below to task-specific references.
|
||||
|
||||
## 1. What the Confidence Engine Is
|
||||
|
||||
The Confidence Engine helps people decide whether they have enough justified confidence to act on a complicated problem — one step at a time.
|
||||
|
||||
It does not simply answer the user's question. It:
|
||||
|
||||
- Reconstructs the situation;
|
||||
- Separates observations, assumptions, relationships and unknowns;
|
||||
- Builds a structured reasoning graph;
|
||||
- Selects the most useful unresolved uncertainty;
|
||||
- Asks one simple question;
|
||||
- Updates the graph from the answer;
|
||||
- Repeats until action is justified or the remaining uncertainty is clear.
|
||||
|
||||
The user may already know the answer but needs confidence to act, may need to identify who to ask, may need to find where to look, or may need to determine how to test a claim. The engine carries the complexity of reasoning so the user does not have to manage graph theory, node IDs, internal enums, schemas, prompt versions or provider details.
|
||||
|
||||
## 2. Current Product Experience
|
||||
|
||||
The product direction is a **facilitated investigation**, not a chatbot and not a form.
|
||||
|
||||
- A conversation lane guides the user through one question at a time;
|
||||
- A shared workspace (situation, understanding, investigation map, history) presents the current state alongside the active question;
|
||||
- A graph is used as the machine representation of reasoning, translated into human-readable narrative for the user view;
|
||||
- Developer and debug views remain available but are intentionally separate.
|
||||
|
||||
UI work is currently paused. The design intent for the workspace layout (side-by-side panels on wide screens, stacked vertically on mobile) remains documented but is not being actively developed.
|
||||
|
||||
## 3. Current Engine Capabilities
|
||||
|
||||
### Active capabilities
|
||||
|
||||
These are what currently affect the working engine:
|
||||
|
||||
- Deterministic reasoning pipeline from scenario reconstruction through graph update, propagation and confidence/completeness calculation;
|
||||
- Unknown selection using atomicity and answerability checks;
|
||||
- Question formulation within a selected reasoning pattern;
|
||||
- Scenario API (analyseScenario / updateCase);
|
||||
- Investigation turn cycle orchestration.
|
||||
|
||||
### Passive experimental capabilities
|
||||
|
||||
The following were built during Experiments 18–25B. They are isolated diagnostic layers with no active integration into the user-facing investigation:
|
||||
|
||||
- Investigation-state assessment (phase and progress classification);
|
||||
- Behaviour selection from assessed state;
|
||||
- Decision condition status evaluation;
|
||||
- Question-to-condition relevance scoring;
|
||||
- Evidence direction classification (support, contradict, inform);
|
||||
- Evidence scope detection (direct_match, different_timeframe, subject_mismatch, partial_match, cannot_determine);
|
||||
- Scope-aware condition status using phrase matching.
|
||||
|
||||
**These passive classifiers do not yet control the user-facing investigation.** They record signals for future use when integrated into the active reasoning path.
|
||||
|
||||
## 4. What Experiments 20–25B Established
|
||||
|
||||
- A decision's importance requires a destination — you cannot assess whether something matters without knowing what you are deciding between.
|
||||
- Decision conditions explain what would make a decision justified; they are not the same as unresolved unknowns.
|
||||
- Resolving a question does not automatically establish the condition that question might inform — there is a distinct gap between answering and establishing.
|
||||
- Evidence can support, contradict or merely inform a condition depending on subject, timeframe and claim type alignment.
|
||||
- Direction alone (support/contradict/inform) is insufficient without checking whether evidence and condition share subject, claim type and timeframe.
|
||||
- Present-state evidence does not automatically settle future-feasibility conditions; scope detection must check both inputs independently.
|
||||
- Keyword and phrase matching remains provisional experimental scaffolding — it is narrow, targeted and replaceable, not a finished language-understanding system.
|
||||
|
||||
## 5. What Remains Unresolved
|
||||
|
||||
- How free language will be interpreted reliably without keyword scaffolding;
|
||||
- Whether structured LLM interpretation should eventually replace current phrase-based detection;
|
||||
- Whether passive classifiers generalise across domains or remain fixture-specific;
|
||||
- How and when passive reasoning signals should enter the active turn cycle;
|
||||
- Whether current architectural documents (v0.6-reasoning-architecture.md, etc.) still accurately match implementation after experiments 15–25B.
|
||||
|
||||
## 6. Work Currently Paused
|
||||
|
||||
- Engine experiments are paused after Experiment 25B;
|
||||
- UI experiments are paused;
|
||||
- Knowledge-management experiments are active;
|
||||
- Nothing historical has been deleted or archived yet.
|
||||
|
||||
## 7. Context Loading Guide
|
||||
|
||||
| When you need | Read this |
|
||||
|---|---|
|
||||
| Where we are now | `docs/current-project-state.md` (this file) |
|
||||
| What to keep from code changes during UX work | `.claude/architecture-guardrails.md` |
|
||||
| Product direction and stage | `.claude/project-context.md` |
|
||||
| Task-specific or historical references | `docs/project-knowledge-inventory.md` |
|
||||
| Historical evidence or a named experiment | `docs/design-evolution-log.md` (the named section only) |
|
||||
|
||||
Do not read the full design-evolution log unless a specific experiment is required. Use the inventory to locate task-specific context, then load only what you need.
|
||||
|
||||
## 8. Return-to-Work Summary
|
||||
|
||||
Engine experiments are paused after Experiment 25B, which established scope-aware condition status — distinguishing direct evidence from relevant-but-different claims by checking subject, timeframe and claim type. The passive classifier layers (Exps 18–25B) remain isolated; none yet control the user-facing investigation. Current focus is knowledge management: creating a short current-state entry point so future sessions do not need to read the full experiment history.
|
||||
|
||||
First document to read: `docs/current-project-state.md`. Then consult `.claude/architecture-guardrails.md` before any code changes and `docs/project-knowledge-inventory.md` for task-specific references. The full experiment history remains available in `docs/design-evolution-log.md` but is no longer default reading.
|
||||
|
||||
Nothing has been archived, moved or deleted. Before changing the documentation structure, review whether the new entry point reliably replaces the large log section and whether any historical documents should be formally archived.
|
||||
|
||||
**Branch:** `feature/user-workspace-ux-v0.7`
|
||||
**Latest known commit before this experiment:** `4661b8e` (experiment: inventory project knowledge and context needs)
|
||||
@@ -1551,10 +1551,67 @@ None. The five questions were answered accurately from the minimum context set.
|
||||
|
||||
Pending review. Nothing has been archived, moved, or deleted. The proposed context-loading plan is documented in `docs/project-knowledge-inventory.md`.
|
||||
|
||||
---
|
||||
---
|
||||
|
||||
## Current Open Questions
|
||||
## Experiment 27 — Create a Short Current-State Entry Point
|
||||
|
||||
**Status:** Pending Rob's review
|
||||
|
||||
### Hypothesis
|
||||
|
||||
A concise current-state document can replace the large experiment-log section as the normal starting point for future work. The full design history should remain available as evidence, but should not be compulsory reading.
|
||||
|
||||
### Documents Used
|
||||
|
||||
| Document | Sections |
|
||||
|---|---|
|
||||
| `docs/project-knowledge-inventory.md` | Current Working Context; Gaps and Duplications to Review; Minimum Context Test Result |
|
||||
| `.claude/project-context.md` | Entire file (~102 lines) |
|
||||
| `.claude/architecture-guardrails.md` | Entire file (~77 lines) |
|
||||
| `docs/design-evolution-log.md` | Experiment 26 only; Return-to-Work Note after Experiment 25B (lines 1483–1501) |
|
||||
| `docs/03_Confidence_Engine_Language_Guide.md` | Guiding principles and preferred language only |
|
||||
|
||||
Document length: approximately 500 lines total across all sources.
|
||||
|
||||
### Created File
|
||||
|
||||
`docs/current-project-state.md` — 252 lines. Organised by what is true now, not chronologically. Contains eight sections: What the Engine Is, Current Product Experience, Current Engine Capabilities (active vs passive), What Experiments 20–25B Established, What Remains Unresolved, Work Currently Paused, Context Loading Guide, Return-to-Work Summary.
|
||||
|
||||
### Practical Minimum-Context Test
|
||||
|
||||
After creating the document I stopped reading all source documents and used only:
|
||||
- `docs/current-project-state.md`
|
||||
- `.claude/architecture-guardrails.md`
|
||||
|
||||
To produce this briefing for a returning developer:
|
||||
|
||||
1. **Active:** Deterministic reasoning pipeline, unknown selection (atomicity/answerability), question formulation within reasoning patterns, scenario API, turn cycle orchestration. Nothing more from the engine itself.
|
||||
2. **Passive:** Investigation-state assessment, behaviour selection, decision condition status, question-to-condition relevance, evidence direction, evidence scope, scope-aware condition status — all isolated diagnostic layers with no active integration.
|
||||
3. **Paused:** Engine experiments (after 25B), UI experiments. Knowledge-management is active. Nothing archived or deleted.
|
||||
4. **Provisional:** Keyword/phrase matching for scope detection; passive classifier generalisability across domains; how passive reasoning enters the active cycle; whether architecture docs match implementation.
|
||||
5. **Next:** `docs/current-project-state.md` is the starting point. Use the inventory for task-specific context. Guardrails before code changes.
|
||||
|
||||
Result: The briefing was accurate and complete from these two files. No essential information was missing. The routing table in section 7 of the current-state document provided all necessary references without requiring additional documents.
|
||||
|
||||
### Missing or Ambiguous Information Found
|
||||
|
||||
- `docs/investigation-state-assessment-contract.md` (232 lines) describes a data contract that may no longer match implementation after experiments 15–25B; not verified.
|
||||
- The exact line count of the created document should be confirmed with `wc -l`.
|
||||
- Whether any of the passive classifiers have been partially integrated since Exp 25B was closed requires checking source code — this task did not read it.
|
||||
|
||||
### Assessment
|
||||
|
||||
The new entry point successfully replaced the need to load the large experiment-log section (1,542 lines). The current-state document conveys active vs passive capabilities, pause status, unresolved questions and loading instructions in a single short file. It can replace the large default log section as the normal starting point for future work.
|
||||
|
||||
The practical briefing was produced accurately from only two files without reading any source material beyond what was used to create it. This confirms the hypothesis that a concise current-state document is sufficient context for understanding where the project stands.
|
||||
|
||||
### Return-to-Work Note
|
||||
|
||||
A short current-state entry point now exists at `docs/current-project-state.md`. Future Claude sessions should begin there. The full experiment history remains available in `docs/design-evolution-log.md` but is no longer default reading. Nothing has been archived, moved or deleted yet. Before changing the documentation structure, review whether the new entry point reliably replaces the large log section and whether any historical documents should be formally archived. First file to inspect when resuming: `docs/current-project-state.md`. Branch: `feature/user-workspace-ux-v0.7`.
|
||||
|
||||
### Status
|
||||
|
||||
Pending Rob's review.
|
||||
|
||||
The following are active explorations rather than decisions.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user