stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 3 Releases Wiki Activity

Publish final search-first correction phases

Browse Source
This commit is contained in:
master
2026-03-07 23:58:48 +02:00
parent c568e09a1d
commit a295841d25
7 changed files with 366 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

78
docs/implplan/SPRINT_20260307_035_DOCS_search_first_final_correction_phases.md Normal file
View File

@@ -0,0 +1,78 @@
# Sprint 20260307-035 - Search First Final Correction Phases
## Topic & Scope
- Turn the latest direct operator feedback into an execution-ready final correction stack for search.
- Lock the product rules for single-entry search, secondary assistant deep-dive, automatic weighting, and executable suggestions only.
- Publish implementation phases that can be shipped and committed independently without re-opening the search model debate.
- Working directory: `docs/`.
- Expected evidence: updated why/how documentation, new phase sprint files, and a docs-only commit.
## Dependencies & Concurrency
- Extends `SPRINT_20260307_031_DOCS_search_operator_correction_phases.md`.
- Extends `SPRINT_20260307_033_AdvisoryAI_search_query_understanding_and_viability.md`.
- Safe parallelism: once this sprint lands, FE and AdvisoryAI work may proceed independently in their owning directories as long as contracts remain additive.
## Documentation Prerequisites
- `docs/modules/ui/search-zero-learning-primary-entry.md`
- `docs/modules/advisory-ai/knowledge-search.md`
- `docs/modules/advisory-ai/unified-search-architecture.md`
- `src/AdvisoryAI/__Tests/INFRASTRUCTURE.md`
## Delivery Tracker
### DOCS-SF-001 - Capture final operator objections as hard product rules
Status: DONE
Dependency: none
Owners: Project Manager, Documentation author
Task description:
- Record the new direct-usage objections explicitly: search and assistant still feeling split, visible scope mechanics still being wrong for the default flow, suggestions failing in practice, and the need for automatic summary when evidence is close.
- State the rules in terms that implementation and QA can enforce, not in aspirational product language.
Completion criteria:
- [x] The why/how doc records the direct operator objections and the final product rules.
- [x] The rules state that search is always the primary entry and assistant is secondary.
- [x] The rules state that surfaced suggestions require ingestion-backed executability proof on supported routes.
### DOCS-SF-002 - Publish final implementation phases with single-directory ownership
Status: DONE
Dependency: DOCS-SF-001
Owners: Project Manager
Task description:
- Create the next phase sprint files for FE shell consolidation, AdvisoryAI answer/ranking proof, and live route verification.
- Each phase must have one owning directory, explicit dependencies, exact tests, and clear completion criteria.
Completion criteria:
- [x] Separate sprint files exist for FE shell consolidation, AdvisoryAI weighting/proof, and live route execution coverage.
- [x] Each sprint defines exact unit/integration/Playwright evidence requirements.
- [x] Safe parallelism notes are explicit.
### DOCS-SF-003 - Keep setup and live-ingestion expectations explicit
Status: DONE
Dependency: DOCS-SF-002
Owners: Documentation author
Task description:
- Make sure the phase stack continues to state that the CLI is not assumed to exist, must be compiled or run from source, and that live suggestion validation is invalid without corpus rebuild.
- Keep the language concise and operator-focused.
Completion criteria:
- [x] The phase stack references the compile-or-source-run CLI guidance already in repo docs.
- [x] Live verification requires corpus rebuild order and route support checks.
- [x] Decisions & Risks reference the updated why/how doc.
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-03-07 | Sprint created to turn direct operator feedback into the final corrective phase stack for search-first self-serve UX. | Project Manager |
| 2026-03-07 | Updated `search-zero-learning-primary-entry.md` with the final operator rules, published the FE/backend/live-route phase sprints, and synced UI/AdvisoryAI task boards. | Project Manager |
## Decisions & Risks
- Decision: search is the single primary entry point; assistant is a secondary deep-dive from search.
- Decision: current-page weighting is automatic product behavior, not a visible user control.
- Decision: suggestions are only acceptable when they are executable against the active ingested corpus on supported routes.
- Risk: prior corrective passes simplified the visible search surface but left shell-level and live-route inconsistencies.
- Mitigation: split the final pass into FE shell consolidation, backend/live-answer hardening, and route-level live proof.
- Reference: `docs/modules/ui/search-zero-learning-primary-entry.md`
## Next Checkpoints
- 2026-03-08: publish final correction phases and land the docs-only commit.
- 2026-03-08: start FE shell consolidation.

