Architecture blueprint and workplan refinement

This commit is contained in:
2026-05-05 19:19:41 +02:00
parent 228b397fc5
commit 9f1b8da87a
10 changed files with 539 additions and 1 deletions

View File

@@ -44,6 +44,9 @@ The strongest implementation wedge is:
- Treat identity, provenance, permission checks, audit, and structured errors as
P0 infrastructure, not enterprise-only additions.
- Use `docs/architecture-blueprint.md` as the implementation shape for domain
core, application services, ports, adapters, persistence, retrieval,
workflow, service APIs, and agent-safe operation.
- Separate source, normalized, and derived representations.
- Keep transformations traceable to inputs, versions, parameters, actor, policy,
and output artifacts.
@@ -57,7 +60,7 @@ The strongest implementation wedge is:
| Workplan | Role | Primary Coverage |
| --- | --- | --- |
| `KONT-WP-0004` | Architecture rebase | Resolve open product/architecture decisions and publish V0.2 traceability. |
| `KONT-WP-0004` | Architecture rebase | Establish the blueprint, resolve open product/architecture decisions, and publish V0.2 traceability. |
| `KONT-WP-0005` | Asset registry core | Stable identity, source/normalized/derived forms, metadata, permissions, audit, durable state. |
| `KONT-WP-0006` | Ingestion core | Jobs, connectors, extractors, local files, markdown, PDFs, office docs, datasets, normalization. |
| `KONT-WP-0007` | Retrieval core | Query contracts, lexical search, filters, context graph retrieval, permission-aware results, snippets, KPIs. |