Markitect boundary and reuse tests

This commit is contained in:
2026-05-05 19:41:32 +02:00
parent 9f1b8da87a
commit ef8391e6a7
15 changed files with 490 additions and 6 deletions

View File

@@ -36,6 +36,14 @@ and policy checks described in `docs/architecture-blueprint.md`. Search indexes
and ranking backends are adapters; they must not define the stable query or
result contracts.
## markitect-tool Boundary Remark
For Markdown-backed assets, retrieval adapters may use Markitect selectors,
extraction helpers, local index concepts, and context-package source spans to
produce grounded units and snippets. Engine retrieval contracts, result
envelopes, policy filtering, pagination, feedback, and cross-format search
remain engine-owned.
## R7.1 - Implement query contracts pagination sorting and result envelopes
```task
@@ -149,6 +157,8 @@ Acceptance:
- Results explain why they were returned and where they originated.
- Snippets are permission filtered.
- Retrieval packages are suitable for later grounded answer generation.
- Markdown snippets can reference Markitect selector matches or context-package
spans as adapter provenance.
## R7.7 - Capture retrieval feedback and KPI measurement hooks