87
docs/implplan/SPRINT_20260307_036_FE_search_first_shell_consolidation.md Normal file
View File

@@ -0,0 +1,87 @@
# Sprint 20260307-036 - FE Search First Shell Consolidation
## Topic & Scope
- Finish the search-first shell so the operator perceives one primary workflow: search first, deeper help second.
- Remove leftover shell/search wording and affordances that imply explicit scope control or a separate assistant product.
- Keep the primary result flow automatic: input correction at the top, answer first, supporting results next, assistant only as a deeper follow-up.
- Working directory: `src/Web/StellaOps.Web/`.
- Expected evidence: FE implementation, targeted unit tests, Playwright coverage, and a scoped commit.
## Dependencies & Concurrency
- Depends on `SPRINT_20260307_035_DOCS_search_first_final_correction_phases.md`.
- Informs `SPRINT_20260307_037_AdvisoryAI_search_answer_proof_and_weighting.md`.
- Safe parallelism: backend route-coverage work may proceed in `src/AdvisoryAI/**` if it does not break the FE contract before this sprint lands.
## Documentation Prerequisites
- `docs/modules/ui/search-zero-learning-primary-entry.md`
- `src/Web/StellaOps.Web/AGENTS.md`
## Delivery Tracker
### FE-SF-001 - Consolidate shell language around search-first entry
Status: TODO
Dependency: none
Owners: Developer
Task description:
- Reduce assistant branding in the top-bar search flow, answer panel, and drawer chrome so the operator experiences a single search-first workflow.
- Keep the compact assistant icon beside the search field, but use secondary "details/deeper help" language in the primary surface.
Completion criteria:
- [ ] The top-bar search surface reads as one workflow with a secondary assistant action.
- [ ] Answer-panel and launcher labels no longer imply a competing primary entry model.
- [ ] No search-origin assistant action performs a route jump.
### FE-SF-002 - Make automatic result shaping clearer than mechanics
Status: TODO
Dependency: FE-SF-001
Owners: Developer
Task description:
- Refine the primary result surface so it emphasizes the best local answer, with overflow presented quietly as supporting context.
- Keep `Did you mean` directly below the input and avoid any scope or refinement teaching copy.
Completion criteria:
- [ ] `Did you mean` stays input-adjacent.
- [ ] Overflow is visibly secondary and uses plain operator-facing labels.
- [ ] No recovery/refinement mechanics are rendered in the primary flow.
### FE-SF-003 - Tighten suggestion handling and successful history behavior
Status: TODO
Dependency: FE-SF-002
Owners: Developer
Task description:
- Ensure starter chips react correctly to viability changes and no-result executions.
- Keep history success-only and make the clear-history affordance remain low-emphasis.
Completion criteria:
- [ ] Starter chips disappear when backend viability marks them non-executable.
- [ ] No-result searches never persist into history.
- [ ] The clear-history action remains a discreet icon treatment.
### FE-SF-004 - Verify the shell consolidation paths
Status: TODO
Dependency: FE-SF-003
Owners: Developer, Test Automation
Task description:
- Add targeted Angular and Playwright coverage proving that the shell presents search as the primary path and assistant as a secondary deep-dive.
- Cover suggestion execution and no-result history behavior in the FE surface.
Completion criteria:
- [ ] Angular tests cover updated labels, answer/overflow presentation, and success-only history behavior.
- [ ] Playwright covers search-first entry, assistant launch from search, and suggestion execution on the simplified shell.
- [ ] No visible mode or scope controls appear in covered flows.
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-03-07 | Sprint created for the FE shell consolidation half of the final search-first correction pass. | Project Manager |
## Decisions & Risks
- Decision: assistant remains available but secondary; search is the first-class workflow.
- Decision: current-scope weighting is communicated through answer ordering, not control surfaces.
- Risk: shell-level copy and layout may still imply a separate assistant product even after earlier cleanup.
- Mitigation: change the primary-surface labels and add focused FE regression coverage.
- Reference: `docs/modules/ui/search-zero-learning-primary-entry.md`
## Next Checkpoints
- 2026-03-08: land shell language cleanup and answer/overflow presentation refinements.
- 2026-03-08: land targeted unit and Playwright coverage.

