Terminal

KYE Protocol™ Terminal

Every agent action, decided at t=0 and sealed: an interactive demo with fictional data.

Decision centre: chain of authority, admissibility, finality

Computed

You learn: Who decided what, along which chain, why a request was held or denied, and that the record is final and verifiable. You can: Watch decisions arrive; approve as the delegate (the initiator cannot), verify a seal, revoke a delegation.

Approver's phoneDara Quinn, head of procurement
  1. KYE™ policy decision point

    Procurement agent orders above its approval threshold

    approval_threshold_breach

    ProcurementNeeds approval

    Chain of authority

    1. Orrin Logistics (demo) Principal
    2. Dara Quinn, head of procurement kye:authority:orrin.example:procurement-head-2026
    3. Procurement agent kye:authority:orrin.example:proc-04-2026q4
Approver consoleDara Quinn, head of procurement
  1. KYE™ policy decision point

    Drafting agent prepares a disclosure letter, with redaction

    permission_granted

    LegalAllowed

    Decision record sealed

    1. Decision allow_with_constraints
    2. Obligations kye:obligation:redaction

    ff8305bc6290ca7ef2d60b6290c4c2712c62b1280faf28be46d896685fdea90e

  2. KYE™ policy decision point

    Credit agent acts outside its jurisdiction

    jurisdiction_unsupported

    Financial servicesDenied

    Decision

    1. not_revoked grant in force
    2. within_time_window 2026-10-14T09:09:20Z before 2027-01-12T00:00:00Z
    3. action_in_scope credit.line.approve in [credit.line.approve]
    4. purpose_matches lending.adjudicate = lending.adjudicate
    5. within_jurisdiction US in [GB, IE]
    6. within_constraints GBP 4,200.00 ≤ GBP 25,000.00
agent-decisionsAgent platform team (demo)
  1. KYE™ policy decision point

    Accounts-payable agent pays a supplier invoice

    permission_granted

    Agent paymentsAllowed

    Chain of authority

    1. Brightmoor Retail (demo) Principal
    2. Ana Ruiz, finance lead kye:authority:brightmoor.example:finance-lead-2026
    3. Accounts-payable agent kye:authority:brightmoor.example:ap-11-2026q4
CISO dashboardCISO (demo)
  1. KYE™ policy decision point

    Clinical summarisation agent asks to read records for marketing

    permission_missing

    Healthcare data accessDenied

    Decision

    1. not_revoked grant in force
    2. within_time_window 2026-10-14T09:05:31Z before 2027-01-01T00:00:00Z
    3. action_in_scope record.read in [record.read, record.summarise]
    4. purpose_matches marketing.outreach ≠ clinical.summarise
    5. data_class_in_scope [health.record] in [health.record]
    6. within_jurisdiction GB in [GB]
  2. KYE™ policy decision point

    HR operations agent acts on a revoked delegation

    delegation_revoked

    HRDenied

    Signal

    1. Regional treasurer, EU Revoked
    2. Treasury agent (fx-router) Revoked by cascade
How this widget is built
Demonstrates
Decision feed and approvals
Components
  • Policy decision point (evaluate, kye_decide)
  • Chain of authority
  • Admissibility checks
  • Decision records and evidence packs
  • Revocation cascade
Flow
Each decision lands on the device of whoever must know or act: approvals on the approver's phone, denials on the CISO dashboard, allows in the team channel. Tapping one opens its chain, checks, seal or cascade. Architecture diagram
Used on
  • /examples/: On the examples page; it plays when scrolled into view (Play/Pause).
  • /: The home page, right after its opening.
  • /terminal/: The terminal: the decision centre on its devices.

Recent decisions

Demo data

You learn: What KYE™ decides for each agent action, why (reason code), and who must act. You can: Replay the feed; approve or decline the held decision.

  1. KYE™ policy decision point Accounts-payable agentpayments.transferAllowed

    Accounts-payable agent pays a supplier invoice

    permission_granted

    Pay €412.90 to Paperhouse Supplies (demo), invoice INV-2026-0917

    In-appWebhook

    • accounts_payable.settle
    • kye_decide
  2. KYE™ policy decision point Procurement agentpurchase_order.createNeeds approval

    Procurement agent orders above its approval threshold

    approval_threshold_breach

    Order 40 pallets of packaging film from Kilnworks Supplies (demo), £18,400

    App pushIn-appWebhook

    • procurement.replenish
    • kye_decide
  3. KYE™ policy decision point Clinical summarisation agentrecord.readDenied

    Clinical summarisation agent asks to read records for marketing

    permission_missing

    Read 1,200 patient records to build a marketing list (demo)

    In-appWebhook

    • marketing.outreach
    • kye_purpose_admit
  4. KYE™ policy decision point HR operations agenthr.record.updateDenied

    HR operations agent acts on a revoked delegation

    delegation_revoked

    Change a staff member's contracted hours (demo)

    In-appWebhook

    • hr.contract.administer
    • kye_authority_check
  5. KYE™ policy decision point Research and drafting agentdocument.draftAllowed

    Drafting agent prepares a disclosure letter, with redaction

    permission_granted

    Draft a disclosure letter for matter M-2207 (demo)

    In-appWebhook

    • legal.matter_support
    • kye_decide
  6. KYE™ policy decision point Credit decisioning agentcredit.line.approveDenied

    Credit agent acts outside its jurisdiction

    jurisdiction_unsupported

    Approve a £4,200 credit line for an applicant in the US (demo)

    In-appWebhook

    • lending.adjudicate
    • kye_decide
How this widget is built
Demonstrates
Decision feed
Components
  • Policy decision point (kye_decide)
  • Decision records (kye.decision.record.v1)
  • Approval routing (dual control)
  • Evidence packs
Flow
Each agent action is decided against its chain of authority; approvals go to the delegate who holds the threshold; every outcome is sealed. Architecture diagram
Used on
  • /examples/: On the examples page, with the rest of its scenario.
  • /developers/: The developer portal: what every call returns.
  • /governed-ui/: GovernedUI™: the decisions it shows.
  • /mcp/: The MCP server: the decisions behind its tools.
  • /platform/: The platform: decisions with their chains of authority.
  • /terminal/: The terminal: every decision, replayable.