Hiyma
LiveDesksPricing
Terminal desks
8 live · 5 building · opens in the terminal
GWRWar RoomliveConflict, shipping, chokepoints and risk zones, read spatially.GODGod-ViewliveA 3D picture of movement across the planet, including ships that go dark.NEWSNews IntelligenceliveThe global firehose as events, entities, places and market relevance.FINMarkets CommandliveEquities, commodities, FX, rates, crypto and macro on one clock.EQEquities CommandliveFrom ticker to tape: filings, events and market structure.OPTOptions CommandliveFlow, volatility, unusual activity and positioning behind the move.MOBMobility & LogisticsliveAir, sea, space and land: what is moving, what stopped, what is late.WSWorkspaceliveOne canvas: arrange any instrument around a single situation.CRYPTOCrypto CommandbuildingThe majors on a 24/7 clock: price, leverage and flows.ARMSArms IntelligencebuildingArms sales, transfers and contracts as they are announced.HEDGEBallastbuildingYour business in one terminal: exposure, drivers, hedges, stress tests.SEMISemiconductor TerminalbuildingThe AI industrial stack: labs, silicon, power and unit economics.REOReorderbuildingEight bets that the world’s plumbing is being rewired.
Terminal desks

Each desk answers one kind of question and reads the same live picture as every other, so a headline, a ship and a price move can be followed across them without changing tools.

Request terminal access
Try it, no keyAsk the live picture a questionEvery figure has a receiptSee what one carriesCompare plansFree seat to sovereign
By the question you are paid to answer
Investors & macro desks“Does the story agree with the price?”Geopolitical & country risk“Where is pressure building, and what does it touch?”Supply chain & trade“Which routes and counterparties are exposed?”Sanctions & compliance“Who is designated, and who is moving near them?”Analysts & investigators“Can I show my working?”AI agents & automation“Can my agent trust what it reads?”
By sector
Government and DefenseFinancial MarketsEnergy and UtilitiesSupply Chain and LogisticsIndustrial and ManufacturingTechnology and CyberInsurance and Risk TransferHumanitarian and Public InterestCorporate Security and Executive RiskResearch and Advisory
By workflow
Strategic WatchOne live watch lane when a country, route or book turns.Exposure MappingTrace an event to the assets, suppliers and positions it touches.Scenario LabStress a what-if before it happens.Operational BriefingA cited brief from the same picture the desks show.Compliance and DiligenceDesignations beside the entities and ships they touch.Command OperationsA shared operating picture for a crisis cell.
100 buyer profiles Find your deployment fit
See every use case
Version 2
Verifiable intelligence

The doctrine, how it is enforced, and the evidence. Every figure in the paper is measured and sealed, and any one of them can be checked from inside the paper.

Read the paper Check a figure
Part I · The argument
0Abstract1The hollow-data problem2Doctrine: never fabricate13What is not yet true
Part II · How trust is enforced
3Where every read comes from4The data spine5Enforcement, written down6Knowing what we know7The trust layer8AI under the same rules9The trust boundary
Part III · Evidence & road ahead
10Every noun is a URL11Data strategy12Evidence14Roadmap15Check the paper yourself16Glossary & references
RelatedSecurityComplianceDocumentationSystem status
Uplink
UNCLASSIFIED // FOUO
DOC_REF: HIYMA/VERIFY/v1.0

Verify

Every sealed day of every ledger, chained so no past day can be rewritten — and a checker that proves a record was in a sealed day.

Each ledger (options alerts, informed-flow scores, and soon every forward test in the Arena) seals its day under a Merkle root before any outcome is known. Each day's link commits to the previous link, so changing any past root breaks every link after it. This page re-derives the chain every time it loads.

leaf
sha256("00" + leaf value)
node
sha256("01" + left + right); an odd node pairs with itself
link
sha256(stableStringify({ scope, date, merkleRoot, leafCount, prevHash }))
proof
fits the day's leaf count: depth, index below the count, a self-paired node is its own sibling
code
lib/trust-layer/certificate.ts · lib/arena/seal-chain-pure.ts · crates/hiyma-verify · spec/vectors/trust

Loading the anchors…

Loading the seal chain…

Re-executable seals

A re-executable seal names what was computed, from what, and by which code: the Merkle root of the input rows, the sha256 of the kernel (a WebAssembly file anyone can fetch and run), and the sha256 of the output. Your browser re-runs the kernel on the rows and gets the same bytes, or it does not.

input
Merkle root over sha256(canonical(row)), rows in order
kernel
sha256 of the .wasm, served at /rx/<sha256>.wasm, rebuilt the same from crates/hiyma-rx
output
sha256(kernel(canonical({ params, rows })))
code
lib/rx/rx-verify.ts · crates/hiyma-rx · spec/rx

Re-run a computation

Hiyma

Operational intelligence with its provenance attached. Desks read the warehouse. Empty is empty.

Network
DocsStatusSecurity
Legal
PrivacyTermsExportCompliance
Modules
SignalsArmsMarketsSatellite
Uplink
Use CasesPricingAPIEnterpriseSupport
System status
© 2026 Hiyma · closed beta · access by approval

Anchors

No anchor yet: the daily anchor starts when hiyma-seal-anchor is enabled.

Every day the newest link of every ledger above goes into one document. Its sha256 is stamped with OpenTimestamps (a public calendar commits it to a Bitcoin block within hours) and signed with our key. With a day's document and its proof, anyone can run ots verify anchor.json and check that day without trusting us.

Ledgers

collect.ledger · 114 days · 2026-01-13 → 2026-05-06crypto.tape · 52 days · 2026-09-30 → 2026-11-20equities.opening · 19 days · 2026-10-23 → 2026-11-20gazette.finals · 14 days · 2026-10-02 → 2026-10-15hl.density · 20 days · 2026-10-30 → 2026-11-19hl.referee · 24 days · 2026-10-28 → 2026-11-20hl.tape · 23 days · 2026-10-29 → 2026-11-20inst.flows · 1 day · 2026-10-30 → 2026-10-30inst.ledger · 2 days · 2026-10-19 → 2026-10-23inst.report · 2 days · 2026-09-30 → 2026-10-31ml.claims · 35 days · 2026-10-15 → 2026-11-20ml.leak · 1 day · 2026-10-15 → 2026-10-15ml.models · 4 days · 2026-10-15 → 2026-11-17ml.scores · 29 days · 2026-10-22 → 2026-11-20nx.claims · 1 day · 2026-11-11 → 2026-11-11omi.supply · 38 days · 2026-10-14 → 2026-11-20options.alerts · 65 days · 2026-08-21 → 2026-11-20options.book · 1 day · 2026-11-03 → 2026-11-03options.ifs.oos · 40 days · 2026-09-25 → 2026-11-20optx.day.418c2c099d64 · 21 days · 2026-10-23 → 2026-11-20optx.hq.418c2c09 · 13 days · 2026-11-04 → 2026-11-20panel.cells · 5 days · 2026-11-16 → 2026-11-20rx.reasoner · 5 days · 2026-11-16 → 2026-11-20thirteenf.signals · 2 days · 2026-11-12 → 2026-11-15

inst.report

chain intact · 2 links

head 316d9334111689b0026243bb8cf8a73307caa7806349f7c918dfe43b84721618

dayleavesmerkle rootlink
2026-10-31106580e99d1711425a371d2292db5b9ad1221600439dce87ffb40575fe45cc3762316d9334111689b0…
2026-09-307f68fc55c3317b89caae39a2ec09378fa30c642e56bb44aa8884ef40539214d44934a3f2aa2739bb5…

Check a record

Re-deriving the chain in your browser…