77
docs/implplan/SPRINT_20260307_037_AdvisoryAI_search_answer_proof_and_weighting.md Normal file
View File

@@ -0,0 +1,77 @@
# Sprint 20260307-037 - AdvisoryAI Search Answer Proof and Weighting
## Topic & Scope
- Tighten backend unified search so automatic current-route weighting, overflow suppression, and blended answer composition feel decisive and trustworthy.
- Make suggestion viability and answer usefulness stricter so surfaced search starters do not survive on weak or clarify-only evidence.
- Preserve the rule that telemetry is optional and not part of search correctness.
- Working directory: `src/AdvisoryAI/`.
- Expected evidence: backend implementation, targeted tests, updated docs, and a scoped commit.
## Dependencies & Concurrency
- Depends on `SPRINT_20260307_035_DOCS_search_first_final_correction_phases.md`.
- Depends on `SPRINT_20260307_036_FE_search_first_shell_consolidation.md` for final FE phrasing, but contract work may proceed in parallel if additive.
- Informs `SPRINT_20260307_038_FE_live_search_supported_route_execution_matrix.md`.
## Documentation Prerequisites
- `docs/modules/ui/search-zero-learning-primary-entry.md`
- `docs/modules/advisory-ai/knowledge-search.md`
- `docs/modules/advisory-ai/unified-search-architecture.md`
- `src/AdvisoryAI/AGENTS.md`
## Delivery Tracker
### AI-SF-001 - Strengthen automatic in-scope weighting and overflow suppression
Status: TODO
Dependency: none
Owners: Developer
Task description:
- Tighten route, entity, and recent-action weighting so supported current-page answers win more consistently when the evidence is actually close.
- Keep overflow only when outside-scope evidence still materially improves the answer.
Completion criteria:
- [ ] Service tests cover current-route winners, close-score blends, and suppressed overflow cases.
- [ ] Coverage metadata still explains the winning scope without FE heuristics.
- [ ] Unsupported or weak current-scope corpora do not hide clearly better outside-scope answers.
### AI-SF-002 - Make blended answers and suggestion viability stricter
Status: TODO
Dependency: AI-SF-001
Owners: Developer
Task description:
- Refine context-answer composition so close clusters produce a short grounded blend and dominant results stay decisive.
- Keep suggestion viability grounded-only for surfaced chips and detect unsupported/empty corpora explicitly.
Completion criteria:
- [ ] Blended and dominant answer paths are tested separately.
- [ ] Clarify-only or unsupported suggestions do not pass visible viability.
- [ ] Corpus-readiness states remain explicit in the response contract.
### AI-SF-003 - Preserve optional telemetry and deterministic fallbacks
Status: TODO
Dependency: AI-SF-002
Owners: Developer
Task description:
- Keep analytics and feedback optional without changing search ranking, history semantics, or answer composition.
- Ensure the final correction pass does not reintroduce telemetry coupling.
Completion criteria:
- [ ] Search behavior remains stable with telemetry disabled.
- [ ] Tests cover telemetry-disabled search and suggestion flows.
- [ ] Docs state clearly that telemetry is optional infrastructure.
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-03-07 | Sprint created for the backend weighting and suggestion-proof half of the final search-first correction pass. | Project Manager |
## Decisions & Risks
- Decision: search answer shape is inferred, not selected by the operator.
- Decision: suggestion executability requires grounded evidence on supported routes.
- Decision: telemetry remains optional and separate from correctness.
- Risk: stricter viability may suppress too many starters unless corpus readiness is modeled accurately.
- Mitigation: add route-support and corpus-readiness test coverage instead of guessing in FE.
- Reference: `docs/modules/ui/search-zero-learning-primary-entry.md`
## Next Checkpoints
- 2026-03-09: land tighter weighting/blending tests and stricter suggestion gating.
- 2026-03-09: verify telemetry-disabled behavior remains unchanged.

