Do not sell funding.
Sell a paid decision architecture around an economic workflow the owner already needs.
Operator system / originate · underwrite · execute
Use another company's assets without becoming owned by them.
The operator creates a transaction that is valuable before shared capacity exists: the owner becomes an anchor customer, buys its own productive infrastructure, and pays for bounded architecture and operation. Rights over the operator remain finite, explicit and extinguishable.
Do not sell machines.
Register a capacity bottleneck and purchase trigger. Hardware is the approved response to evidence.
Do not sell yourself.
Sell named deliverables, operating service and defined capacity rights. Your company and generalized IP remain yours.
Portable operator skill pack
Eight capabilities turn a relationship into an investable node.
Each skill emits a versioned artifact. The operator is therefore replaceable at the service layer without making the operating system uninspectable or trapping the owner.
Counterparty qualification
Identify operating demand, decision authority, asset control, liquidity, conflicts and the reason the owner should rationally transact.
OWNER_FIT.mdEconomic underwriting
Build baselines, attribution rules, investment gates and downside limits without presenting hypotheses as realized value.
VALUE_LEDGER.jsonDeal composition
Separate customer revenue, asset ownership, capacity, financing, operator compensation and optional upside into explicit claims.
DEAL_GRAPH.yamlContract architecture
Issue the correct order form, SOW, asset schedule, authority matrix, data terms, evidence schedule and exit plan.
CONTRACT_MAP.mdNode engineering
Design the smallest hybrid topology that meets privacy, quality, continuity and economics; register purchase triggers before products.
NODE_SPEC.jsonWorker governance
Bind every agent to a role, model route, toolset, data class, spend budget, approval edge, evaluation and revocation path.
WORKER_REGISTRY.jsonManaged execution
Operate schedules, integrations, incidents, model changes and human handoffs without allowing custom work to consume the operator.
RUN_RECEIPT.jsonExpansion underwriting
Use value, utilization, reliability and attention cost to approve, revise or reject each additional machine, site and revenue stream.
SCALE_MEMO.mdOperator revenue architecture
Earn from decisions, delivery and stewardship—in that order.
Early cashflow should come from services the owner can expense against its own transformation. Capacity and performance economics enter only after operational proof.
1
Value Architecture
Fixed feePaid before implementation; funds discovery, baseline, deal design and counsel-ready artifacts.
2
Implementation
Milestone feePaid against acceptance tests for a bounded set of workflows and infrastructure outcomes.
3
Managed node operations
Monthly recurringRuntime, worker, connector, security, observability, reporting and controlled improvement.
4
Capacity allocation
Metered / contractedResidual compute or storage only after owner demand and operational reserves are protected.
5
Performance participation
Optional / narrowTied to a named value pool, attribution method, duration and cap—not the operator's entire company.
6
Procurement or finance
DisclosedAny rebate, referral fee, lease spread or hardware margin is visible and separated from technical advice.
operator enterprise value= reusable protocol + recurring managed nodes + verifiable casesnot bespoke hours + emotional obligations + hidden cross-subsidy
Boundary doctrine
Every unpriced right will eventually be exercised.
Family trust, friendship and excitement reduce friction; they do not define governance. The operator's survival depends on converting implicit expectations into priced, expiring, reviewable rights.
- 01No vague promise to 'handle AI' for the owner.
- 02No equity merely because the owner purchases infrastructure.
- 03No claim on unrelated brands, repositories, models or future ventures.
- 04No open-ended priority override against the operator's own company.
- 05No production use of employee consumer subscriptions as hidden infrastructure.
- 06No autonomous purchase, payment, contract, hiring or safety-critical decision.
- 07No hardware purchase without a registered economic or operational trigger.
- 08No performance fee without baseline, attribution, audit access, term and cap.
The network model
No single operator should carry the entire transaction.
Starlight separates origination, economic architecture, legal localization, technical delivery, managed operation and financing. One person may hold several roles; the receipts still name them independently.
Finds the owner, earns trust and surfaces the economic opportunity.
Underwrites workflows, deal claims, controls, node topology and evidence.
Localizes legal, tax, financing, privacy and corporate-benefit treatment.
Implements integrations, workers, dashboards, infrastructure and tests.
Runs the node, resolves incidents, reports evidence and controls change.
Retains final authority, assets, data, budgets and consequential approvals.
Operator activation
Bring one owner, one workflow and one credible asset base.
The first activation produces the qualification memo, deal graph, Value Architecture proposal and private deal room. Implementation is not sold until the owner approves the economics and boundaries.