Turn expert governance frameworks into KYE™-Powered commercial Packs.

Domain experts who own a framework — and want it shipped as a Pack.

The Foundry selects expert partners who bring the right combination of ownable IP, named buyer-network access, and a paid productisation budget. The qualification gate is deliberately strict: KYE Protocol™ mark-bearing Packs carry the same conformance posture as KYE™-authored framework mappings, so the partner side must clear the same evidence bar.

• Clinical-risk specialists. Practitioners who own a clinical safety case framework with audited NHS Trust deployments and named CCIO relationships.
• Ex-regulators. Former regulators with named prior roles inside MHRA, FCA, PRA, ICO, EBA, OCC, ESMA, equivalent — whose framework reflects practitioner-grade interpretation of regulator-of-record text.
• Audit firms with proprietary frameworks. Boutique audit firms whose engagement methodology is itself ownable IP — not merely an application of the regulator text.
• Model-risk practices. Specialist model-risk practitioners with SR 11-7-grade methodologies, validation playbooks, or post-deployment monitoring patterns.
• Insurance underwriters and reinsurers. Underwriters whose authority-and-loss-event framework applies cleanly to agentic-AI risk transfer.
• Compliance-framework owners. Authors of named compliance frameworks who hold the IP and want a protocol-grade commercial distribution.

Four prerequisites — non-negotiable at the Scout gate.

• Domain expertise — named. Named prior roles, audited deployments, regulator engagements, publications. The partner produces the named evidence at application time; KYE™ verifies it.
• Ownable IP — distinct from regulator text. Pure reproduction of public regulator text does not qualify — KYE™ already maps the regulator text. The partner brings the rubric, the templates, the hazard taxonomy, the per-tier playbook — whatever makes the framework theirs.
• Buyer network — named. Named relationships inside the target buyer segments who will accept a pilot conversation. Without this, the productisation has no GTM.
• Paid productisation budget. The partner brings funded productisation budget. The Foundry is not a free-rider rail; KYE™ does not fund speculative productisation.

Application → Scout → Build → Certified Pack → Directory listing.

• 1. Application. Submit the 11-question canonical Foundry application form. The form captures framework summary, ownable IP attestation, domain expertise evidence, named buyer-network evidence, conflicting-IP attestation, NDA, intended public claims, evidence buyers need, tier requested, and exclusivity — plus the required legal attestations (authority to bind, accuracy, closed-registration acknowledgement, data-processing consent). Fee schedule and revenue split are set by KYE™, so no pricing is requested.
• 2. Super-admin review. The application enters a super-admin-gated queue. Dual-channel sign-off per KYE™ banking-grade — no auto-approval, no junior-reviewer approval, no email-only approval. Approval response within 10 business days.
• 3. Scout engagement. 2–4 week structured assessment. Framework deep-mapping fit-check against the canonical artefact template. Output: framework-fit memo + Build-tier conversion proposal or polite decline.
• 4. Build engagement. 12–16 week full productisation. The partner co-authors control rows, rule packs, dictionaries, sector pack bindings, and per-claim evidence definitions in the canonical shape. Every public claim runs through the claim-approval workflow.
• 5. Coverage attestation. Co-signed envelope proving the Pack's claim-set is bijective with its bound canonical artefacts. The attestation is the gate for the KYE Powered Pack™ badge.
• 6. Badge issuance. Dual-channel sign-off transitions the badge from `draft` to `certified`. The KYE Powered Pack™ wordmark renders on the partner site and on the KYE™ directory.
• 7. Directory listing. The Pack is listed on the KYE™ directory under the partner-programme rail. Buyers verify the badge against the directory in one round-trip.

Revenue-shared by channel of origin — with claim approval reserved.

• KYE-sourced revenue split. Default 70/30 to KYE™. The buyer was originated through a KYE™-led channel.
• Partner-sourced revenue split. Default 60/40 to partner. The buyer was originated through the partner channel.
• Strategic-deal override. Co-sold, co-branded deals ≥ £500k revert to 50/50 irrespective of channel of origin.
• Exclusivity. Maximum 24 months. Time-boxed. Performance-gated by ARR originated, qualified pipeline value, certified buyers count, and attestation emission count. Missed gates downgrade or revoke the right.
• Claim approval — non-negotiable. Every public claim about the Pack requires prior KYE™ written approval through the canonical claim-approval workflow. A Pack carrying the KYE™ mark cannot make a claim the protocol has not validated.
• Discontinuation clause — non-negotiable. KYE™ retains the right to revoke the KYE Powered Pack™ badge on bijection failure, claim breach, conflict of interest, or material commercial breach. Revocation is permanent for the `pack_id`.
• Termination wind-down. Termination triggers a wind-down right; in-flight Pack instances continue to honour their entitlement window. No Pack instance is cut off mid-entitlement.

Published Authority Packs — the productisation template, shipped.

Each pack below is a KYE-built reference Authority Pack™ — the exact end-to-end shape every Foundry partner inherits: rule pack, dictionary, sector pack, obligation manifest, signed coverage attestation, and a public landing. They demonstrate the template a partner's framework is productised into.