3. Intelligence Layer
The first web-facing version of Aerion's long-term software story: the AI Mining Operator. This section specifies two working surfaces delivered in the MVP — an operator cockpit and a document-grounded assistant — and one area scaffolded for a later phase.
3.1 AI Operator cockpit
A single operator screen built on the site and market inputs Aerion supplies. Four views plus a scenario simulation panel.
- 1Energy-to-compute spread visualisation: the margin between energy cost and compute value, charted per site and in aggregate.
- 2Site and miner status views: per-site and per-miner state — online, idle, and current contribution to output.
- 3Dispatch decision log: a chronological record of dispatch calls holding the decision, its timestamp and the input values it was based on. Entries are written in plain language.
- 4State model: three machine states — operate, throttle, stop — applied consistently across the site views, the decision log and the explanations.
- 5Scenario simulation: an input panel for adjusting the supplied site and market values. The model returns the state it would select under those conditions using only the data provided. No figures are generated by the system.
- Data source
- Site and market inputs supplied by Aerion. The cockpit performs no independent data acquisition.
- Machine states
- operate · throttle · stop
- Delivered layer
- SaaS interface and product layer only — cockpit, state model, decision log and explanations.
Boundary — Hardware automation
The MVP does not automate physical mining hardware. It builds the SaaS interface and product layer that connects to real site-control systems once telemetry and control APIs become available. Hardware control is out of scope for this engagement. The cockpit runs on the site and market inputs Aerion supplies.
3.2 AI assistant
A document-grounded assistant. Answers are drawn only from approved Aerion sources and the controlled platform data the user is entitled to see. Out-of-scope questions return a decline.
| Ref | Capability | Scope |
|---|---|---|
| AI-01 | Explains metrics | Plain-language readings of the numbers shown across the dashboard, in the user's own account context. |
| AI-02 | Summarises pool status | Current pool status, utilisation, and what a given figure means for a participant. |
| AI-03 | Explains epoch states | An epoch's current position — pending, challenged, final — and what each state implies. |
| AI-04 | Explains POMP state | Reserve position, activated inventory, and how performance-linked availability works. |
| AI-05 | Service credits | Credit balances, reservations, and how usage maps to future compute access. |
| AI-06 | Locks and bonds | Lock status, verifier bonds and provider bonds. |
| AI-07 | Allocation tiers | How allocation tiers are reached and what each tier changes for the account. |
| AI-08 | Navigation help | Directs users to the relevant view or document. |
| AI-09 | Admin drafting help | Drafts investor updates and exchange summaries for the Aerion team from platform data. |
- Knowledge base
- Admin-managed. The Aerion team adds and withdraws approved sources from the admin console (§4.1), and the assistant answers from that list only. No source is ingested automatically and no external content is scraped.
- Data access
- Controlled platform data, limited to what the requesting account is entitled to see.
Exclusion — Assistant guardrails
The assistant gives no financial advice and uses no guaranteed-return language. It will not project prices, promise yields, or frame an allocation as an investment recommendation. Questions of that shape are declined and redirected to Aerion's approved risk and disclaimer material.
3.3 Licensing road ahead
Two areas are built into the MVP as structure and navigation only. Functionality is out of scope for this engagement.
- 1Licensing area reserved for future B2B operator accounts: the entry point for licensing the cockpit to third-party sites.
- 2AI / HPC readiness view for qualified sites: shows how a location scores against AI and HPC workload requirements rather than mining alone.
- 3Both areas ship in the MVP as structure and navigation. Functionality is scoped and priced in a follow-up phase.
- 4Licensing terms, pricing and operator onboarding rules are defined by Aerion. This scope covers the interface only.