Travel & Hospitality AI agent · Aviation emissions units
Aviation Emissions Units AI Agent
Resolve CORSIA scope per state pair against the list ICAO republishes each year, hold every emissions unit with its programme, vintage and conditions, and run the four clocks the operator answers to.
Assembles the eligibility case, never the cancellation
In
01
A reporting year closes, and the verified Emissions Report reaches the State by 30 April.
02
A scaling factor publishes 31 October, and the State notifies the requirement by 30 November.
Reason
03
A unit is offered, and the ICAO eligible-units document settles whether it qualifies at all.
04
A unit carries a vintage, and only reductions dated 2021 to 2026 sit inside the window.
05
A cancellation falls due 31 January 2028, and no first-phase deadline has yet run.
Decide
06
A cancellation completes, and a verified Emissions Unit Cancellation Report follows by 30 April.
07
A state pair is queried, and ICAO republishes the participating list before the next answer.
Out
08
A Union airport is served, and Article 5 of Regulation (EU) 2023/2405 sets a yearly uplift share.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
The agent resolves scope and holds each unit with its conditions. An accredited verifier assesses it; the operator submits the report and cancels the units.
Example workflow
One state pair, unit to cancellation
AgentHuman
1Unit and route records receivedRegistry statements, programme attestations, route schedules or fuel uplift records
2Eligibility context assembledThe unit, the programme that issued it, the vintage it carries and the state pair it answers for
3Submission state draftedThe units, their conditions and the scope answer
4Controls appliedEligibility checks, vintage checks, deadline checks and completeness confidence
No human action required
Stages 1 to 4 run unaided, and nothing is cancelled at any of them — the agent is assembling, and the environment lane opens at the completeness gate.
5DecisionSplits at the completeness gate
Eligibility settled
Goes to the operator to cancel.
Anything lapsed
Adds an environment read first.
Environment review
The submission is held with its units, the conditions on them and the scope behind it.
Cancel · Append record · Send to environment
Cancelled — by the operator▼
6Unit and route records updatedOnly where write access and records policy allow it
7Outcome evaluatedEligibility accuracy, scope coverage, environment corrections and what review found
Corrections
Each environment correction is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Cancelling a unit in the registry.
Assessing a cancellation report for misstatement.
Submitting the verified Emissions Report to the State.
Deciding that a state pair falls outside scope.
Automation boundaryAgent acts unaided
✓Hold every unit with its programme and its vintage.
✓Resolve every state pair against the list now in force at ICAO.
✓Mark the unit whose eligibility has lapsed since it was bought.
✓Track four submission clocks the operator has to meet.
Nothing is cancelled or submitted except by the operator, inside the agreed boundaries.
Judging whether a unit still qualifies.
Telling a State that the fleet has offset.
Setting the scaling factor for a compliance year.
Changes to unit, route or fuel records.
Example output
One emissions unit, annotated
Our corporate travel policy agent reads a claim against policy; this record is what a single emissions unit carries.
Submission state · single unitIllustrative example
Unit
Recorded as
Vintage
Source of record
Confidence
Held for
Listed programme, one unit
Matched to the eligibility list in force
First-phase window
Registry statement, 3 August 2026
Held uncancelled
The operator, as the instrument names it
As receivedTaken from the registry statement and the programme attestation — it reaches as far as those sources do.
What the record holdsRegistry statementProgramme attestationVintage window
Why no cancellation hereWhether a unit still qualifies is settled on the list, not by a model.
ActionCancelAppend recordSend to environment
What the score decidesBelow the configured threshold the submission picks up an environment read first.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Every emissions unitFrom the programme that issued it
03Submission
Where the record is used
Our vessel emissions agent splits one consumption dataset across four instruments for a designated company person; this page asks whether a unit still qualifies and whether the scope answer has changed since last year.
01Approved path
A unit, and its conditions
The ICAO eligible-units document reached its thirteenth edition, approved 31 October 2025, and every listed programme carries authorisation, corresponding-adjustment and vintage conditions.
02Human review
What was checked, and not found
Annex 16 Volume IV was never read directly — ICAO document pages refused the request, so every paragraph reaches us through ICAO model-regulations training material — and the offsetting weighting, the ReFuelEU synthetic sub-quota and the UK obligation step for 2026 remain unconfirmed.
04Build an evidence trail
The unit, the programme that issued it and the person who cancelled stay on the report.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Fuel and flight sourcesFuel uplift records Flight and route schedules
Units and registriesRegistry statements Programme attestations
Verification and reportingVerifier query log Submitted report filings
Agent
Aviation emissions units
Reads the units Resolves scope and vintage Holds for the operator
Compliance schemesCORSIA · EU ETS UK ETS · ReFuelEU reports
Integration availability depends on the client's existing systems and API access.
Agent controls
Six conditions between the model and the operator
Six conditions, and a unit has to meet all of them. Whatever qualifies is charted in the map below.
L6 · Outermost — last line of defenceInward → L1 · closest to the model
L6Rollback / safe modeConfine the agent to eligibility assembly when evaluation or production signals degrade.Roll back
L5Version monitoringTrack model, prompt and eligibility rules; the FAA CORSIA MRV Program is voluntary, and COM(2026) 616 final of 17 July 2026 is a proposal only.Track
L4TraceabilityRecord each unit, its programme, the state pair it answers for and every read of the submission.Record
L3Operator releaseHold the submission for the operator; that hold governs release, not whether a unit still qualifies.Gate
L2Vintage guardrailsTest every unit against the eligible-units document and its conditions; the first-phase vintage window shuts 31 December 2026.Restrict
L1Confidence thresholdsRoute a thin submission to an environment read before the operator sees it.Require review
Model coreSubmission assembled — the units, their conditions, the scope and completeness
L1 – L2Test whether a submission may stand
L3Leaves the cancellation with the operator
L4 – L5Keep the unit and the programme behind it
L6Holds the cancellation unmade when signals degrade
How Nestack evaluates it
Evaluate the whole assembly — not only the submission that comes out.
Coverage runs the whole depth of the workflow, and every layer is cut by slice.
Surface — the submission a verifier assesses
Depth of coverage ▼
E1Final-output evaluationDid the submission carry the conditions each unit has to meet?
E2Step-level evaluationDid the agent read the right state pair, the right edition and the live record?
E3Tool evaluationDid it read and write the correct unit and the correct vintage?
E4Confidence calibrationDo low-confidence submissions actually attract more environment corrections?
E5Slice evaluationHow does performance change across specific state pairs?
E6Business outcomeHow many submissions needed a correction before the operator cancelled?
Floor — the obligation the operator owns
Failure modes
Where each failure originates in the agent
Seven failure modes, each placed at the stage where it first shows.
Agent lifecycleDirection of processing →
01 · Retrieval1 mode
KA-03
Stale eligibility read
The list read is not the edition now in force.
Stage gathersThe units, the routes, the dates and the records
02 · Reasoning2 modes
KA-04
Unit asserted, not shown
A unit is called eligible without its conditions.
KA-06
Proposal read as adopted
An extension still in procedure is worked as law.
Stage proposesThe units, their conditions and the scope
03 · Tool / write2 modes
KA-02
Thin submission passed on
A submission moves without the environment read.
KA-05
Unit bound to wrong state pair
A record is filed against the wrong route.
Stage writesOnly where write access and approval policy allow it
04 · Output1 mode
KA-01
Cancelled, conditions unrecorded
The report shows a cancellation but not what qualified it.
Stage returnsThe submission a verifier assesses and a State reads
05 · Change / Version1 mode
KA-07
Silent vintage regression
A configuration change moves the window, not the record.
Stage tracksModel, prompt, eligibility rules and unit fields
Sev-1 · a unit cancelled on no eligibilitySev-2 · wrong scope answer reaches the StateSev-3 · source degrades, submission holds
A state-pair-level scope-accuracy figure can read clean while the pairs that only just entered carry most of the rework. Nestack reports the correction rate by state pair, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
State pairs newly in scope
8.9%
3.6×
Review
State pairs left off the list
6.4%
2.6×
Review
Routes touching a Union airport
4.0%
1.6×
Watch
Intra-EEA routes under the ETS
1.5%
0.6×
Normal
Bar: correction-rate lift vs. intra-EEA route baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
What a lapsed vintage costs
A cycle ends when the ineligible vintage is a standing case. That suite is what the next report assembled is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Correction rate rises on state pairs newly in scope.
02Diagnose
The unit bought in good faith that the eligibility list had already moved past is read back until one cause remains.
03Improve
Changes leave numbered, and the submissions that forced them travel attached.
04Verify
One submission case still failing is enough to stop the whole release.
05Learn
The case is kept, and the eligibility rules are rewritten alongside it.
Learn → DetectThe return edge. The next submission is measured against a suite one case longer.
Typical build scope
Twelve workstreams across six weeks
The build scope set beside the delivery timeline. Week structure follows the six-week plan — discovery, sources, submission assembly, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Unit-eligibility and automation-boundary scoping.
02Fuel, route and registry sources.
03State-pair scope and unit-condition coverage mapping.
04Unit and route record ingestion.
05Unit, programme and vintage binding.
06Eligibility scoring and review routing.
07Operator cancellation workflow.
08Fuel and registry-system integration.
09Eligibility and scope cases.
10Guardrails and cancellation controls.
11Submission-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne state pair, one yearProductionProduction offsetting workflowAdvancedMultiple schemes / entities
Introduced at Pilot
Submission assembly to your routes✓✓✓
Operator cancellation release✓✓✓
Unit-eligibility baseline✓✓✓
Introduced at Production
Reporting by state pair—✓✓
Cancellation workflow in your systems—✓✓
Approved write-back—✓✓
Fuel-record integration—✓✓
Introduced at Advanced
Multi-scheme operators——✓
Cross-scheme submission packs——✓
Large route networks——✓
Multi-scheme deadline controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, network size, approval controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your routes and the schemes each one owes→Route mapping and unit-record captureWeek 1
02Representative registry, fuel and verifier records→Record binding, eligibility logic and the scope baselineWeek 2
03Your monitoring plan as the State approved it→Unit mapping, route binding and the automation boundaryWeek 1
04Access to relevant APIs, feeds or exports→Registry, fuel and verifier-source assessment, then integration setupWeek 2
05Submissions you would not want verified→Vintage cases and the evaluation suiteWeek 4
06What no emissions unit may guarantee→Eligibility scoring, review routing, guardrails and release controlsWeek 3
07A nominated focal point for the operator→Cancellation workflow, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
The bars here measure effort and not the page, and that is why two phases have to share one week.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Scheme discovery, route mapping and the automation boundaryW2Source integration and the unit-eligibility baselineW3Submission assembly, eligibility logic and release controlsW4Evaluation suite, vintage cases and failure-mode testingW5Registry integration, pilot submissions and targeted correctionsW6One compliance year run under the nominated focal point, then Agent Care handover
Reading the bandEach bar spans only the weeks its own work is named for. Two phases share the fifth because the work does.
At the end of W6When the unit record validates, Agent Care picks the agent up.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Travel & Hospitality AI agent
Build an emissions units agent around the document that decides whether a unit still counts.
Show us one unit and the programme behind it. Not a measurement problem. A provenance one: the eligible-units document reached a thirteenth edition on 31 October 2025, and the first-phase cancellation deadline of 31 January 2028 has never run. Fuel buying is a different agent.