77
docs/implplan/SPRINT_20260307_038_FE_live_search_supported_route_execution_matrix.md Normal file
View File

@@ -0,0 +1,77 @@
# Sprint 20260307-038 - FE Live Search Supported Route Execution Matrix
## Topic & Scope
- Prove that surfaced search suggestions and answer paths work end to end on the supported live routes, not only on Doctor.
- Treat corpus rebuild, route support, and suggestion executability as release gates for the search-first UX.
- Expand Playwright verification across findings, policy, VEX, and the existing Doctor coverage where ingestion supports them.
- Working directory: `src/Web/StellaOps.Web/`.
- Expected evidence: live Playwright coverage, setup-proof docs when needed, and a scoped commit.
## Dependencies & Concurrency
- Depends on `SPRINT_20260307_035_DOCS_search_first_final_correction_phases.md`.
- Depends on `SPRINT_20260307_036_FE_search_first_shell_consolidation.md` and `SPRINT_20260307_037_AdvisoryAI_search_answer_proof_and_weighting.md`.
- Safe parallelism: deterministic FE-only tests may evolve independently as long as the live matrix assertions remain additive.
## Documentation Prerequisites
- `docs/modules/ui/search-zero-learning-primary-entry.md`
- `docs/modules/advisory-ai/knowledge-search.md`
- `src/AdvisoryAI/__Tests/INFRASTRUCTURE.md`
- `src/Web/StellaOps.Web/AGENTS.md`
## Delivery Tracker
### QA-SF-001 - Add supported-route live preflight and corpus readiness checks
Status: TODO
Dependency: none
Owners: Test Automation
Task description:
- Extend the live Playwright harness so it verifies route support and corpus readiness before the UI assertions begin.
- Fail fast on empty or unsupported corpora instead of letting dead suggestions surface as flaky UI failures.
Completion criteria:
- [ ] Live tests verify the rebuild order and supported-route readiness before UI assertions.
- [ ] Unsupported routes are skipped explicitly, not treated as passing suggestion coverage.
- [ ] Empty corpora fail the suite clearly.
### QA-SF-002 - Execute surfaced suggestions on supported routes
Status: TODO
Dependency: QA-SF-001
Owners: Test Automation
Task description:
- For each covered live route, open the search surface, capture the surfaced starter chips, execute them, and verify grounded or materially useful results.
- Cover assistant handoff from the grounded answer path as part of the same journey.
Completion criteria:
- [ ] Every surfaced starter on covered live routes is executed in Playwright.
- [ ] The route-level suite verifies grounded answers or visible useful cards, not just non-empty DOM.
- [ ] Assistant handoff keeps the current page context.
### QA-SF-003 - Keep deterministic shell regression aligned with live proof
Status: TODO
Dependency: QA-SF-002
Owners: Developer, Test Automation
Task description:
- Update deterministic Playwright coverage so the simplified shell behavior and the live-route behavior assert the same product rules.
- Keep the suites readable and route-specific rather than one monolithic soak.
Completion criteria:
- [ ] Deterministic and live suites assert the same search-first product rules.
- [ ] Covered routes include at least Doctor plus every additional supported ingested route.
- [ ] The execution log records exact commands and results.
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-03-07 | Sprint created for the supported-route live suggestion execution matrix in the final search-first correction pass. | Project Manager |
## Decisions & Risks
- Decision: suggestion coverage is invalid unless the live corpus is rebuilt and non-empty.
- Decision: supported-route proof is part of search release quality, not an optional smoke test.
- Risk: some routes may not yet have enough ingested corpus support to sustain live suggestion coverage.
- Mitigation: preflight route support explicitly and suppress unsupported suggestions in product code.
- Reference: `docs/modules/ui/search-zero-learning-primary-entry.md`
- Reference: `src/AdvisoryAI/__Tests/INFRASTRUCTURE.md`
## Next Checkpoints
- 2026-03-09: land live preflight and supported-route route matrix scaffolding.
- 2026-03-10: execute the first full live supported-route suggestion pass.