Files
Assistant/docs/PROJECT_STATUS.md
m d0255558e2
CI / test (push) Successful in 12s
CI / test (pull_request) Successful in 12s
feat: add creator advisory console
2026-08-16 20:15:47 +03:00

2.9 KiB

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. 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.
  2. 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.
  3. Artifact and Epistemics product behavior: their ownership boundaries exist, but no product task has yet specified durable user-facing workflows for them.

DEV-000045 closes the DEV-000044 artifact-provenance finding for new promotions by stamping the merged Git revision into OCI labels, recording exact promoted image IDs outside the repository, and making production monitoring reject label or digest drift. Images that predate DEV-000045 remain historically unverifiable from the image alone.

ADR-0006 and DEV-000046 establish the provider-neutral, non-canonical Creator advisory boundary. DEV-000048 connects it to authenticated Creator Web and adds the advisory console; until a provider/data-egress decision is accepted, it deliberately reports PROVIDER_UNAVAILABLE and sends nothing outside the private runtime topology.

These are explicit scope decisions, not hidden incomplete steps in DEV-000043. No production secret is stored in the repository.