DEV-000061 checkpoint interaction chat foundation
CI / test (push) Failing after 10s
CI / test (pull_request) Failing after 11s

This commit is contained in:
m
2026-08-17 14:10:04 +03:00
parent e4b6121dc0
commit 41154be211
26 changed files with 1376 additions and 8 deletions
@@ -0,0 +1,19 @@
# ADR-0009 — Human Interaction canonical owner
Status: Accepted
Date: 2026-08-17
Accepted under: DEV-000061 rev.1A Creator decision
## Decision
`interaction` is the narrow canonical owner for `Conversation`, `HumanUtterance`, typed `SpeechAct`, immutable/versioned `OriginalHumanIntent`, interpretation revisions, correction relations, and interaction provenance. It is transport-neutral; `WEB_CHAT` is its first channel.
Interaction stores actor/session/identity-assurance references but does not own authentication or identity truth. It does not own Claims, Evidence, Observations, Beliefs, Work state, Authority, Commit, provider selection, model state, generic memory, or general Artifacts. Assertions may be proposed to Epistemics but never become verified fact automatically. Directives remain non-executable proposals and must use existing Authority/Commit paths.
Raw content is an immutable Interaction-owned bounded payload in V1; `ContentRef` permits a later Artifact migration without historical rewrite. Conversation only references Situation/Work context and cannot contain their state. Corrections append a new utterance/relation; historical messages are never rewritten.
Questions may use only the provider-neutral Cognitive Gateway/Router. Cognitive output is advisory and cannot mutate canonical state. Interaction has no provider-specific import or credential.
## Consequences
A dedicated `interaction` schema/role and typed contracts are added. No cross-owner SQL join, FK, direct write, privilege escalation, provider activation, or automatic action is introduced.
@@ -0,0 +1,26 @@
# ADR-0010 - CredentialRef Secret Resolution
Status: Accepted
Date: 2026-08-17
Accepted under: DEV-000061 rev.2 Creator scope decision
## Decision
Long-lived runtime credentials are represented in canonical configuration as typed `CredentialRef` metadata, never as plaintext secret values. A trusted runtime resolves a `CredentialRef` through a provider-neutral Secret Resolver into a secret value stored in a protected Secret Backend.
The V1 backend is the existing protected local secret storage exposed to trusted runtimes as files under an explicitly configured root such as `/run/secrets`. This is bootstrap delivery, not canonical live configuration. The resolver is technical platform infrastructure and owns no domain meaning, provider state, model state, authority, or Interaction semantics.
Docker environment variables may carry minimal bootstrap references, such as a credential reference id or an allowed secret file path, but Docker environment is not the long-term canonical configuration store for Domovoy. Operational concepts such as provider endpoints, model bindings, routing configuration, health, project settings, capability configuration, and runtime policy must remain movable toward canonical registries without redeploy.
## Boundaries
- Plaintext secrets, API keys, tokens and passwords remain forbidden in source, task packets, logs, tests and ordinary environment configuration.
- Secret-file references are allowed only through typed resolver policy and fail closed outside the protected backend root.
- Canonical owners store `CredentialRef` metadata and policy only; the secret value stays in the Secret Backend.
- The resolver is not Interaction-specific and must be reusable by other trusted runtime consumers.
- Cognitive models receive no plaintext secret unless a future explicitly authorized operation requires it.
## Consequences
DEV-000061 may connect `interaction_role` by creating a CredentialRef and resolving it from the protected V1 local backend. This adds a minimal `platform/secrets` mechanism and typed `contracts/secrets` contract without introducing Vault, Kubernetes secrets, HSM, distributed replication, secret management UI, automatic rotation, PKI, or cluster scheduling.
+13 -3
View File
@@ -141,6 +141,13 @@
"may_depend_on": [
"contracts.identity"
]
},
"interaction": {
"id": "mod.interaction",
"owns": ["Conversation", "HumanUtterance", "UtteranceInterpretation", "OriginalHumanIntent", "InteractionRelation"],
"database_schema": "interaction",
"boundary_class": "remote_capable",
"may_depend_on": ["contracts.identity", "contracts.situation", "contracts.cognitive", "platform.ids", "platform.events"]
}
},
"platform": {
@@ -150,7 +157,8 @@
"platform.outbox",
"platform.inbox",
"platform.telemetry",
"platform.errors"
"platform.errors",
"platform.secrets"
],
"rule": "platform owns mechanisms, never domain meaning"
},
@@ -162,7 +170,8 @@
"work",
"epistemics",
"capability",
"artifact"
"artifact",
"interaction"
]
},
"continuity_runtime": {
@@ -197,7 +206,8 @@
"continuity": "continuity_role",
"capability": "capability_role",
"commit": "commit_role",
"artifact": "artifact_role"
"artifact": "artifact_role",
"interaction": "interaction_role"
},
"cross_owner_fk": "forbidden_by_default",
"cross_owner_write": "forbidden",
+10 -1
View File
@@ -68,6 +68,13 @@ modules:
boundary_class: remote_capable
may_depend_on: [contracts.identity]
interaction:
id: mod.interaction
owns: [Conversation, HumanUtterance, UtteranceInterpretation, OriginalHumanIntent, InteractionRelation]
database_schema: interaction
boundary_class: remote_capable
may_depend_on: [contracts.identity, contracts.situation, contracts.cognitive, platform.ids, platform.events]
platform:
allowed_packages:
- platform.ids
@@ -76,11 +83,12 @@ platform:
- platform.inbox
- platform.telemetry
- platform.errors
- platform.secrets
rule: "platform owns mechanisms, never domain meaning"
runtime_topology_v1:
core_runtime:
modules: [identity, situation, work, epistemics, capability, artifact]
modules: [identity, situation, work, epistemics, capability, artifact, interaction]
continuity_runtime:
modules: [continuity]
commit_runtime:
@@ -102,6 +110,7 @@ storage_topology_v1:
capability: capability_role
commit: commit_role
artifact: artifact_role
interaction: interaction_role
cross_owner_fk: forbidden_by_default
cross_owner_write: forbidden
cross_owner_application_join: forbidden