KYE Continuity Profile · v1.0

From authority to continuity.

KYE does not stop at who logged in. It traces who or what acted, on behalf of whom, through which delegation chain, using which capability, under what authority, inside what scope, in what state, and with what evidence. For agentic systems, the next challenge is continuity: preserving the chain between original intent, interpretation, authority, decision, execution and audit.

KYE Continuity Profile helps organisations detect when delegated actions drift from authorised intent, scope, state, oversight or incentive alignment.

1 · What continuity preserves

Ten dimensions, one continuous chain.

KYE Core records the seven dimensions of any authority decision. Continuity preserves three more — intent, interpretation and incentive / pressure context — and binds them all to a single replayable record.

flagIntentDeclared goal, declared_by, constraints, created_at — what the principal asked for, in their own words.
translateInterpretationInterpreted goal, confidence, material_drift_detected — how the agent read the request.
verified_userAuthorityScope match, capability match, delegation chain valid, authority state — the Core binding.
timelineStateSix-dimension state-vector snapshot at decision time.
extensionCapabilityManifest, side-effect level, version — the action surface bound to authority.
priority_highPressureUrgency, coercion, social-engineering signals — was the principal under duress?
paymentsIncentiveOptimisation goal, commercial / affiliate / commission flags — was the agent conflicted?
balanceDecisionContinuity status + checked_dimensions + score (0..1) + obligations.
play_arrowExecutionRequested action, basket hash, amount, execution_state — what the agent then did.
verifiedEvidenceContinuity Evidence Pack — replayable bundle for the whole chain.
2 · What it detects

Ten drift types. Each one signed and audited.

When delegated agency drifts away from the authorised chain, KYE Continuity Profile records a KYEAgencyDriftEvent, signs it, hash-chains it into the audit ledger, and emits a kye.agency_drift.detected signal on KYE Signal Bus.

  • intent_drift — agent reinterpreted the goal materially
  • authority_drift — action no longer matches the grant
  • scope_drift — request exceeds the scope ceiling
  • state_drift — actor / principal / credential state changed mid-flight
  • capability_drift — agent invoked an off-manifest capability
  • execution_drift — execution differs from approved decision
  • incentive_drift — commercial / affiliate conflict surfaced
  • oversight_drift — required human-in-the-loop missed
  • evidence_drift — audit / evidence chain incomplete
  • delegation_drift — sub-delegation broke parent constraints
3 · Schemas (Apache 2.0, public mirror)

Six normative objects. Validated in CI.

Reproduce: git clone https://github.com/KYE-Protocol/schemas && cd schemas && npm ci && npm test

4 · Apps that compose this profile

Five planned apps. Contracts open; engines paid.

verified_userKYE Continuity GatewayRuntime continuity check before execution.
timelineKYE Intent Trace AppSignal → action visualiser.
monitor_heartKYE Agency Drift MonitorDrift detection + alerting.
verifiedContinuity Evidence PackReplayable proof bundle.
account_treeDelegated Agency GraphCross-chain visualisation.
5 · Open / paid boundary

The contracts are open. The engine is paid.

Open under Apache 2.0

  • All v1 schemas above
  • Reason-code dictionaries
  • Webhook event names
  • Sample fixtures + examples
  • Conformance test vectors
  • Validator SDK (TS / Py / Go)
  • Sample MCP read-only tools

Proprietary (commercial licence)

  • KYE Continuity Gateway runtime engine
  • Intent-drift detection algorithm
  • Incentive-conflict scoring engine
  • Pressure-signal analysis engine
  • KYE Agency Drift Monitor (managed)
  • Sector-specific continuity packs
  • BYOC / on-prem deployment