Build a new company natively on authority finality™.

Who the Studio is for

Founders whose product turns on a consequential action.

The Studio selects a small number of founders and operators whose core thesis depends on an agent or a system taking a consequential action — and being able to prove who authorised it. If your venture lives or dies on defensible authority, you need the rails KYE Protocol™ already runs; the Studio builds them in from the first commit.

• Agentic-product founders. You are building a product where an AI agent acts — approves, pays, files, releases — and a regulator or a board will one day ask who let it. The agent is governed as a first-class principal under KYE Protocol™ §0.30 from the start, never bolted on later.
• Regulated-vertical operators. You know a regulated workflow cold — claims, lending, clinical, tax, AML — and you want to ship an AI-native product into it that passes a regulator-style spot check on launch day, not after a painful retrofit.
• Ex-platform builders. You have built infrastructure before and want a co-founder who supplies the hardest 20% — the authority, evidence, and replay layer — so your team ships the product, not the governance plumbing.
• Repeat founders seeking aligned capital-of-effort. You would rather trade equity for a partner who builds alongside you than pay an agency that disappears at handover. KYE™'s stake vests with your milestones, so incentives stay aligned for the life of the build.

What KYE Protocol™ ™ brings to the cap table

The authority layer, built in — not a services invoice.

KYE™ is your technical co-founder for the authority-finality layer. You bring the venture thesis and the domain; KYE™ brings the authority-finality layer every regulated AI product now needs and the discipline that lets your venture make claims it can defend in front of an auditor.

• Authority-finality rails. Purpose Permission™ admissibility at the action boundary, Evidence Pack™ sealing, and Replay-Proof™ derivable from public keys alone. Your venture rides these rails as-is; you never re-implement them.
• Governed agents as principals. Every agent your venture ships is scaffolded through the KYE™ Agent Dev Kit™ so it has a canonical identity, authority bindings, and a full evidence chain — governed exactly like a human or system principal under KYE Protocol™ §0.30.
• Banking-grade from day one. WORM audit, dual-channel sign-off on irreversible actions, and a §0.3 evidence trail on every consequential act. Your venture ships at a grade regulated buyers can adopt, cutting enterprise security review from weeks to days.
• Go-to-market reach. At Launch, your venture is listed in the KYE Protocol™ directory as an authority-native venture (consent-based) and introduced across the KYE™ buyer network of regulated enterprises.
• Aligned, milestone-gated terms. KYE™'s equity and revenue-share are earned in tranches tied to your real milestones — thesis validated, MVP live on the rails, first governed launch — so KYE™ earns its stake by delivering, not by signing.

The one hard rule

Every Studio venture is authority-native — or it is out of scope.

The Studio has a single non-negotiable gate: your venture must be authority-native, built natively on KYE Protocol™'s authority-finality rails. This is the line that makes the Studio a category-owner's program rather than a generic incubator — and it is why KYE™ can put its own equity behind what you build.

• Authority-native means the rails are load-bearing. Purpose Permission™, Evidence Pack™, and Replay-Proof™ are part of how your product works, not a compliance add-on. If they were removed, the product would not be defensible.
• A venture that does not run on the rails is routed elsewhere. If your idea does not turn on consequential-action authority, the honest answer is a generic accelerator — not the Studio. You will hear that at Spark, fast, instead of after months.
• No self-perpetuating automation. Any automation the Studio co-builds carries a bounded termination guarantee under KYE Protocol™ §0.32 — no process that triggers itself into an unbounded loop. KYE™ will not co-build a runaway.
• Leave the rails, lose the claim. If a venture later ceases to be authority-native, the authority-native claim and KYE™ co-branding are withdrawn under the rail-offboarding clause. The venture may continue — just not as a KYE™ authority-native venture.

Three tiers · sequenced co-creation

Spark / Forge / Launch — validate, build, launch.

The tiers are sequenced. Spark validates the authority thesis. Forge co-builds the authority-native MVP. Launch hardens the rails and takes the venture to market. Each tier is invite-only and cohort-capped, and KYE™'s consideration is the equity and revenue-share governed by a milestone-gated terms envelope — disclosed to admitted founders, not printed here.

KYE™'s consideration is equity and/or revenue-share earned through milestone-gated tranches — KYE™ earns its stake by delivering, not by signing. Exact terms are disclosed to admitted founders under the engagement.

How co-creation works

Application → Spark → Forge → Launch → Directory listing.

The path from application to a governed launch is concrete, not theoretical. Admission is application-reviewed through the KYE Protocol™ engagement rail at every step, and KYE™'s equity tranches release against your real milestones along the way.

• 1. Application. Submit the Studio application. You describe the venture thesis, why it depends on consequential-action authority, your domain evidence, the equity/revenue-share you are open to, and the legal attestations. A strong authority-native thesis qualifies you to apply; the cohort is capped and admission is reviewed.
• 2. Spark — validate. A focused validation window with named founder availability. KYE™ pressure-tests the authority thesis and produces a governed validation record. Outcome: a Forge proposal or an honest decline.
• 3. Forge — co-build. KYE™ integrates the venture onto the authority-finality rails, scaffolds the agents as first-class principals, and stands up the governed product surface. The equity-terms envelope is executed; tranches are milestone-gated.
• 4. Launch — go to market. KYE™ hardens the rails to banking-grade, co-runs the governed launch, and lists the venture in the directory (consent-based) with KYE™ buyer-network introductions.
• 5. Evidence on every act. From launch, the venture emits the §0.3 governance-evidence family on every consequential action — so it ships with a full evidence trail and can prove who authorised what, in minutes, when an auditor asks.

Where the Studio sits

One of four ways to partner — and the only one that co-founds.

KYE Protocol™ runs four distinct partner programs. The Studio is the only one that co-creates a brand-new venture and takes equity in it. If your need is one of the other three, those are the right doors — and you will be pointed to them honestly.

• KYE™ for Startups™ — credits. Free metered-governance credits for early startups already building. No co-creation, no equity. See KYE™ for Startups™.
• KYE™ Design Partner™ — co-design. Existing enterprises co-design KYE Protocol™'s own core product for discounted founding-customer terms. No new venture, no equity. See KYE™ Design Partner™.
• KYE™ Sector Pack Foundry™ — productise your framework. Domain experts turn their existing framework IP into a KYE-Powered Pack™ for pack-sale revenue-share. No new company built from zero. See the Sector Pack Foundry™.
• KYE™ Authority-Native Venture Studio™ — co-found. The Studio co-creates a NEW authority-native venture with you and takes equity and revenue-share in that venture. This page.

Bring the venture. We'll build the authority layer.

Applications are invite-only and cohort-capped. Submit the Studio application; you describe an authority-native thesis and the terms you are open to, and KYE Protocol™ responds with a Spark conversation or an honest decline.

Canonical KYE™ surfaces referenced on this page: KYE™ Agent Dev Kit™ · KYE Protocol™ · Purpose Permission · Universal Engagement Rail.