docs: consolidate historical records and verify public manual publication

2026-09-15 14:37:29 +02:00
parent 5f3a7f5975
commit 4ff91e8d6e
63 changed files with 633 additions and 6598 deletions
@@ -0,0 +1,53 @@
+# Knowledge archives: consolidated implementation evidence
+
+Consolidated on 15 September 2026 from the M1–M3, E1–E3 and X1 records of 8–9 September.
+This is historical verification evidence, not a claim that these test counts describe today's
+tree or that every installation has passed acceptance. Original commands, detailed outcomes and
+local deployment details remain under `docs/plans/` in Git commit
+`5f3a7f5975b96fae1e1cdd0da08b4d60d41064cc`.
+
+| Increment | Delivered boundary | Recorded verification |
+| --- | --- | --- |
+| M1 | PostgreSQL Memory authority, administration, durable indexing retry | 1,134 harness + 9 portable cases; 17 real PostgreSQL/Qdrant cases; 190 Pi gates; 632 frontend. One backend auth timeout passed its isolated rerun. |
+| M2 | Dense/BM25 recall, scoped links and explicit projection rebuild | 1,152 harness; 78 targeted cases with real embedding; 13 Fastify API cases; 10 wheel/CLI cases. |
+| M3 | Human Memory promotion, receipts and physical-schema dependency cleanup | 1,152 harness + 9 portable; 41 Memory integration, 1 optional embedding skipped, 1 L2 excluded; 195 Pi gates; 635 frontend; 5 Catalog integration. Backend timing case passed isolated rerun. |
+| E1 | Editable file authority and explicit consolidation | 1,180 harness + 9 portable; real Qdrant including optional 35-unit PSD probe. No actual PSD authoring checkout conversion in E1. |
+| E2 | Evidence administration, host CLI and pending activation recovery | 1,355 backend, 639 frontend, 1,248 harness; portable-path rerun passed with THT_HOME unset. Initial authenticated visual acceptance remained manual. |
+| E3 | Draft import, explicit source refresh and protected manual corrections | 1,359 backend, 641 frontend, 1,256 harness; 24 focused checks. Synthetic filesystem/HTTP/S3 behavior, not a live S3-account certification. |
+| X1 | Human-reviewed Memory/Evidence conflict correction and durable recovery | 1,264 harness + 9 portable; 1,366 backend, 645 frontend, 199 Pi gates; desktop/mobile widget probe and later real authenticated administration probe. |
+
+X1's configured `zai/glm-5.3` probe used synthetic conflicting knowledge. It was not a full
+autonomous Pi-session certification or acceptance of PSD semantics. Later administration
+checks exercised real authentication and a disposable synthetic workspace, including persistence
+across backend restart. Existing PSD archive content was not rewritten by those probes.
+
+## Current authorities and repeatable checks
+
+- [Memory implementation and storage](../gestione-memory.md), ADR 0018.
+- [Editable Evidence](../contracts/curated-evidence-v4.md), ADR 0019.
+- [Session corrections](../contracts/archive-repair.md).
+- [Evidence lifecycle acceptance](../testing/evidence-lifecycle-test-plan.md).
+- Harness tests under `tests/memory/`, Evidence integration tests, backend route/service tests,
+  Pi gate tests and frontend tests are the executable regression boundaries. Run portable-path
+  tests without a THT_HOME override; optional L2/provider tests require separate authorization.
+
+Do not equate passing synthetic tests with real-provider quality, live S3 coverage, PSD-domain
+acceptance or permission to migrate another installation. Those remain explicit operator gates.
+
+## Catalog/model design records consolidated at the same time
+
+The old metadata-catalog exploration and description-generation plan/spec are no longer
+current-state authorities. PostgreSQL/Fastify ownership, installation bindings, description
+generation and source-sampling constraints now live in ADRs 0001–0016,
+[architecture](../architecture/overview.md), [Database Management](../operations/database-management.md)
+and the [description acceptance checklist](../testing/2026-08-29-ai-catalog-description-generation-acceptance.md).
+The installation-model plan is replaced by ADR 0013 and the
+[current model catalog guide](../general/pi-configuration.md).
+
+Preserve these outstanding questions rather than infer acceptance from implementation:
+real provider/DWH acceptance recorded by the owner, licensing review of shipped optional models,
+future dialect/multi-schema support, and any desired semantic aliases/value descriptions.
+The former proposed catalog-to-core cutover and separate database permissions are already
+represented by current ADR 0016 and `database.manage`; do not reopen them as unfinished steps.
+The original description-generation plan referred to issue #4 for final delivery gates;
+this consolidation neither changes nor closes its tracker state.