KYE™ Continuity Profile™ · v1.0

From authority to continuity.

Your data, your keys, your evidence — even if we disappear. Open schemas. Open verifier. Bring-your-own KMS.

Apply for pilot →Read the docs

Continuity Profile, point by point

Demo data

You learn: The page's points, one at a time. You can: Step through them.

  1. Step 1 of 8

    KYE Protocol™

    intent_drift

    agent reinterpreted the goal materially

  2. Step 2 of 8

    KYE Protocol™

    authority_drift

    action no longer matches the grant

  3. Step 3 of 8

    KYE Protocol™

    scope_drift

    request exceeds the scope ceiling

  4. Step 4 of 8

    KYE Protocol™

    state_drift

    actor / principal / credential state changed mid-flight

  5. Step 5 of 8

    KYE Protocol™

    capability_drift

    agent invoked an off-manifest capability

  6. Step 6 of 8

    KYE Protocol™

    execution_drift

    execution differs from approved decision

  7. Step 7 of 8

    KYE Protocol™

    incentive_drift

    commercial / affiliate conflict surfaced

  8. Step 8 of 8

    KYE Protocol™

    oversight_drift

    required human-in-the-loop missed

How this widget is built
Demonstrates
KYE Protocol™
Components
  • The points this page makes
Flow
Each point in order, as the page sets it out. Architecture diagram
Used on

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

Plain take

Plain take

Your data. Your keys. Your proof. Even if we vanish.

  • Open schemas. Open verifier. Open vocab.
  • Bring your own KMS.
  • Bring your own object store.
  • Bring your own auditor.

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.

Intent

Declared goal, declared_by, constraints, created_at — what the principal asked for, in their own words.

Interpretation

Interpreted goal, confidence, material_drift_detected — how the agent read the request.

Authority

Scope match, capability match, delegation chain valid, authority state — the Core binding.

State

Six-dimension state-vector snapshot at decision time.

Capability

Manifest, side-effect level, version — the action surface bound to authority.

Pressure

Urgency, coercion, social-engineering signals — was the principal under duress?

Incentive

Optimisation goal, commercial / affiliate / commission flags — was the agent conflicted?

Decision

Continuity status + checked_dimensions + score (0..1) + obligations.

Execution

Requested action, basket hash, amount, execution_state — what the agent then did.

Evidence

Continuity 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: curl -fsSL https://kyeprotocol.com/schemas/policy-decision.json | jq '."$id"'

4 · Apps that compose this profile

Five planned apps. Contracts open; engines paid.

What it is. Why it matters. What to do next.

KYE™ Continuity Gateway™

Runtime continuity check before execution.

KYE™ Intent Trace App™

Signal → action visualiser.

KYE™ Agency Drift Monitor™

Drift detection + alerting.

Continuity Evidence Pack™

Replayable proof bundle.

Delegated Agency Graph

Cross-chain visualisation.

5 · Open / paid boundary

The contracts are open. The engine is paid.

One sentence: a signed, replayable proof of decision.

Request the procurement pack →Protocol overviewDiscoverability Profile™

Ready to see your AI agents flagged?

Start in shadow mode. We’ll deliver your first Evidence Pack™ in 4–8 weeks.

Apply for pilot →Try the sandbox →

Canonical KYE™ surfaces referenced on this page: Evidence Pack™ · KYE Protocol™.