This commit is contained in:
@@ -0,0 +1,22 @@
|
||||
# Credentials and secrets
|
||||
|
||||
## Git
|
||||
Remote is fixed to `https://git.cin.su/m/Assistant.git`.
|
||||
|
||||
The repository can be read externally, but a push may require authentication. First let normal Git credential helpers handle authentication. Do not add username/password to the remote URL.
|
||||
|
||||
If authentication is not already configured, ask the user for either:
|
||||
- a Gitea personal access token with the minimum repository scope, or
|
||||
- username + token/password if their local setup requires it.
|
||||
|
||||
Never store it in Git.
|
||||
|
||||
## Portainer
|
||||
Target is `https://docker.cin.su`.
|
||||
|
||||
Preferred automation credential: `PORTAINER_API_KEY` supplied outside Git. `PORTAINER_ENDPOINT_ID` may also be required after environment discovery.
|
||||
|
||||
Do not guess Portainer credentials and do not search other project source trees for literal passwords. Existing OS/environment secret stores may be used without revealing values.
|
||||
|
||||
## Production services
|
||||
Each privileged runtime gets only its required secret/capability bindings. `commit-runtime` is intentionally isolated from the general Core Runtime.
|
||||
@@ -0,0 +1,17 @@
|
||||
# Deployment V1
|
||||
|
||||
Target control plane: Portainer at `https://docker.cin.su`.
|
||||
|
||||
Recommended V1 deployment topology:
|
||||
- `assistant-core-runtime`
|
||||
- `assistant-continuity-runtime`
|
||||
- `assistant-commit-runtime` (isolated privileged runtime)
|
||||
- `assistant-cognitive-worker` (replaceable, no canonical ownership)
|
||||
- PostgreSQL 18.6
|
||||
- NATS as replaceable integration transport
|
||||
|
||||
Temporal is intentionally **not** the canonical owner of future obligations. If/when Temporal is added, loss of Temporal must be recoverable from canonical continuity state.
|
||||
|
||||
The initial stack definition is `deploy/docker-compose.prod.yml`. Portainer may deploy it from Git after the repository has been pushed.
|
||||
|
||||
Credentials/API deployment automation is deliberately not embedded. Use `PORTAINER_API_KEY` from an external secret source or deploy through Portainer UI/API after authenticating.
|
||||
@@ -0,0 +1,28 @@
|
||||
# Foundation Exit audit — V1
|
||||
|
||||
Status is based on executed repository tests and Docker-stack verification on 2026-08-16.
|
||||
|
||||
| Criterion | Status | Evidence / gap |
|
||||
|---|---|---|
|
||||
| Cold agent can use repository artifacts | PASS | `AGENTS.md`, architecture documents, versioned task packets and `devctl preflight`. |
|
||||
| Cross-owner DB write denied | PASS | `tests/owner_acl/verify.ps1` proves `continuity_role` cannot write `work.tasks`. |
|
||||
| Wrong-project mutation rejected | PASS | focus isolation tests and the remote WS-004 guarded commit harness. |
|
||||
| Stale/revoked authority rejected | PASS | action-commit tests and live HTTP 409 checks in DEV-000017. |
|
||||
| Duplicate/replay side effect prevention | PASS | isolated Test Executor applies by ActionIntentID once, injects lost ACK, and reconciles without mutation. |
|
||||
| Future obligation survives engine loss | PASS | prospective-memory recovery and reproducible remote Continuity restart harness. |
|
||||
| No-LLM continuity | PASS | DEV-000014 stopped cognitive worker while Core, Continuity and Commit remained available. |
|
||||
| Two process topologies | PASS | in-process suites plus `tests/topology_equivalence/verify-remote.ps1` for extracted runtimes. |
|
||||
| Provider swap/fake | PASS | deterministic cognitive fake has no canonical mutation authority. |
|
||||
| Declared/observed architecture | PASS | strengthened sentinel checks declared contract dependencies and implementation imports; discovered Commit→Identity drift was removed. |
|
||||
| Semantic migration drill | PASS | Capability Health V1→V2 migration, rejection of V3 and projection rebuild. |
|
||||
| Guardrails negative tests | PASS | negative self-tests cover infrastructure imports, cross-module implementation imports, undeclared contracts, protected-path task authority, and live DB ACL denial. |
|
||||
|
||||
## Foundation conclusion
|
||||
|
||||
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:
|
||||
|
||||
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.
|
||||
@@ -0,0 +1,11 @@
|
||||
# Local project and private resources
|
||||
|
||||
Expected local root on the user's workstation:
|
||||
|
||||
`Z:\mst\codex\assistent`
|
||||
|
||||
These are user-controlled resources:
|
||||
- Git: `https://git.cin.su/m/Assistant.git`
|
||||
- Portainer: `https://docker.cin.su`
|
||||
|
||||
Do not hardcode drive `Z:` into application semantics. It is a development/workspace locator only.
|
||||
@@ -0,0 +1,9 @@
|
||||
# Semantic migrations
|
||||
|
||||
## Capability Health V1 to V2
|
||||
|
||||
`007_capability_health_v2.sql` assigns existing rows semantic version `1` without inventing an observation time. V2 writers must explicitly provide a positive `observed_at_unix_millis`; unsupported versions are rejected by the owner domain validator.
|
||||
|
||||
Forward fix: deploy the migration before the V2 runtime, then rebuild `capability.health_projection` through `POST /v1/capabilities/health-projection/rebuild`.
|
||||
|
||||
Rollback: retain the migrated canonical rows and run the prior runtime only against V1 rows. A V2 row must not be silently read by an older runtime; use a forward-fix deployment to restore a V2-capable reader.
|
||||
Reference in New Issue
Block a user