Status. Proposed design only. Nothing in this vault is DG client approval. No application, service or test has been executed; every scenario is Not executed. Fees and dates are open.
Step 05 · Discovery and rule ranking
Goal. Search, filters and one transparent rule ranking.
Not started. This is a specification; no code has been written. The primary-step mapping is an index, not proof that each full scenario can be completed in its step: see Dependency-and-Regression-Table.
Prerequisites
Step 04 (published versions). Policy-independent scaffolding may start only after the overall start conditions are met (statement of work, ready-to-start kickoff checklist, funded DG-owned accounts, region and identity provider chosen). Decision-dependent behaviour and its final oracle stay blocked until DG chooses the applicable rule. Proposed defaults are recommendations, never prerequisites. Any provisional synthetic exploration must be labelled reversible and unapproved and is not accepted production behaviour. Blocked until DG decides: required constraints, weights, ties and unknown-data behaviour (Q03). Policy-independent here: search and filter plumbing and eligibility-before-ranking.
Changes (illustrative, not a final schema)
Search, filter and rule-ranking logic over eligible published versions; evidence and gap explanations.
Build items:
- Eligibility before ranking and before counts/pagination
- Deterministic rule version with fixed ties
- Evidence and gap explanation; unknown is not contradiction
- No AI; no deal-probability language
Expected outputs and invariants
Eligibility is applied before ranking, counts and pagination; ties are deterministic; unknown data is a gap, not a contradiction.
Tests-first subset
Primary scenarios of this step (write these tests first): T06, T07.
Assertions to write first: T06, T07; the discovery side of T05, T08.
Method: make one meaningful test fail for the expected reason, implement the minimum behaviour, refactor without changing the observable contract. A scenario whose decision is still pending stays Pending decision; no oracle is invented.
Deferred integration checks
Scenarios whose primary step is this one but whose full variants need later components:
- None: the scenarios of this step can be completed here.
Follow-up verification brought here
Earlier scenarios that can only be completed or rechecked once this step exists:
- T05 — Discovery by search and filters completes it.
- T08 — Search and detail rendering after approval.
- T21 — Recommendation refresh (05), EOI keeping V1 (06) and the safe change alert (07) complete it.
- T22 — Needs recommendations (05), EOI submission (06) and duplicate worker jobs (07).
- T27 — Applies entity by entity as drafts, search results and conversations are built.
- T39 — Core screens exist only after those steps; measured at step 10 on the integrated build.
Decisions DG must settle (dependent behaviour stays blocked until DG chooses)
Exit evidence
Permitted-ID sets and counts exact on the named build; T05 and T08 can now be exercised end to end; T21 and T22 recommendation refresh is available to test.
Evidence is recorded only for a named build and fixture. A software scenario is not recorded as Passed until all its relevant variants have been exercised on a named integrated build (step 11).
Navigation: Step-04-Opportunities-Versions-Approvals ← this step → Step-06-Questions-Interest-Discussions-Actions · Implementation-Order-Overview