KYE Operating Model Profile™ · v1.0

From readiness to runtime control.

Most AI-governance programmes stop at policies, committees, training or review documents. KYE™ connects governance intent to runtime execution. Assess. Gate. Decide. Prove. Revoke. Replay.

KYE Operating Model Profile™ turns AI-governance operating models into runtime authority decisions and replayable evidence — from use-case intake to controlled execution.

route The 10-stage journey door_back Authority Gates™ flaky Commit Boundary™ badge Entity Authority Record™ interactive_space Try it balance Open / paid

1 · The 10-stage journey

Use-case intake → runtime decision → replayable evidence.

Each stage emits a signed event onto KYE Signal Bus™ and is recoverable from the audit ledger.

Use Case IntakeKYEUseCaseIntake — actor type, expected actions, systems, data classes, external effects, commit actions.

Readiness AssessmentKYEReadinessAssessment — ten dimensions assessed, score in [0,1], interpretation.

Risk ClassificationRisk tier (low / medium / high / critical) embedded in the assessment.

Map AuthorityKYEEntityAuthorityRecord — living governance record per delegated actor.

Place GatesKYEAuthorityGate records before high-impact capabilities.

Configure RuntimeKYECommitBoundary records bind recommendation ↔ committed action.

ExecuteRuntime KYEPolicyDecision at the decision endpoint.

EvidenceKYEAdoptionEvidencePack — signed, hash-chained, offline-verifiable.

ReviewKYEReviewPath — multi-step human-review chain with SLAs.

ImproveRevisions to any of the above; full revision chain in the audit ledger.

2 · Authority Gates™

Place runtime gates before high-impact actions.

Authority Gates™ define where an AI worker, workflow, API, model or tool must stop, check authority, request approval, deny execution, quarantine the action or generate evidence.

paymentspayment_executionBefore a prepared payment becomes an executed payment.

sendexternal_messageBefore an outbound message leaves the tenant.

drawcontract_signatureBefore a contract / e-signature is sealed.

medical_servicesclinical_actionBefore a clinical action is performed.

terminalinfrastructure_commandBefore an infrastructure command is issued.

cloud_downloaddata_exportBefore a data export leaves the tenant.

keycredential_rotationBefore a credential is rotated.

verifiedevidence_exportBefore an evidence pack is exported beyond the tenant.

3 · Commit Boundary™

AI can recommend. KYE™ decides whether the action may commit.

The commit boundary is the point where an AI suggestion, plan, draft or preparation becomes an external action with real-world effect.

draft emailarrow_forwardsend email

prepare paymentarrow_forwardexecute payment

recommend refundarrow_forwardissue refund

draft contractarrow_forwardsign contract

suggest clinical steparrow_forwardperform clinical step

plan infra changearrow_forwardexecute command

recommend access grantarrow_forwardissue access grant

propose policy editarrow_forwardapply policy edit

Separate recommendations from committed actions. KYE™ checks authority before the action becomes real.

4 · Entity Authority Record™

Every AI agent, workflow, model or tool gets a governed authority record.

Owner. Purpose. Capabilities. Scope. State. Risk. Decisions. Evidence. Revocation status. One living record — signed, chain-bound, replayable.

smart_toy

Entity Authority Record™ · preview

Finance Payment Preparation Agent

pilot

Owner: Finance Ops · kye:user:finance_owner_001
Risk tier: high
Approved capabilities: invoice.read, payment.prepare, supplier.notify
Prohibited capabilities: payment.execute, contract.sign, credential.rotate
Required gates: kye:gate:payment_execute, kye:gate:external_send
Commit boundaries: kye:commit-boundary:payment_execution
Evidence: evidence_pack_available
Review due: 30 days · monthly cadence
Revocable: yes · cascade required

5 · Schemas (Apache 2.0, public mirror)

Ten normative objects. Validated in CI.

operating-model-profile.json — profile manifest
use-case-intake.json — stage 1 intake
readiness-assessment.json — stage 2 multi-dimension assessment
entity-authority-record.json — stage 4 living record per actor
authority-gate.json — stage 5 runtime gate
commit-boundary.json — stage 6 recommendation ↔ commit boundary
review-path.json — stage 9 human-review chain
training-record.json — per-owner training + certification
adoption-evidence-pack.json — stage 8 signed pack
governed-catalog-entry.json — discovery entry per governed entity

Each stage emits a signed event onto KYE Signal Bus™. The runtime never relies on out-of-band webhooks — KYE™ uses an authenticated, signed event bus with replay-resistant signatures.

6 · Try it — readiness checker

Tell us about your AI worker. We'll show what KYE™ requires.

Front-end illustration only — no data leaves the page. Real implementations call POST /v1/readiness-assessments.

7 · Open / paid boundary

The contracts are open. The managed engine is paid.

Open under Apache 2.0

Open

Operating Model Profile™ schema
Use-case intake + readiness assessment schemas
Entity Authority Record™ schema
Authority Gate™ + Commit Boundary™ schemas
Review path + training record schemas
Adoption Evidence Pack™ schema
Governed catalogue entry schema
Reason-code dictionary · signal bus event names
Sample payloads · basic conformance fixtures

Commercial / patent track

Paid

KYE AI Worker Readiness App™
KYE Authority Gate Designer™
KYE Commit Boundary Monitor™
KYE Governed Entity Catalog™ Pro
KYE Cloud Portal™
KYE Academy™ · training + certification
Readiness scoring + risk tiering engines
Side-effect classification + commit-boundary detection
Sector-specific readiness packs · BYOC / on-prem

Where to go next