Inari is built one jurisdiction at a time, and the method is built one capability at a time. This is an honest read of where the programme stands today — a proven micro-island showcase and a working engine spine — and the ambition stacked behind it. We hold to now / next / later rather than hard dates: the sequence is committed, the calendar isn't.
Inari is past the slideware stage. A complete micro-island showcase has been taken from raw jurisdictional data through to a populated investment case, jurisdiction report, and policy brief — the full chain, on real numbers, not an illustrative example. What proved out on that case is the part that travels: the method, the shared ontology, and the engine that runs them.
The Surplus-to-Structure chain — dossier → analysis → populated deliverable — has been walked all the way through on a live Pacific micro-island. The honesty discipline travels with it: figures render as screening-grade, gaps show as gaps, and the case is made on value kept home and resilience, never a headline return.
Roughly two-thirds of the framework is independent of any one country. A new jurisdiction inherits that universal layer and re-instantiates only the country-specific cores. The component library, deliverable templates, and evidence grammar are reusable — the micro-island is the first instance, not a one-off.
The analytical core is a mature, version-controlled engine with a substantial automated test suite kept green on every change. It emits the standard analysis set that the public deliverables are built on. This is the spine every future jurisdiction and capability plugs into.
Three lines of work run in parallel: extend the jurisdiction pipeline beyond the first micro-island, broaden what the engine can reason about, and put a grounded assistant in front of the method so people can ask it questions directly. Each step is additive — it doesn't disturb what's already proven.
The pipeline runs from New Zealand and a wider Pacific micro-island cohort through to Australia as the first industrial-nation case — anchored on rare-earth and critical-minerals processing. The same method that proved out on the showcase is re-instantiated per jurisdiction; the diversity of these cases is what stress-tests the framework's range.
The engine is being broadened to reason about more of what actually decides an outcome: water security where it's the binding constraint, the pull of real industrial demand on how surplus gets sized, and a jurisdiction's underlying resource endowment. Each capability ships in a way that leaves existing results untouched until calibrated data is in.
A public assistant that answers questions about the Inari method and the public Pacific work, and points genuine interest toward a scoping conversation. It speaks only from a curated, publishable knowledge base — about how the method works, never about client specifics or returns — so it stays useful without overclaiming.
Further out, the direction is clear even where the timing isn't. We want the engine's reasoning to deepen across the whole pipeline, the assistant to answer from live model outputs rather than a static brief, and the publishable layer to be callable by other systems. These are stated as ambition, deliberately — the order is set, the dates are not promised.
Carry the broadened capabilities across every jurisdiction in the pipeline, and add the harder layers — how governance friction and incumbent resistance shape what's actually buildable, and a validation pass that gates any external figures behind a falsifiability test. Credibility before numbers, everywhere.
Graduate the assistant from talking about the method to surfacing real, published figures on request — rendering a single public-safe metric as an evidence card, drawn only from a curated, publishable view. Built only once visitor demand for real numbers is demonstrated, and behind the same confidentiality wall.
Expose the same publishable layer so other systems and AI agents can call Inari as a tool — a partner's assistant or a DFI analyst's agent querying the public-safe slice directly. A distribution play, behind the identical wall: the publishable view is callable; the bankable engine stays private.
Screening-grade analysis and the public showcase work are open — that is what this site, the cases, and the assistant share. Bankable figures — returns, deal structures, the value-side detail — render only under engagement, at calibrated fidelity, under NDA. This isn't coyness; it's the same honesty discipline the method runs on. We would rather show you exactly how far the public layer goes than imply it goes further.
A scoping conversation is the right first step. An hour to understand the question, then a proposed product — or an honest signal that the framework isn't a fit yet. No generic capability deck.
A scoping call is free. The first deliverable is fixed-fee.