Provider-neutral contracts
Identity, decisions and scene contracts are provider-neutral, so continuity survives provider changes.
How it works
Humans+ turns interaction into a governed continuity loop. It does not treat each response as an isolated generation.
The model
What happens: the interaction is received and bound to identity, scope, consent and authority. Why it matters: context is not re-explained. What it will not do: it will not act without established authority or consent.
What happens: the Digital Partner's identity and current AMS state are loaded. Why it matters: responses are situated, not cold. What it will not do: it will not treat internal state as external truth or emotion.
What happens: CKPE retrieves authorised evidence and memory; chronology and contradictions are accounted for; scene readiness is assessed. Why it matters: reasoning is grounded, not guessed. What it will not do: it will not treat a negative retrieval as proof beyond its certified scope.
What happens: a bounded scene is composed and routed to an approved model for reasoning. Why it matters: a scene is not a prompt—it is a governed contextual unit. What it will not do: it will not let a model vendor become the Partner's identity.
What happens: output or action is validated against policy and quality gates, delivered, then reflected on to create reviewable memory candidates. Why it matters: growth is governed and attributable. What it will not do: it will not silently drift or act without approval.
The complete continuity loop
These are logical boundaries, not necessarily sequential model calls. Deterministic rules, small models and parallel preparation are preferred where appropriate.
From web, voice, messaging, email, API or another authorised channel.
Boundaries are set before anything else happens.
Who and what is responsible for this work.
Continuity and current internal state.
Account for chronology and contradictions.
Clarify or escalate if the context is not good enough.
Render it for an approved model.
Form a response, plan or decision package.
Without inventing agreement.
Authority, evidence and quality controls.
Only authorised actions execute.
Update internal state and reviewable memory.
Model independence
Model selection is governed by capability, sensitivity, latency, cost, availability, quality and behavioural compatibility. The Partner's identity and decision record stay independent of the model used for any step.
Identity, decisions and scene contracts are provider-neutral, so continuity survives provider changes.
Approved models are routed by capability, policy, risk, cost and availability.
Behavioural compatibility, identity stability and rollback readiness are checked before a model is promoted.
Explore trust by design, or talk to the team about your organisation.