Agent 3 · Operations & Commercial Automation · control surface

Make money and build distribution.

This is where the Operations cluster is displayed and orchestrated: the repository registry, the KPI system with revenue first, the workflow ranking, the 90-day objective counted from logged customer conversations, the decision log and kill list, the weekly CEO report, and the versioned contracts to the Energy and Physical AI clusters. Nothing is for sale on this page. Every number is measured and sourced, or it says not yet measured.

mandate: Operations & Commercial Automation — Revenue Firstregistry reviewed 2026-09-05validation period 2026-09-05 → 2026-12-04 · 48 days leftmachine index /api/cluster/

Revenue first

The primary KPI, then the six the CEO report opens with. A value appears here only when it has been measured from the named source.

Revenue · primary
not yet measured
source when measured: Invoice ledger of the entity that bills the customer.
MRR
not yet measured
source when measured: Billing system.
Pipeline
not yet measured
source when measured: Customer evidence log (content/cluster/evidence.ts).
Qualified opportunities
not yet measured
source when measured: Customer evidence log.
Conversion
not yet measured
source when measured: Customer evidence log.
Retention
not yet measured
source when measured: Derived from churn.
Gross margin
not yet measured
source when measured: Ledger plus infrastructure invoices.

All fourteen KPIs, with definitions →

90-day objective

Customer conversations0 / 50
Qualified opportunities0 / 10
Serious design partners0 / 3
Paying customers0 / 1

Counted from the evidence log. 42 of 90 days elapsed.

Roadmap and evidence →

Registry · 12 entries

CORE1
MODULE0
RESEARCH0
INTERNAL8
EXPERIMENT3
ARCHIVE0

2 names from the mandate not located in the public inventory: LogistiSync, Equipment tracking.

Full registry →

Latest decision

D-007 · 2026-09-05
The control room shows measured values or "not yet measured" — never placeholders

Every KPI value is null until measured, with a source named. Roadmap progress is counted from the evidence log, never typed. GitHub metadata is fetched, never hand-copied. The CI guard fails on a KPI with a value but no measurement date.

Kill list: nothing frozen or killed yet.

Decision log and kill list →

Weekly CEO report

No report filed yet. The template with the eighteen mandated fields is ready.

Reports →

Core and vertical applications

EcoWoods is the commercial proving ground; the Forge sites are vertical experiments; Runway Fuel is a platform hypothesis until two independent customers require the same workflow. Live repository metadata is on the registry page.

Registry — core and vertical tiers
NameStatusRoleCodeSite
Runway FuelINTERNALPlatform hypothesis. Not to be generalized prematurely.not located—
ecowoods-appCORECommercial proving ground. Every workflow claim in this cluster is tested here first.ecowoods-appecowoods.ca
FloorForgeEXPERIMENTVertical experiment — flooring. Shares its buyer with the EcoWoods proving ground.floorforge-aifloorforge-ai.vercel.app
PaintForgeEXPERIMENTVertical experiment — painting.paintforge-aipaintforge-ai.vercel.app
DryForgeEXPERIMENTVertical experiment — drywall.dryforge-ai—
Bahn Project ManagerINTERNALVertical hypothesis — critical infrastructure project operations. The cluster’s only foothold outside contracting.bahn-project-manager—

Elsewhere in the network

The operator’s explainers stay on this site: Why AI is power-bound, not GPU-bound · Grid inertia and the 50 Hz constraint · IT/OT convergence in railway traction power — all explainers, the books.

Operated by Vincenzo Ceccarelli Grimaldi, electrical engineer in Frankfurt am Main — the CEO layer above the three clusters. vincenzo@igrimaldi.engineering · contact form.