Architecture blueprint and workplan refinement

workplans/KONT-WP-0004-knowledge-operations-architecture.md

@@ -31,6 +31,8 @@ workflow state, exportability, and agent-safe operation from the start.
 ## Outputs
 
 - Updated scope and roadmap documentation.
+- `docs/architecture-blueprint.md` as the architecture baseline for the V0.2
+  implementation sequence.
 - Architecture decision notes for the P0 capability baseline.
 - Traceability from PRD/FRS V0.2 requirements to implementation workplans.
 - Revised implementation sequence for `KONT-WP-0005` through `KONT-WP-0010`.
@@ -188,12 +190,17 @@ Acceptance:
 
 - `SCOPE.md` reflects the V0.2 knowledge operations vision.
 - `docs/knowledge-operations-roadmap.md` maps PRD/FRS areas to workplans.
+- `docs/architecture-blueprint.md` defines the implementation shape and review
+  checklist.
 - `README.md` points to the new research and roadmap materials.
 
 ## Definition Of Done
 
 - Architecture docs clearly distinguish engine, application, connector,
   provider, and domain-package responsibilities.
+- Architecture docs define domain core, application service, port, adapter,
+  persistence, retrieval, workflow, policy, audit, service API, export, and
+  agent-safe operation boundaries.
 - Workplans `KONT-WP-0005` through `KONT-WP-0010` exist and are linked to State
   Hub.
 - `python3 -m pytest` passes.

workplans/KONT-WP-0005-asset-registry-governance-state.md

@@ -30,6 +30,13 @@ FR-140 to FR-145, FR-240 to FR-245.
 
 Supporting: FR-180 to FR-182, FR-200 to FR-201.
 
+## Architecture Constraint
+
+Implement this slice through the domain core, application services, repository
+ports, policy port, audit port, and SQLite/in-memory adapters described in
+`docs/architecture-blueprint.md`. The asset registry must not depend on HTTP,
+source connectors, document extractors, search backends, or AI providers.
+
 ## G5.1 - Implement stable asset identity and source references
 
 ```task
@@ -170,4 +177,6 @@ Acceptance:
 - Asset lifecycle tests cover create, retrieve, update, retire, delete request,
   metadata changes, permission checks, audit events, and durable reload.
 - New models map to the V0.2 FRS vocabulary.
+- The implemented package shape follows `docs/architecture-blueprint.md` or
+  documents any deliberate deviation.
 - `python3 -m pytest` passes.

workplans/KONT-WP-0006-multi-format-ingestion-normalization.md

@@ -30,6 +30,13 @@ Primary: FR-020 to FR-030.
 Supporting: FR-001 to FR-008, FR-022 to FR-028, FR-200 to FR-202,
 FR-240 to FR-244.
 
+## Architecture Constraint
+
+Implement ingestion through connector and extractor ports described in
+`docs/architecture-blueprint.md`. Format-specific parsing, local filesystem
+access, `markitect-tool`, PDF/document libraries, and dataset readers must live
+behind adapters, not in the domain core.
+
 ## I6.1 - Implement ingestion job model status and retry surface
 
 ```task
@@ -168,4 +175,5 @@ Acceptance:
 - Local file, text, markdown, PDF/document placeholder, and dataset ingestion
   scenarios are covered by tests.
 - Job status and provenance are inspectable through programmatic APIs.
+- Connector and extractor boundaries follow `docs/architecture-blueprint.md`.
 - `python3 -m pytest` passes.

workplans/KONT-WP-0007-governed-retrieval-context-graph.md

@@ -29,6 +29,13 @@ Primary: FR-040 to FR-050 and FR-060 to FR-071.
 
 Supporting: FR-120 to FR-126, FR-143 to FR-146, FR-163, FR-200 to FR-204.
 
+## Architecture Constraint
+
+Implement retrieval through retrieval services, search ports, repository ports,
+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.
+
 ## R7.1 - Implement query contracts pagination sorting and result envelopes
 
 ```task
@@ -167,4 +174,6 @@ Acceptance:
 - Retrieval tests cover text, metadata, lifecycle, relationship, contextual
   entity, pagination, permission, snippet, and feedback behavior.
 - Retrieval does not bypass policy or source provenance.
+- Search, relationship, and context retrieval contracts follow
+  `docs/architecture-blueprint.md`.
 - `python3 -m pytest` passes.

workplans/KONT-WP-0008-transformations-workflow-jobs.md

@@ -30,6 +30,13 @@ Primary: FR-080 to FR-090 and FR-100 to FR-110.
 Supporting: FR-083 to FR-085, FR-106, FR-144 to FR-145, FR-165,
 FR-200 to FR-202.
 
+## Architecture Constraint
+
+Implement transformations and workflows through operation registries, workflow
+services, repository ports, event ports, policy checks, and audit events
+described in `docs/architecture-blueprint.md`. Execution may start embedded,
+but contracts must allow later queue or workflow-engine adapters.
+
 ## O8.1 - Implement transformation operation registry
 
 ```task
@@ -167,4 +174,6 @@ Acceptance:
 - Transformations and workflows produce inspectable run records and audit
   events.
 - Derived artifacts are persistent, governed, and lineage-linked.
+- Transformation and workflow run models follow
+  `docs/architecture-blueprint.md`.
 - `python3 -m pytest` passes.

workplans/KONT-WP-0009-service-api-agent-safe-operation.md

@@ -31,6 +31,13 @@ Primary: FR-160 to FR-169 and FR-180 to FR-188.
 Supporting: FR-060 to FR-066, FR-080 to FR-085, FR-100 to FR-106,
 FR-120 to FR-126, FR-200 to FR-202, FR-240 to FR-245.
 
+## Architecture Constraint
+
+Implement the service API as an adapter over application services, following
+`docs/architecture-blueprint.md`. HTTP routes must not own domain behavior.
+Agent operations must use the bounded operation catalog, policy checks, audit
+events, dry-run behavior, and review gates described in the blueprint.
+
 ## S9.1 - Implement versioned FastAPI service skeleton and health contracts
 
 ```task
@@ -169,4 +176,6 @@ Acceptance:
 - The service API exposes the MVP operation surface without requiring UI.
 - Agent-safe operations are explicit, bounded, permissioned, auditable, and
   reviewable.
+- API routes remain adapters over the core contracts described in
+  `docs/architecture-blueprint.md`.
 - `python3 -m pytest` passes.

workplans/KONT-WP-0010-observability-export-enterprise-readiness.md

@@ -31,6 +31,13 @@ Primary: FR-200 to FR-207 and FR-220 to FR-225.
 Supporting: FR-183 to FR-188, FR-127 to FR-132, FR-070, FR-166 to FR-168,
 FR-240 to FR-245.
 
+## Architecture Constraint
+
+Implement observability, export, events, webhooks, and recovery through the
+ports, services, audit model, and export package model described in
+`docs/architecture-blueprint.md`. Export and observability must preserve policy
+checks and must not require direct storage access.
+
 ## E10.1 - Expose operational metrics events and job inspection
 
 ```task
@@ -176,4 +183,6 @@ Acceptance:
 - Operators can inspect, diagnose, recover, export, and evaluate MVP engine
   behavior through supported surfaces.
 - Export packages preserve enough context for inspection and migration.
+- Observability, events, recovery, and export follow
+  `docs/architecture-blueprint.md`.
 - `python3 -m pytest` passes.