Host-Platform Authority Adapter Pack™ for System Integrators.
Your enterprise AI runs on a host platform — AuGENT, ServiceNow, Palantir Foundry, Databricks, or a workflow you built. The KYE Host-Platform Authority Adapter Pack™ routes that platform’s tool-calls, retrievals, document-processing and human approvals through the KYE Protocol™ Authority Gateway and seals an Evidence Pack™ before each consequential action commits. As a System Integrator you ship the governance layer your regulated customers already need — you integrate KYE Protocol™, you do not compete with the platform.
Enterprises buy agentic AI — then stall on “prove it stayed inside the approval.”
An enterprise AI platform can run an agent. It cannot prove, cryptographically and at action time, that each consequential action stayed inside the approval, the delegation chain, the purpose and the scope a human signed off. That proof gap is what stalls regulated AI adoption — and it is what your customers ask you, the System Integrator, to close. Three facts converge:
- The platform runs the agent; it does not govern authority. Tool-calls, RAG retrievals, document processing and human-in-the-loop steps execute — but the authority decision is not bound, signed, or replay-derivable at the commit boundary.
- You already own the integration. SIs sit between the platform and the regulated customer. Adding the KYE Protocol™ governance layer is an integration, not a rebuild — §0.25 integrate, don’t compete.
- One envelope, every host. The Pack projects the single KYE Protocol™ governed tool-call envelope across every host platform. No per-platform reinvention, no parallel evidence shape — one contract you ship everywhere.
A KYE-powered authority adapter — recurring revenue on a governance layer you own.
- Evidence before the commit boundary. For every consequential action, a sealed Evidence Pack™ is emitted before the host commits — binding actor, delegator, scope, policy, purpose, and the Authority Finality™ outcome.
- Fail-closed by default. When the Authority Gateway is unreachable, consequential actions deny rather than slip through — the No-SPOF posture regulated buyers require.
- Replay-derivable from public keys alone. An auditor verifies the chain offline against published keys — no vendor cooperation, no private envelope, no bilateral trust.
- Revenue share through the Foundry. You productise the adapter once and ship it across your customer base under the KYE-Powered Pack™ badge, on a Foundry Build revenue-share envelope.
- Standards-anchored. The Pack maps to EU AI Act™ Article 12 record-keeping and Article 14 human oversight, NIST AI RMF, ISO/IEC 42001, and SOC 2 CC6 — the controls your regulated customers are already audited against.
One governed envelope — projected across every host platform.
Every host platform you support routes through the same contract. The adapter is a declarative integration over the canonical host-platform-adapters manifest — not one connector per platform reimplemented. Five host classes ship in the reference manifest.
- 1 — Host action proposed. A tool-call, RAG retrieval, document-processing step, model inference, or human-in-the-loop approval is about to run on the host platform.
- 2 — Authority Gateway check. The adapter calls the KYE Protocol™ Policy Enforcement Point in the host runtime (in-process SDK, sidecar proxy, gateway callout, or webhook) before the commit boundary.
- 3 — Single governed envelope. The adapter emits the one canonical KYE Protocol™ governed tool-call envelope — never a per-host shape. The decision is bound to actor, delegator, scope, policy and purpose.
- 4 — Evidence Pack™ sealed. A signed, replay-derivable Evidence Pack™ is sealed before the host’s point of no return.
- 5 — Authority Finality™ outcome. The action commits or is refused. The host platform proceeds only on an allow; consequential surfaces fail closed on gateway unavailability.
Five host classes — one adapter family.
The host-platform-adapters manifest declares each host and the action surfaces the adapter governs. An SI extends the family by grafting a new host entry — never by forking the envelope.
| Host platform | Class | Commit boundary the adapter governs |
|---|---|---|
| AuGENT | Enterprise AI platform | Agent tool-call dispatch + HITL approval |
| ServiceNow | ITSM / workflow platform | Change-task state transition to Implement |
| Palantir Foundry | Operations platform | Action commit to an operational data object |
| Databricks | Data & AI platform | Retrieval / inference feeding a consequential action |
| SI-built bespoke workflow | SI-bespoke | The SI-declared point of no return |
Each entry pins the single governed envelope and a fail-closed posture for consequential surfaces. The Pack is the §0.10 generalisation of the connector pattern: one root, many projections.
Qualified System Integrators — apply through the Foundry.
The KYE Host-Platform Authority Adapter Pack™ ships through the KYE Sector Pack Foundry™ Build tier as an authority-adapter expert pack. Productisation is qualification-gated; revenue share and pricing are disclosed under NDA to qualified applicants. You build the adapter once; KYE Protocol™ governs the authority, the evidence, and the replay-proof beneath it.