← Hive × Equinix · the ingestion map
Prepared privately for Equinix · not a customer, partner, or endorsement

Fabric already has the stops.
Hive gives each one a receipt.

You built the neutral place where AI providers, enterprises, and clouds meet. Every one of those meeting points is a decision waiting to be proven. Here is exactly where each Hive primitive clicks into Fabric, what it reads, and what it hands back. Nothing in this map moves customer data.

Prompt. Proof. Provenance. The proof is in the provenance.

Fabric surface · Hive primitive · what it produces

Four Fabric surfaces. Four places a receipt attaches.

Read each row left to right: the Fabric surface you already run, the Hive primitive that rides beside it, and the signed artifact it produces. The primitive reads a fingerprint and a rule number. It never reads the payload.

Fabric surface Distributed AI Hub The on-net place a customer's AI decision is made, next to the model and the data it needs.
Hive primitive Proof Pre-Fill The instant a decision forms, the receipt is prepared and bound before the action fires, by fingerprint only.
Produces A ready receipt at the moment of decision No lag, no after-the-fact reconstruction. The proof exists as the decision does.
Fabric surface Interconnection · the port itself The virtual connection where one party's traffic crosses to another. Your core meter.
Hive primitive InkFrame non-mutation A content-addressed envelope sealed by its own hash. Change one byte and the address changes, which breaks the signature.
Produces A tamper-evident record of what crossed Anyone can recompute the hash to verify it. Non-mutation is provable, not promised.
Fabric surface Geo Zones for Fabric Where you already control the location a workload runs. The "where" answer.
Hive primitive Disclosure-Free Replay Reconstruct the exact route and cue surface of a decision from offsets and fingerprints, with no payload present.
Produces Proof the route held, without moving the data Turns "the data did not leave the zone, trust us" into "here, check the route yourself."
Fabric surface Fabric Intelligence · routing Where Fabric decides how and where a flow moves across the hub.
Hive primitive Arrival Countersignature The gateway counter-signs on arrival, so what actually ran is proven to match what was cleared to run.
Produces Proof of the journey, not just the origin Covers the whole hop across the hub, end to end, in one signature chain.

The canon is larger than four. These four are the ones that touch Fabric directly. The full Hive primitive set sits behind them, and the same signing substrate carries all of it.

How a decision becomes a receipt inside your hall

One decision. One pass through the map.

Watch a single decision move through the four attach points. The bright travelling line is the receipt. The customer's data never leaves the box on the left.

Reads a fingerprintHive sees a SHA-256 of the decision and a rule number. Never the prompt, the data, or the recipient.
Signs beside the workThe receipt is built and hybrid-signed next to the decision, not in front of it. Zero added delay to the customer's path.
Hands back proofEquinix holds a portable, independently checkable receipt. The customer's data stays exactly where it was.
Operational discipline · how we keep the rail honest

We run soaks as a matter of routine.

A signing rail is only worth what its worst day proves. So we run continuous, long-duration soak passes against the engine and read every one for lost, mismatched, duplicate, cross-tenant, and unverifiable receipts. It is standard practice here, not a milestone we are waiting on. Every pass is itself signed, so the discipline is checkable, not asserted.

0
integrity failures at the last benchmark gate, across 5,000 frames
0
tamper escapes: every altered frame was caught
signed on every receipt: Ed25519 and ML-DSA-65, FIPS 204
100%
of runs shipped with a signed manifest you can re-verify yourself

The honest line stays honest: the numbers above are from a reference build, and the same soak discipline runs continuously against the engine as a matter of routine, every pass itself signed. The point is that nothing here rests on a single number. The discipline runs on a schedule, and you can check any pass yourself.

Hands on the wheel · no account, offline, your machine

What your team can run today.

Everything below is provable by you, not asserted by us. The verifier kit is a small offline package. It ships only the public-safe verification code; the proof-sizing logic stays private, so there is nothing sensitive to pass around.

1
Verify a real signed receipt. Recompute every hash, then check both signatures against the published keys. Two minutes, offline.
2
Break it on purpose. Change one byte and watch verification fail. This is the non-mutation promise made testable on your own screen.
3
Re-verify our benchmark. Recompute the 5,000-frame manifest root and check its signature. The numbers become yours to confirm, not ours to claim.
4
Reconstruct a route with no payload. Rebuild exactly which cues sat where, from fingerprints alone. The direct answer to showing a route without moving the data.

Node 20+ required · runs offline · no account · no network calls · four checks, one command. The verifier page has the download and the one-command run guide.