Private prospect artifact · Not indexed · Cerebras is not a customer · Hive Civilization Inc.
proof architecture map · prepared for Andrew Feldman, Naor Penso, and the Cerebras technical team

Four filed primitives.
Pick only what the surface needs.

The Cerebras Technical Companion covers two specific proof of concept surfaces: streamed proof and wafer scale verification. This page is the wider map.

It shows, use case by use case, which of the four filed proof primitives applies, what that primitive fixes, what evidence it produces, what it deliberately does not claim, and why stacking more than one primitive is additive rather than redundant.

Cerebras does not need all four to get value. Each use case below can use only the primitives it needs.

The crosswalk The four primitives Back to the technical companion Hive Proof Architecture
purpose of this page

Filed art,
mapped to real surfaces.

Every primitive below is filed art from the provisional application Cryptographic Pre-Commitment, Pre-Submission Attestation-Level Binding, Multi-Source Divergence Detection, and Bonded Performance Attestation for Streamed Machine-Generated Inference Responses (Hive Civilization Inc., filed 31 July 2026).

why this matters on wafer scale hardwareNone of the four primitives requires, and none depends on, a hardware isolated trusted execution environment. That property is what makes them usable on wafer scale and other massively parallel architectures that do not expose that kind of enclave.

the four filed proof primitives

What each one is,
and where it lives.

The four filed proof primitives, their generic descriptors, stable page titles, public routes, and Proof Architecture anchors
PrimitiveGeneric descriptorStable page titlePublic routeArchitecture anchor
ForetokenStreamed pre commitment and terminal attestationForetoken/foretoken//canon/#foretoken
Stipryn™Pre submission proof level bindingStipryn/stipryn//canon/#stipryn
Multi source divergence detectionNon hardware attested divergence detection between asserted and observed valuesMulti-Source Divergence/multi-source-divergence//canon/#multi-source-divergence
Bonded performance attestationPerformance distribution bound to content digest and a declared budgetBonded Performance Attestation/bonded-performance-attestation//canon/#bonded-performance-attestation

Each public route above is indexable and does not link to Cerebras specific material. The noindex Hive Proof Architecture page is the shared reference point that connects those public pages back to this private prospect page and to the Cerebras partner page, which is why the navigation from this page runs to the architecture anchor for each primitive.

crosswalk · use cases and surfaces to primitives

Four surfaces.
Different primitives on each.

Streamed chat and completion endpoints

today
High throughput token streaming, where the commercial value of speed is realized specifically because tokens are streamed rather than delivered as one complete response.
primitives
ForetokenStipryn™
Foretoken adds
A fixed evidentiary starting point for a streamed response. Foretoken commits the request ID and run ID before or concurrently with the first content unit, then seals the stream with a terminal attestation that ties back to that commitment, so the full life of the stream, start to finish, is provable from a single pair of artifacts rather than from narrative alone.
Stipryn™ adds
A proof level fixed ahead of time rather than chosen after the response is already known. Stipryn™ fixes the required proof level before transmission, while the party bearing the consequence still controls the request. This keeps the evidentiary standard consistent regardless of how any particular run turns out.
evidence produced
A sealed artifact showing the full life of one streamed response, timestamped at both ends, with a proof level commitment fixed before the request left the composing party.
does not claim
It does not claim to know why a response took the time it took, it does not alter the model's output, and it does not certify the content of the response as correct, safe, or compliant.
why additive
Foretoken alone proves the stream was not backfilled. Stipryn™ alone proves the proof standard was not downgraded after the fact. Together, Cerebras gets a request to response record where neither the evidentiary bar nor the content can be adjusted with hindsight, without either primitive doing the other's job.

Silicon and model identity claims

today
A wafer scale architecture that is the physical basis of the Cerebras speed advantage, and internal knowledge of which silicon and model build served a given request.
primitives
Multi source divergence detectionForetoken, optional, for timing context
divergence detection adds
A second, independently checkable line of sight alongside a silicon or model identity claim Cerebras already makes. It binds a Cerebras asserted value and a separately observed value into one signed structure so a verifier can check consistency without needing access to either party's execution environment.
evidence produced
A signed structure that a third party can inspect to see whether the asserted and observed values agree, and that flags a signal when they diverge beyond a threshold.
does not claim
It does not give Hive, or anyone else, access to Cerebras's execution environment or wafer internals. It does not require a hardware isolated trusted execution environment. It does not claim Cerebras's assertion is false; it only makes disagreement visible if it exists. If Cerebras signs the assertion with a Cerebras held key, as proposed under Surface B of the technical companion, the trust root for that assertion stays with Cerebras, not with Hive.
why additive
On its own, a Cerebras signed assertion tells a buyer what Cerebras says happened. Divergence detection adds a second, non colluding line of sight without asking Cerebras to expose anything beyond the assertion it already chooses to make.

Service level commitments and speed based pricing

today
A real, defensible latency and throughput advantage that Cerebras already markets as a core product strength.
primitives
Bonded performance attestationForetoken anchored budget
bonded performance attestation adds
A performance claim tied to one specific run rather than selected after the fact from among candidate runs. It binds a performance distribution, measured over the actual content units of one streamed response, into the same signed structure as the content digest of that response, alongside a declared performance budget fixed before the outcome was known.
evidence produced
A single artifact that evidences both what was produced and how quickly it was produced, checkable against the budget that was declared in advance.
does not claim
It does not measure or estimate wafer compute time by itself. It measures a performance distribution over content units as delivered, and it only carries a compute characterization to the extent Cerebras itself declares or signs one. It does not set pricing and does not certify service level agreement compliance as a legal matter.
why additive
Anchoring the performance budget with a Foretoken pre commitment forecloses cherry picking twice over: once because the budget was fixed before the run, and again because the terminal attestation ties the delivered content to that same run. This is what makes a speed premium defensible rather than just asserted.

