feat(confidence-engine): promote focused learning on done
This commit is contained in:
@@ -1651,3 +1651,38 @@ Refer to existing context documents before making architectural decisions:
|
||||
- `docs/current-working-principles.md` — axiomatic principles anchor.
|
||||
- `docs/Confidence_Engine_Return_to_Origin_Methodology_Context_2026-08-18.md` — RTO methodology.
|
||||
- `docs/methodology-checkpoint-return-to-origin.md` — repository-facing checkpoint summary.
|
||||
|
||||
---
|
||||
|
||||
## Canonical Playwright Investigation (v0.49 live run 2026-08-28)
|
||||
|
||||
### Scenario:
|
||||
E-commerce checkout abandonment
|
||||
|
||||
Situation text: "Our e-commerce checkout page has a high abandonment rate of 72%. Users report confusion about shipping costs appearing only at the final step."
|
||||
|
||||
Mobile defects: overlapping buttons and tiny text fields.
|
||||
|
||||
### Purpose:
|
||||
Longitudinal live UI verification for current Confidence Engine increments — specifically focused → global Finding handoff and Done-for-now promotion behavior.
|
||||
|
||||
### Identity:
|
||||
E-commerce checkout abandonment scenario (72% rate + late shipping disclosure + mobile UX defects). Distinguished from the product-launch enterprise-customer scenario used in v0.48 experiments.
|
||||
|
||||
### Canonical focused thread:
|
||||
"Relative contribution of delayed shipping cost disclosure versus mobile UI defects to the overall abandonment rate, as these are presented as distinct dimensions affecting user behavior"
|
||||
Target node: `n58lwnx`
|
||||
|
||||
### Current minimum live state (post-run):
|
||||
- focusedContributions: 1
|
||||
- findings: 3 (all originatingTargetNodeId = n58lwnx, userDisposition = null)
|
||||
- promoted Current Understanding: YES (includes Evidence citation from eligible Findings)
|
||||
- Done-for-now promotion verified: YES
|
||||
|
||||
### Live-test policy:
|
||||
- reuse this investigation for subsequent Playwright checks on this branch;
|
||||
- confirm scenario identity before every live run (inspect localStorage["confidence-engine-investigation"] + rendered Current Understanding);
|
||||
- do not silently continue against another scenario;
|
||||
- do not create a fresh scenario unless an experiment explicitly requires one;
|
||||
- if this investigation is absent, report TEST-STATE MISSING rather than diagnosing persistence failure;
|
||||
- structural/relative assertions only for LLM output — no exact prose dependency.
|
||||
|
||||
Reference in New Issue
Block a user