Owner economics first.
No machine is purchased before a named workflow, accountable owner, baseline and acceptance test exist.
Starlight protocol / joint infrastructure / 01
Convert assets into governed intelligence capacity.
A deal system for operators who can create AI leverage and owners who control operating demand, warehouses, solar, batteries, buildings or capital. The owner buys measurable capability. The operator earns by designing and running it. Capacity expands only when the receipts justify it.
Owner-fundedOperator-managedEvidence-gatedModel-neutral
01Asset ownerDemand · site · capital · energy
02Deal operatorArchitecture · workers · execution
STLJoint InfrastructureContracts · control · provenance
03Owned nodeCompute · storage · network · telemetry
04Evidence ledgerValue · utilization · decisions · risk
productive claim metered execution verified receipt
00 / transaction thesis
Do not ask another company to fund your AI company. Construct a transaction in which it buys its own productivity, owns the productive assets, and grants you only the capacity and economics you have explicitly earned.
Assets remain legible.
Ownership, warranty, location, cost basis, capacity and exit are registered—not inferred from family trust or enthusiasm.
Capacity is contracted.
Business-critical demand, operator allocation, burst rights and revocation are explicit. Money never becomes accidental governance.
Expansion follows receipts.
Recurring value, utilization, failure rates and founder attention decide the next asset purchase. A GPU farm is an outcome, not a starting identity.
The exchange
Two independent businesses. One bounded productive system.
The protocol preserves separate ownership while composing the assets neither side could exploit as effectively alone.
AAsset owner
Contributes what is scarce to the operator.
- Existing operating demand and distribution
- Warehouses, roofs, power, batteries, network or buildings
- Balance-sheet credibility, purchasing power and supplier access
- Domain expertise, employees and real workflows
Receives
Higher productivity, owned infrastructure, controlled private intelligence and optional residual-capacity yield.
SJIContracted productive claimsfees ↔ assets ↔ capacity ↔ evidence
BDeal operator
Contributes what is scarce to the owner.
- AI architecture, workflow design and model routing
- Portable skills, worker roles, evaluation and governance
- Implementation, integration and managed operations
- Productization across sites and future customers
Receives
Architecture, implementation and recurring operations revenue; only then defined capacity or performance upside.
Deal sequence
Capital enters after evidence becomes structurally possible.
Each gate creates a receipt that makes the next commitment legible to the owner, operator, lawyer, accountant and lender.
- G0Deal thesis + conflicts map
Qualify the exchange
Name the owner, the economic workload, the asset base, the operator and the decision rights. Reject deals whose only thesis is cheaper compute.
- G1Signed order + baseline register
Buy the architecture
The owner commissions a fixed-scope Value Architecture. Baselines, economics, risks and procurement triggers are established before implementation begins.
- G2Acceptance tests + run receipts
Prove three workflows
Ship the smallest set of workflows capable of changing revenue, margin, working capital, asset productivity or management load within ninety days.
- G3Asset registry + capacity schedule
Install the owned node
The asset owner buys only the machines justified by measured demand. Ownership, warranty, location, metering and capacity rights are explicit.
- G4Worker registry + economic ledger
Operate under evidence
Workers receive bounded authority. Every consequential action has a human owner; every claim of value has a baseline and attribution rule.
- G5Scale memorandum + new approval
Expand or stop
Scale into additional buildings, workloads or external capacity only when recurring value, utilization and operating discipline clear the contract gate.
Where value is allowed to come from
The first node is underwritten by business effects—not token throughput.
01contribution margin per qualified opportunity
Revenue conversion
Lead qualification, configuration, pricing, quotation, follow-up and customer lifecycle—without replacing the systems that already hold commercial truth.
02gross margin, inventory turns, cash conversion
Margin & working capital
Supplier intelligence, stock exceptions, price drift, receivables preparation and purchasing signals delivered as decision-ready exceptions.
03net operating income per asset
Building & energy productivity
Metering, maintenance, PV and battery telemetry, tenant or site services, remote operations and additional productive uses of physical space.
04verified value per compute euro
Private intelligence capacity
Document work, retrieval, models, creative production and internal agents routed across local and cloud capacity according to privacy, quality and economics.
Investment gaterequired verified monthly value
=pilot ceilingtarget payback months
+monthlyrun cost
Compile your threshold →The operating system
One control plane above contracts, workers, models and machines.
The same primitives support one family business, ten operator-originated deals or a multi-site portfolio. Tenants, credentials, memories, budgets and queues remain separate.
06
Owner cockpitCommitments · economics · approvals · incidents · expansion
decision surface05
Deal & policy graphContracts · authority · budgets · data classes · stop conditions
control plane04
Worker registryRoles · skills · models · tools · schedules · escalation
operating layer03
Workflow runtimeHermes · deterministic jobs · MCP · queues · evaluations · rollback
execution layer02
Hybrid intelligence meshPrivate memory · local models · frontier APIs · cloud burst
routing layer01
Productive assetsOperating company · buildings · solar · batteries · network · machines
economic baseProcurement discipline
Buy the bottleneck—not the fantasy.
- Orchestration nodes
- Buy first. Small, redundant, always-on machines run schedules, connectors, monitoring and recovery.
- Private high-memory node
- Buy when private documents, retrieval or larger local models create a measurable privacy, latency or cost advantage.
- Accelerator node
- Buy only when cloud spend, queue depth, model fit or contracted creative demand crosses the registered trigger.
- GPU farm / additional sites
- Buy after sustained utilization and external demand exist. Never use property-backed debt to finance unpriced experimental capacity.
Provenance
Every economic claim resolves to an inspectable object.
No blockchain theatre. Versioned contracts, signed approvals, asset identities, run receipts and attributable baselines are enough—provided they are part of the operating path rather than assembled after the fact.
DEALSigned scope, economics, authority and expiry
ASSETOwnership, cost basis, location, warranty and capacity
WORKERRole, runtime, model, tools, permissions and budget
RUNInput lineage, actions, approvals, outputs and exceptions
VALUEBaseline, realized effect, attribution and confidence
DECISIONHuman owner, options considered and final authority
RUN_RECEIPT / 2026-09-00142verified
- mission
- prepare supplier price-drift exceptions
- authority
- read + draft; purchasing remains human
- inputs
- ERP export v184 · supplier list v22 · margin policy 4.1
- models
- local extraction → frontier review
- output
- 18 exceptions · 4 high-confidence actions · 0 autonomous purchases
- value
- €3,820 protected contribution margin · finance owner approved
Contract stack
The relationship is designed before money can distort it.
A lawyer localizes the templates. The protocol determines which questions the documents must answer and which rights expire with the underlying exposure.
- 01
Value Architecture Order Form
Defines the paid diagnosis, data room, decision rights, fee and stop condition before implementation is discussed.
- 02
Master Services Agreement
Separates services, liability, confidentiality, warranties and payment from any financing or ownership relationship.
- 03
Pilot Statement of Work
Names the three workflows, acceptance tests, budget ceiling, owners, dates and evidence required for the 90-day gate.
- 04
Asset & Procurement Schedule
Records owner, serial number, location, warranty, purchase basis, useful role and replacement trigger for every machine.
- 05
Capacity Allocation Schedule
Reserves business-critical capacity, operator capacity, burst rules, metering and priority without implying equity or control.
- 06
AI Authority Matrix
Binds every worker to allowed tools, data classes, spend limits, approval gates, escalation and revocation.
- 07
Data Processing & Security Schedule
Defines tenancy, secrets, retention, export, incident handling, subprocessors and the boundary between private and shared systems.
- 08
IP & Reuse Schedule
The owner keeps business data and bespoke deliverables; the operator keeps generalized platform primitives and unrelated ventures.
- 09
Evidence & Economics Schedule
Fixes baselines, attribution rules, value owners, cost owners and the receipt format before anyone claims ROI.
- 10
Exit & Transition Plan
Specifies credential handover, data export, worker shutdown, asset return, deletion evidence and continuity if the partnership ends.
For operators
Originate assets and demand without selling your company.
The operator does not pitch “AI consulting.” They originate a bounded productive node, bring the Starlight contract and evidence system, and remain free to build their own portfolio because custom work is separated from reusable primitives.
Open the operator model ↗ORIGINATE
Find an owner with demand and assets—not a passive investor.
UNDERWRITE
Translate workflows into baselines, payback gates and downside limits.
CONTRACT
Separate services, assets, capacity, data, IP, authority and exit.
COMPOSE
Route work across people, agents, local nodes and cloud providers.
OPERATE
Maintain workers, connectors, observability, incidents and evidence.
EXPAND
Earn the right to add hardware, sites and revenue streams from receipts.
Reference commercial model
One paid decision before one large promise.
Terms are configured to the company, jurisdiction and risk. The reference model keeps architecture, implementation, hardware and ongoing operation economically separate.
VA-1515 working days
Value Architecture
€6,500A decision-grade deal thesis, baseline, contract map, node design, economics and a go / revise / stop recommendation.
PILOT-9090 days
Governed pilot
from €18,000Three bounded workflows, owner-visible controls, worker receipts, acceptance tests and a measured scale decision.
NODE-OPSafter acceptance
Managed node operations
from €2,500 / monthRuntime stewardship, worker operations, observability, patching, evidence reports and controlled expansion.
No equity in Gate 0No guarantee in Gate 0No hidden hardware markupNo open-ended operator scopeNo autonomous consequential action
Construct the first transaction
Start with the economic graph. Machines come later.
Compile the deal, issue the Value Architecture order, open a bounded data room and reach a go / revise / stop decision before anyone buys infrastructure.
Reference frameworkKfW digitalisation financing ↗German computer-hardware useful-life guidance ↗NIST AI RMF ↗Financing, tax and legal treatment require transaction-specific professional review.