Assistant/docs/PROJECT_STATUS.md

Assistant project status

Audit date: 2026-08-16. Active implementation: DEV-000053 revision 1.

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.

DEV-000049 adds and executes a repeatable production audit for that boundary. It proves that an authenticated 16 KiB message reaches only the deterministic unavailable binding, unauthenticated and browser-supplied authority fields fail closed, the request sentinel is absent from cognitive-worker logs, and the cognitive worker has no database, Commit/Executor, Creator or provider credential environment/mount.

ADR-0007 accepts OpenAI Responses API with immutable snapshot gpt-5.4-mini-2026-03-17 and Mode A per-request retention disclosure as the first real provider binding class. DEV-000050 implements its standard-library adapter and adversarial fake-transport tests: fixed origin/payload, message-only egress, no tools or provider memory, redirect/proxy denial, no retry, strict output mapping and fail-closed timeout/refusal/unavailable/invalid states. The adapter is not wired into the runtime; production remains on deterministic-fake with no provider credential or egress.

DEV-000051 adds an optional cognitive-worker runtime gate for that adapter. It is disabled when OPENAI_API_KEY_FILE is absent, rejects direct environment credentials, bounds and validates the secret file, and returns 503 before parsing an OpenAI request while disabled. Production configuration and Creator Web routing are unchanged, so the gate is not active and no provider egress occurs.

DEV-000052 promotes the disabled gate without adding a credential, mount or provider environment variable. DEV-000053 adds the server-selected Creator Web routing policy: deterministic behavior remains the default, while the accepted OpenAI Mode A route can only be selected by server configuration and requires a fresh per-request egress acknowledgement. The browser receives authenticated binding metadata for disclosure but cannot select the provider, model or binding. The message and acknowledgement are not persisted.

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