docs: audit post-notification production state
CI / test (push) Successful in 11s
CI / test (pull_request) Successful in 11s

This commit is contained in:
m
2026-08-16 19:48:37 +03:00
parent 759328972a
commit 760f671077
5 changed files with 74 additions and 17 deletions
+6 -4
View File
@@ -21,8 +21,10 @@ Status is based on executed repository tests and Docker-stack verification on 20
Foundation V1 is eligible for freeze. Creator session authentication was also completed as DEV-000019 and does not carry Authority.
Post-foundation product work is intentionally separate:
The three original post-foundation gates are complete:
1. Choose and specify the first real external operation before adding a production Executor credential.
2. Build Creator API/UI only through validated Identity, Authority and Commit boundaries.
3. Add exact diff-to-task scope comparison to promotion CI when the first Git baseline exists.
1. `ADR-0005` specifies the first real external operation, prospective notification delivery.
2. DEV-000024 through DEV-000032 and DEV-000040 through DEV-000043 provide the authenticated Creator API/UI and external operation only through the validated Identity, Authority, Continuity, Capability and Commit boundaries.
3. `ADR-0004` and ARCH-000004 implement exact diff-to-task scope comparison.
DEV-000044 re-ran local architecture/unit checks and the production Creator-to-receiver smoke on 2026-08-16. The deployed stack and Windows operational tasks were healthy. Current product status and explicitly uncommitted future scope are recorded in `docs/PROJECT_STATUS.md`.
+28
View File
@@ -0,0 +1,28 @@
# Assistant project status
Audit date: 2026-08-16. Active audit: DEV-000044 revision 3.
## Delivered
- Foundation V1 is frozen and all exit criteria pass.
- The single Creator account authenticates at `https://assistent.cin.su`; authentication does not imply Authority.
- Creator can inspect the bounded operational view, register and satisfy Continuity prospective items, inspect action history, and explicitly request the accepted notification operation.
- `deliver-prospective-notification-v1` executes only through Capability binding, current Authority and Commit/Executor validation. Its success evidence is an immutable receiver receipt.
- Production runs on `docker.cin.su`; the project does not use the shared test Docker host.
- PostgreSQL backup/restore, encrypted off-host backup, production health monitoring and the current-user Windows notification projection are installed and healthy.
## Evidence from DEV-000044
- `go test ./...`, `go vet ./...`, architecture preflight/checks and PowerShell parsing pass.
- `Test-DomovoyProductionHealth.ps1` reports `healthy` for the production stack, HTTPS/DNS/TLS, backups and registered Windows tasks.
- `tests/creator_commit/verify-remote.ps1` passes the authenticated Creator → Commit → notification receiver receipt flow on `docker-prod`.
- The smoke harness was corrected to preserve HTTP Authorization headers under Windows PowerShell 5.1 native-command argument handling.
## Remaining work requiring a new task decision
1. **Artifact provenance:** running images expose Compose image digests but no OCI Git revision label, and Go build metadata reports the module as `(devel)`. Operational behavior is verified, but the source revision of an already-running image cannot be independently proven from that image alone. A deployment task should stamp the immutable Git revision and record the promoted image digests.
2. **Cognitive provider:** the cognitive worker intentionally remains the deterministic fake. Selecting a real model/provider, data policy and allowed proposal contract requires a separate capability/architecture decision; it must not gain canonical mutation authority.
3. **Product breadth:** notification delivery is the only accepted real external operation. Any additional operation needs its own proposal, authority model, idempotency/reconciliation semantics and Capability binding.
4. **Artifact and Epistemics product behavior:** their ownership boundaries exist, but no product task has yet specified durable user-facing workflows for them.
These are explicit scope decisions, not hidden incomplete steps in DEV-000043. No production secret is stored in the repository.