Renewal, audit, and procurement workflows

today
Enterprise buyers, and their legal, compliance, risk, and audit functions, who increasingly ask for evidence rather than a claim when a decision or renewal depends on inference performance or provenance.
primitives
ForetokenStipryn™Multi source divergence detectionBonded performance attestation All four, selected according to which question the counterparty is actually asking.
the combination adds
A receipt that already carries a pre commitment, a proof level demand, a divergence check, and a bonded performance budget, so procurement, legal, compliance, risk, audit, and renewal reviewers can draw on a single artifact rather than a fresh explanation each time.
evidence produced
A receipt that can travel with the response into procurement, legal, compliance, risk, audit, and renewal workflows without additional narrative from Cerebras.
does not claim
It is not a compliance certification and does not substitute for whatever certifications Cerebras already holds or pursues. It does not imply Hive has visibility into Cerebras's internal controls beyond the specific assertions Cerebras chooses to sign or declare.
why additive
Each primitive answers a narrow question. Buyers rarely ask only one question. Letting Cerebras select the subset of primitives relevant to a specific deal, rather than forcing an all or nothing bundle, is what makes this workflow shaped rather than product shaped.
boundaries that hold across every use case

The same four words,
on every surface.

what is requested

The client's request content, and, where Stipryn™ is used, the proof level bound to it before transmission.

what is reported

Values Cerebras declares about its own execution, carried in the receipt as Cerebras's own assertion and labeled as such.

what is observed

Timing and delivery behavior measured by Hive's instrumentation, from outside Cerebras's own reporting path. This is delivery and instrumentation observation, not wafer compute measurement.

what can be independently verified

Internal consistency of the signed structure, whether a terminal attestation ties back to its pre commitment, and, where Cerebras signs with its own key, whether that signature validates against a Cerebras published key.

scope boundaryHive does not see Cerebras GPU or wafer internals under any of the four primitives.

the two points that hold across all four primitives

Adders, not replacements.
And never load bearing.

The primitives above are adders, not replacements, across every Cerebras use case listed here. Cerebras keeps its model, its serving stack, its pricing, and its customer relationships exactly as they are; Hive adds a proof layer alongside them.

If Hive fails, is disabled, or is removed from the path entirely, Cerebras keeps running without interruption, and any receipt already issued before that point remains independently verifiable, because its evidentiary force comes from cryptographic commitments fixed at the time, not from Hive's continued operation.

additive by construction fault isolated · fail open by default receipts stay checkable without Hive
how these pages link

Private material stays
off the public pages.

The four primitive pages are public and indexable. This page and the Cerebras partner page are private and noindex. Bidirectional navigation between the public primitive pages and this private prospect material runs through the existing noindex Hive Proof Architecture page, not through direct links on the public pages themselves.

this page and the partner page

They link to each other directly, and each links out to the four primitives through the stable anchors on the noindex Proof Architecture page.

the four public primitive pages

They link into the Proof Architecture page as their shared reference point, the same as they would for any other buyer context. They do not link out to the Cerebras partner page or to this page.

the noindex Proof Architecture page

It carries the return path: it links to the Cerebras partner page and to this page, alongside the non customer disclaimer, so a reader who arrives at the hub from a public primitive page can reach the Cerebras specific material without the public pages themselves pointing at private prospect content.

what this is not

Stated before
the ask.

not a benchmarking service

Hive does not rank providers and does not publish comparative performance tables.

not a compliance certification

A signed record that a measurement was taken is not a statement of legal or regulatory compliance.

not a customer claim

This is not a claim that Cerebras is, or would become, a Hive customer.

not a shipped product announcement

This is a private prospect artifact describing filed art and a proposed proof of concept.

what it is

A map of where four pieces of filed art could add proof value across Cerebras surfaces, for Cerebras to select from as it sees fit.

Select the surface.
Hive does the build.

The two proof of concept surfaces are set out in full on the technical companion. Each use case above can use only the primitives it needs, so the first pilot does not commit Cerebras to anything beyond the one surface it picks.

PICK ONE SURFACE. HIVE RUNS THE POC.

See the two surfaces Send the surface selection Hive Proof Architecture

Companion page. The Cerebras Technical Companion carries the proof envelope, both POC surfaces, the Stipryn™ language, the bounded sandbox measurements, the receipt field sketch, and the acceptance matrices for each surface.

This is a prospect artifact from Hive Civilization Inc. Cerebras is not a customer. Nothing here implies a partnership, endorsement, deployment, agreement, or customer relationship.

Private Proof Architecture Map · noindex / nofollow / noarchive · this page is not affiliated with, endorsed by, or produced in cooperation with Cerebras Systems, and product and company names referred to here belong to their respective owners · the four primitives described are filed art from a provisional application and are patent pending · Foretoken™ and Stipryn™ are Hive marks · Hive does not observe wafer or GPU internals, and any compute characterization carried in a receipt is a provider declared or provider signed value · nothing here is a benchmark, a certification, a forecast, or a representation about any deployment · prepared by Steve Rotzin, Founder, Hive Civilization Inc. · Wyoming, USA

Cerebras technical companion · Explore Hive Proof Architecture

Canon cross reference

The exact canon entries behind this page

Each link opens that entry in the canon implementation explorer, where its schema, mint route, open verify route, auth requirement and implementation state are stated. The state shown here is read from the same registry file the explorer renders from, so the two cannot drift apart. Nothing here implies a customer, a deployment or an endorsement.

Search the explorer for Cerebras canon matching