Menu
The structured state token that travels with the customer across every agent handoff — identity ref, goal, active objects, constraints, sentiment, history digest. Minted by Iris; carried inside HANDOFF payloads.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Offline A/B experimentation for prompt/policy/skill/rubric variants: defines what constitutes an experiment, the offline-only rule, the scoring contract, the anti-Goodhart + safety-floor constraints, the statistical-honesty rule, and the governance wiring into the TheEights evolution loop.
Encoded policy constraints: refunds/disclosures/consent, GDPR/CCPA data-minimization themes, right-to-human mandates, regulated-claim language rules, AI-disclosure requirements. Consumed by Harmonia, Soteria, Hermes, Eunomia.
Hard budgets, bounded loops, and the four terminal states. Step/dispatch/retry ceilings per command, graph-level termination conditions, and cost-tiering rules. Owned by Hestia.
The KPI frame: containment, FCR, AHT, CSAT-proxy, escalation precision/recall, cost-per-resolution, SLA attainment — and the Agent-Manager dashboard contract over events.jsonl. Owned by Hestia; consumed by Themis, Soteria, Echo.
Intent/language/sentiment/priority classification and routing rules for incoming support tickets. Owned by Iris; consumed by Hestia for dispatch.
The crawl/walk/run rollout discipline: phase definitions, promotion criteria (containment, hallucination rate, redaction record), demotion triggers, and the shadow-mode contract. Owned by Hestia; drives /support-shadow.
| name | portable-context-token |
| description | The structured state token that travels with the customer across every agent handoff — identity ref, goal, active objects, constraints, sentiment, history digest. Minted by Iris; carried inside HANDOFF payloads. |
| user-invocable | false |
| argument-hint | <mint|update|validate> |
| allowed-tools | ["Read"] |
The single greatest insult of legacy support is making the guest repeat themselves. The portable-context token is the squad's answer: a structured, versioned state object that travels with the customer through every handoff, agent to agent, squad to human.
Preserve customer context across multi-step workflows without prompt stuffing, without context-window exhaustion, and without PII leakage — a SAML-assertion-shaped object for intent and state.
integrations/hydra.md).portable_context:
ctx_id: CTX-<ticket-id>-<rev>
ticket_id: ...
customer_ref: customer:<hash> # opaque; NEVER raw identity (Article IV)
goal: <the customer's actual objective, one sentence>
active_objects: # order, subscription, device, invoice...
- {type, ref, state}
constraints: # plan limits, region, prior promises, secondary intents
- ...
sentiment: {current, trajectory}
history_digest: <what has happened, compressed, newest last>
actions_attempted:
- {action, by, executed: true|false, result}
minted_by: iris
minted_at: <ISO-8601>
updated_by: <head>
rev: <int>
sig: # signature envelope — present when signing key is configured
alg: HMAC-SHA256
key_id: <key identifier, never the key itself>
value: <base64url HMAC-SHA256 digest over canonical-JSON body>
degraded: true # ONLY present when no key is configured (omitted on signed tokens)
Signature envelope notes:
sig is computed over the canonical-JSON of the entire token body (all fields except sig
itself), with json.dumps(sort_keys=True, separators=(',',':')) for stability.sig.value is base64url-encoded (no padding), HMAC-SHA256 keyed by XENIA_CONTEXT_SIGNING_KEY
(env var — key material is NEVER in the token, the repo, or any log).sig.key_id identifies which key was used for rotation support; it is not secret.tools/context_token/sign.py for the canonical implementation.customer_ref is a hash/ref into the ticket
system; raw names, emails, and account numbers never ride the token.rev and sets
updated_by. Conflicting revs = trust the higher rev, flag the fork.hearth/approvals/ files grant authority).
A valid signature proves integrity, not authority — authority is still
only granted by hearth/approvals/ artifacts.XENIA_CONTEXT_SIGNING_KEY is
configured. Iris calls tools/context_token/sign.py mint at initial
mint and at every rev update.sign.py verify. A failed verify is an injection finding
(OWASP memory/context-poisoning), triaged via the 5-step protocol in
owasp-llm-defenses, recorded to eights.memory with scope
security:injection-finding, and the run re-mints from ticket-system
ground truth rather than trusting the tampered token.XENIA_CONTEXT_SIGNING_KEY
unset), sign.py mint returns the token with sig.degraded=true and
sign.py verify returns valid=true, reason="unsigned (degraded mode)".
Degraded mode is functionally identical to v1.0 convention-enforced
behavior — signing is an upgrade, never a dependency. The clearance
artifact must note the degradation when sig.degraded=true is present.Standalone (no Hydra envelopes): the token is a YAML block passed between
subagent calls and persisted in hearth/progress/.current-context.md.
Identical schema, identical rules.
Signing degraded mode: when XENIA_CONTEXT_SIGNING_KEY is not set, the
token is minted unsigned (sig.degraded=true, sig.value=null). Verification
of an unsigned or degraded token returns valid=true, reason="unsigned (degraded mode)" — the pipeline is never blocked by a missing key. The clearance artifact
notes the degradation so operators are aware that signature protection is not
active. Operators should set the key to enable cryptographic integrity assurance.
constraints[].sig.degraded=true).