01
Sponsor
Funds a repeatable control pattern
Select a portfolio-company workflow and define the minimum evidence needed for implementation oversight. The sponsor does not become the company's trust root.
For private equity operating partners and portfolio finance leaders
Protect the capital behind agentic action.
Agents are moving from advice to action. EMILIA Gate puts a customer-owned authority tollgate at the systems where they change vendor bank details or release payments.
On completely mediated covered paths, no accepted exact-action authority and required evidence means no provider entry.
- Scope
- 1 protected workflow
- Duration
- 90 days
- Fixed fee
- $25K
- Start
- Observe first
Covered finance pathComplete mediation required
Agent proposesRelease $82,000
payment.release / vendor_014GATE
Customer-owned checkExact action + authority + evidence
HOLDFinance providerNot entered without accepted evidence
Gate controls admission on the covered path. It does not prove that bank details are correct, that fraud is absent, or that the provider succeeds.
The portfolio opportunity
One control pattern. Company-owned authority.
A sponsor can fund the same consequence-control discipline across companies without centralizing their keys, approvals, or operational records. Start with one company and one finance boundary. Repeat only after the control works under that company's systems, people, and risk rules.
Control model
Portfolio visibility without portfolio custody.
The sponsor can underwrite the rollout. The portfolio company remains the authority owner. Gate sits where the consequence becomes real.
02
Portfolio company
Keeps authority local
Own credentials, approvers, policies, trust roots, retention, and detailed action evidence. Decide which actions Gate may admit at the covered boundary.
03
EMILIA Gate
Controls the exact action
At a completely mediated executor path, require accepted exact-action authority and required evidence before provider entry, then preserve an action-bound record.
Sponsor may receiveBuyer-agreed coverage and implementation evidence
Portfolio company retainsKeys, policy, approvals, credentials, and detailed records
Portfolio Action Risk Lab
See the finance precheck before you discuss production.
Provision one throwaway observe-only key for Northstar Components, a fictional company consenting to this synthetic exercise. Then evaluate a vendor bank-detail change and a payment release against the existing finance prechecks.
- No ERP connection
- No real account or vendor data
- No money moved or blocked
- No production protection implied
OBSERVE ONLY
This synthetic lab evaluates metadata. It does not authorize, block, mutate, or execute a production finance action and does not establish complete mediation.
Consenting sandbox subjectNorthstar Components
FICTIONAL01 / Provision
Create a scoped, throwaway finance sandbox key.
The key is born for observe mode. It cannot turn this exercise into enforcement or reach a production ERP, bank, or payment rail.
The first engagement
One finance workflow. 90 days. $25K.
A fixed scope creates a real decision point: accept a completely mediated Gate design, keep observing, or stop. It does not require a portfolio-wide platform commitment.
01
Name the boundary
Map one vendor bank-detail change or payment-release path, including every credential and alternate route capable of reaching the provider.
02
Observe before enforcing
Run synthetic and buyer-approved read-only validation. Measure what the configured authority rule would hold, refuse, or allow without changing production behavior.
03
Make a buyer-owned decision
Deliver the boundary design, acceptance evidence, limitations, and operating procedure. Production enforcement begins only after explicit buyer acceptance.
Buyer receives
A bounded implementation decision, not a promise of universal safety.
- One protected-workflow definition and path map
- Customer-pinned authority and evidence rule
- Observe-mode precheck findings and limitations
- Boundary acceptance plan and operating procedure
The claim boundary
Control the crossing. Keep the conclusion honest.
The customer's rule at a covered action boundary
Exact action, finite authority, required evidence, refusal, one-time admission state, and an action-bound record under the customer's pinned trust inputs.
Truth, wisdom, legality, or a successful effect
Bank-detail correctness, payee identity, fraud absence, provider success, unmediated paths, investment performance, and legal or audit conclusions require separate evidence.
Questions operating partners ask
What the portfolio model does and does not mean.
Does EMILIA make a private equity investment safe?
No. EMILIA does not cover every agent risk or make an investment safe. Gate controls one bounded class of action risk at a configured boundary when every covered path to the consequential system crosses the control and the customer configures the authority and evidence rules. Source truth, bypass paths, fraud absence, provider outcome, legality, and business wisdom remain outside the claim.
Does the sponsor control each portfolio company's keys or approvals?
No. The deployment model keeps credentials, trust roots, authority rules, and detailed action evidence with the portfolio company. A sponsor can fund a common control pattern and receive only the buyer-agreed, payload-minimized implementation evidence.
What does complete mediation mean?
Every path capable of producing the covered effect must cross Gate at the executor or system-of-record boundary. A sidecar, prompt filter, or voluntary agent call cannot constrain an alternate path that bypasses the deployed control.
Does the Portfolio Action Risk Lab move or block money?
No. It provisions a throwaway observe-only sandbox key and evaluates fictional finance-action metadata. It does not connect to an ERP, change vendor data, release a payment, authorize production use, or provide production protection.
What is included in the first pilot?
One buyer-selected vendor bank-detail change or payment-release workflow, 90 days, and a fixed $25K scope. Work begins with synthetic and read-only validation. A production path changes only after the buyer accepts the boundary, trust inputs, operating procedure, and complete-mediation design.
Start with a real boundary
Protect one portfolio-company finance workflow.
Bring the workflow, owner, executor path, current approval rule, and known bypasses. We will scope the smallest pilot that can produce a defensible yes or no.
Customer deployment path only. EMILIA is not an insurer, auditor, investment adviser, or accredited certifier and does not make investment-safety claims.