BunkerOS: One Ledger From Nomination to Claim

A bunker fuel quality dispute doesn't get resolved quickly, and the reason usually isn't the dispute itself — it's that the evidence needed to resolve it lives in five disconnected places. The original nomination is in an email thread. The scheduling change is in a spreadsheet someone updated by hand. The delivery note is a PDF attached to a different email. The lab report arrived separately, days later. And by the time a claim is actually filed, someone is reconstructing a timeline from all of it under deadline pressure, hoping nothing got lost along the way.

BunkerOS is the OS Series' second marine system — built by Xamun and delivered by BlastAsia — and it exists to eliminate that reconstruction step entirely, by chaining every stage of a bunker fuel transaction to one tamper-proof ledger from the moment it starts.

Five Stages, One Chain

BunkerOS links nomination, scheduling, execution, quality audit, and claims into a single continuous record. Each stage writes to the same ledger the moment it happens, so by the time a claim is filed — if one is filed at all — the full evidentiary trail already exists. Nobody has to go looking for it.

Nominations come in through AI-parsed intake: incoming nomination details, whether from email or a structured form, are parsed automatically to reduce manual entry. Critically, nothing gets written to the ledger until a human confirms it — the AI drafts and extracts, it doesn't commit. That distinction matters for a system whose entire value proposition is that its records are trustworthy enough to settle a dispute.

Quality Auditing Backed by a Live Regulatory Graph

Bunker fuel quality compliance runs on international standards — principally ISO 8217 for fuel specifications and ISO 4259 for test-result precision — and those standards get revised, and interpretations of them shift with enforcement practice. BunkerOS's quality-audit stage checks delivered fuel against these specifications using a live connection to GraphIQ, Xamun's regulatory knowledge graph, so the audit reflects current spec limits rather than whatever was true when the system was configured.

If that live connection isn't available — a connectivity gap, a graph service interruption — BunkerOS falls back to a local deterministic rule set rather than failing the audit outright, so quality checks don't stop just because the network does.

Rules That Change Deliberately, Not Accidentally

The compliance rules governing quality audits and claims processing are managed through a dual-approved, versioned rules-pack system: any change to the rules requires two authorized approvals before it takes effect, and every version is retained. This matters because a rules change that happens quietly — one person updating a threshold without review — is exactly the kind of thing that undermines confidence in an audit trail. BunkerOS makes rule changes deliberate and visible.

Claims That Don't Miss Their Deadline

Bunker fuel claims are time-barred — miss the contractual or statutory window to file, and the claim is gone regardless of merit. BunkerOS tracks these deadlines automatically against the transaction timeline, and when a claim is filed, it assembles a hash-sealed evidence bundle — the nomination, scheduling record, delivery documentation, and quality audit results — as a single tamper-evident package, rather than something a claims team has to compile by hand under time pressure.

Built for the People Actually Placing Orders

Buyers interact through a mobile-first portal, reflecting the reality that bunker orders and status checks often happen from a vessel or a port office, not a desktop. Throughout the system, AI stays confined to drafting and parsing — extracting structured data from a nomination, flagging a possible spec issue for review — never to autonomous decision-making on quality determinations or claims outcomes. Those calls stay with the people accountable for them.

Configurable Beyond the Gulf

BunkerOS launched with Gulf bunkering operations as its first market, and its ISO 8217/ISO 4259 quality-audit logic and GraphIQ regulatory backbone are built around international marine fuel standards rather than a single jurisdiction's rules. For operators outside the Gulf, the same nomination-to-claim chain, dual-approved rules-pack governance, and time-bar tracking can be configured around local port procedures, additional regional quality standards, and jurisdiction-specific claims timelines — the architecture doesn't assume Gulf operations, it started there.

Delivered Through BlastAsia's Engagement Models

Like the rest of the OS Series, BunkerOS is built by Xamun through the Xamun Software Factory and delivered by BlastAsia through its Turnkey or xDD engagement models, with regulatory and port-specific configuration scoped as part of onboarding.

For bunker fuel suppliers and traders who've felt the cost of a slow, evidence-scattered claims process, the case for BunkerOS is straightforward: the record that would eventually be needed to resolve a dispute should already exist by the time the dispute happens — not get assembled after the fact, against a deadline, from five different places.

If you're running bunker fuel operations and want to see how BunkerOS handles your specific quality standards and claims process, let's talk through your operation.