Origin Ledgers Launch App
INTELLIGENCE

Understand your program while it runs.

Intelligence works inside LEDGERS, across every participant in your emissions allowance program. It turns supplier and operational data into positions you can read, explain and plan against, before the period closes.

Program A · Period 2026Illustrative
Allowance Measured Projected
Allowance Measured Projected
THE OPERATING PROBLEM

A program is settled on verified figures. It is run on scattered data.

Emissions data arrives from many participants, in many formats and at different times. Invoices, utility bills, spreadsheets and system exports rarely line up. Without structure, the company operating the program sees its position only at period close.

  • Supplier submissions
  • Invoices
  • Utility bills
  • Spreadsheets
  • PDFs
  • ERP exports
  • Procurement data
  • Logistics records
THE INTELLIGENCE LOOP

Four functions prepare. People decide. The infrastructure records.

Intelligence runs on its own analysis track. Nothing it prepares becomes part of your program until it passes a gate: assurance at the level your program requires, then authorization by the participant or the company operating the program.

The intelligence loop Analysis track, dashed: NOVA, AURA, LYRA, VEGA. Gate 1, Assurance, connects AURA to Recorded in LEDGERS. Gate 2, Authorization, connects VEGA to Policy checks. Control track, solid: Recorded in LEDGERS, Policy checks, PVN validation, Registrar signing, Execution, Reconciliation, Record. Branch from Execution: carbon credits through ORIGIN, where the program permits. Return from Record to NOVA: new operational data. ANALYSIS TRACK CONTROL TRACK ORIGIN Carbon credits through ORIGIN, where the program permits New operational data GATE 1 Assurance GATE 2 Authorization Authorized NOVAAURALYRAVEGA Collect & structureCalculate & analyzeReport & explainModel & plan Recorded inLEDGERS Policy checks PVN validation Registrar signing Execution Reconciliation Record
Dashed: prepared by Intelligence Solid: recorded in your program
NOVA · COLLECT & STRUCTURE

Every figure starts as a record that keeps its source.

NOVA takes the data your program receives and structures it into program records. Each record stays linked to the document it came from. Entries that do not reconcile are flagged and held for review.

  • Files or API. Upload invoices, utility bills, spreadsheets and PDFs, or send data by API, including exports from ERP, procurement and accounting systems.
  • Structured to your program. Records are organized by participant, source and period, within the program boundary.
  • Held for review. Flagged entries stay visible, with the reason, until someone resolves them.
More on NOVA →
Program recordsIllustrative
ParticipantSource
Participant 01Invoice
Participant 02Utility billHeld for review
Participant 03ERP export
Participant 04SpreadsheetHeld for review
Participant 05PDF
AURA · CALCULATE & ANALYZE

Emissions become positions against each allowance.

AURA classifies emissions within your program boundary, matches an emission factor to each activity and calculates every participant's position against its allowance. Each calculation keeps its trail, from source record to factor to result.

  • Your program's method. AURA applies the calculation method configured for your program.
  • Anomalies flagged. Figures that break from expected patterns are flagged for review.
  • Three positions. Within allowance, At allowance or Excess, each marked as projected, measured or verified.
More on AURA →
Program A · Period 2026Illustrative
Allowance Measured Projected
Participant 01 Within allowance Measured
Participant 02 Within allowance Projected
Participant 03 Within allowance Measured
Participant 04 Excess Projected
Participant 05 Within allowance Projected
Participant 06 Within allowance Measured
CONTROL

Where analysis ends, control begins.

A figure prepared by Intelligence is a working figure. It becomes part of your program only through the same controls that govern every program event.

See how PVN validates each event
  1. 1Prepared by Intelligence. Working figures, shown dashed.
  2. 2Verified by the assurance provider or review your program requires.
  3. 3Authorized by the participant or the company operating the program.
  4. 4Validated, executed and recorded. PVN validates the lifecycle event. Origin Ledgers executes it and records the result.

PVN validates lifecycle events. It does not validate analysis produced by Intelligence.

LYRA · REPORT & EXPLAIN

Every number in a program report can be traced.

LYRA turns program activity into management reports: emissions, allowances allocated and used, participant positions, reconciliation and validation status, outstanding actions and exceptions. Select any figure to see its source, calculation, assurance state and PVN state.

  • Written for the people running the program. Status, exceptions and next actions sit in one place, for every participant.
  • Carbon credits as they stand. Where your program uses carbon credits, reports show each as allocated, assigned or retired.
More on LYRA →
Program reportIllustrative
VEGA · MODEL & PLAN

Test a decision before you commit to it.

VEGA models how a change would move your program's position. It shows which participants contribute most to projected excess and how future allowance requirements could shift. Every result is labelled as a scenario.

For example:
  • A supplier reduces its emissions by 15%.
  • Production rises by 20%.
  • A logistics route changes.
More on VEGA →
Program A · Period 2026Illustrative
Current trajectory Scenario A Scenario B
Scenario A Scenario B Current trajectory
RESIDUAL REQUIREMENTS

Where carbon credits are needed, the requirement comes with its basis.

When your program permits carbon credits, VEGA shows the residual requirement and how it was reached: projected or verified excess under your program rules. Validated supply is available through ORIGIN. Allowances never become carbon credits.

How validated supply works
Illustrative
LEDGERS
Participant 02Within allowance
Participant 04 ExcessProjected Residual requirement
ORIGIN
SUPPLY-CHAIN SCALE

From the whole program to a single supplier.

Intelligence works at the level where a program is run: each participant, including each supplier, against its own allowance.

participants Illustrative
  1. 01

    Program view. Emissions and position across every participant.

  2. 02

    Supplier emissions. Each supplier's emissions, by source and period.

  3. 03

    Supplier position. Each supplier against its allowance, individual or pooled.

  4. Scenario
    04

    Supplier action. A scenario for one supplier, ready for an authorized decision.

DATA BOUNDARY

Your program's data stays inside your program.

Intelligence works in the private Origin Ledgers environment. The company operating the program sees Intelligence for its own program. Each participant sees its own data and position. Nothing Intelligence produces appears in the public registry.

Data from one program is never used to produce Intelligence for another.

Our AI model provider
Private Origin Ledgers environment
Intelligence
NOVA AURA LYRA VEGA
Public registry