attempts
01 · THE REQUEST
A CUSTOMER REQUESTS ICE DATA.
Northstar Capital is a fictional global asset manager. At the end of the trading day, its portfolio systems need pricing and reference data to value positions, update risk, prepare reports, and support downstream operations.
THE REQUEST SUPPORTSPORTFOLIO VALUATION
→RISK→REPORTING→OPERATIONS
DATA REQUESTEDEnd-of-day fixed-income pricing + reference data
MODELED PACKAGENorthstar EOD · 2026.09.16-A
ENTITLEMENTAUTHORIZED Why was this request allowed? →
DELIVERY WINDOWEND OF DAY
CUSTOMERNorthstar Capital
The data matters because Northstar uses it after delivery.
02 · THE RETRY
ONE DELIVERY. TWO TRANSPORT ATTEMPTS.
The first attempt was sent, but no customer acknowledgement was recorded. The delivery service retried the same package. The second attempt was acknowledged.
- Transport attempt 001 sentPACKAGE A
- Acknowledgement window elapsedUNCONFIRMED
- Retry 002 linked to attempt 001RETRY
- Transport attempt 002 sentPACKAGE A
- Customer acknowledgement recordedACK-NC-7712
RESOLVES TO
under the modeled rule
THE TRANSPORT LOG HAS 2 ATTEMPTS. THE CUSTOMER ACKNOWLEDGED 1 LOGICAL DELIVERY.
WHY DOES THE RESULT EQUAL ONE?
THE REVIEW QUESTION
A later review needs to connect the retry relationship, package fingerprint, entitlement, customer acknowledgement, and agreed rule. This modeled retry sequence is not presented as documented ICE production behavior.
03 · THREE VIEWS
THE SAME DELIVERY, SEEN THREE WAYS.
Each party keeps its own operating systems. Hive preserves selected accepted events so both can review the same delivery without pretending their internal systems are identical.
ICE OPERATIONSDELIVERY REVIEW
Acknowledgement not recorded
OUTCOME UNCONFIRMEDCustomer acknowledgement ACK-NC-7712
ACKNOWLEDGED- SAME PACKAGE VERSION?
- ✓
- SAME RECORDED PAYLOAD FINGERPRINT?
- ✓
- HIVE EVIDENCE RECEIPT
- ICE-DEMO-ACK-03
- RESULT UNDER AGREED SYNTHETIC RULE
- 1 ACKNOWLEDGED DELIVERY
ICE systems remain authoritative for operational and commercial decisions. Hive preserves the selected evidence used in this demonstration.
ICE DELIVERY EVIDENCENorthstar Capital
MODELED CUSTOMER EXPERIENCE1
acknowledged logical delivery
- Data requested
- EOD pricing + reference data
- Purpose
- Valuation and risk
- Package version
- 2026.09.16-A
- Acknowledged delivery
- 1
- Network retry
- 1
- Entitlement status
- Authorized
- Customer acknowledgement
- ACK-NC-7712
- Evidence state
- ✓ RECORD CONSISTENT
The customer does not need access to ICE's internal systems to retain the evidence relevant to its delivery.
Technical evidence →
- Request ID
- DEMO-REQ-001
- Logical Delivery ID
- LD-8841
- Transport attempt IDs
- 001, 002
- Attempt relationship
- 002 retries 001
- Recorded payload digests
- same digest
- Customer acknowledgement
- ACK-NC-7712
- Hive evidence receipt
- ICE-DEMO-ACK-03
- Signature
- ✓ Valid
- Signed record integrity
- ✓ Matches
- Synthetic capture completeness
- ✓ Complete for defined demo boundary
- Independent source truth
- Not established
- Commercial interpretation
- Defined by synthetic demonstration rule
04 · TEST A MISMATCH
TEST A MISMATCH.
Change one fact and watch the two evidence views stop reconciling.
Choose a mismatch to see exactly where the records stop matching.
05 · RESOLUTION
THE VALUE IS NOT THE RECEIPT BY ITSELF.
THE VALUE IS A SHARED, CHECKABLE EXPLANATION WHEN ICE AND A CUSTOMER NEED TO REVIEW THE SAME EVENT.
Instead of“Your number is wrong.”The review becomes“We differ on this event, this field, or this rule.”
THAT IS THE PRODUCT.
06 · EXPANSION
ONE EVIDENCE PATTERN. MORE THAN ONE ICE WORKFLOW.
The first test stays narrow. The same pattern may apply anywhere ICE and another party need to review selected records around one event.
ENTITLEMENT EVIDENCE
Identity or agent → delegated authority → ICE entitlement → permitted use → access decision → delivery
ICE already shows what it delivered. This adds why that customer, person, app or agent was cleared to get it. Open it →
LICENSED DATA DELIVERY
Request → entitlement → delivery → retry → acknowledgement
MCP / AUTOMATED DATA ANSWER
Authorized machine request → dataset → answer → evidence
COMPASS ANALYTIC
Input state → analytic result → downstream use → evidence
CORPORATE ACTIONS
Action → position → delivery → amendment → retained history
CLEARING DECISIONS
Policy → calculation → review → decision → downstream record
BEST EXECUTION
Trade → method → score → review → recalculation
MORTGAGE SERVICING
Loan event → action → human handoff → correction
CROSS-SYSTEM EVENTS
Instruction → related events → participant records → review
WE DO NOT START WITH ALL EIGHT.WE START WITH ONE QUESTION.
07 · NEXT STEP
PICK ONE WORKFLOW. WE'LL SKETCH IT TOGETHER.
You choose the workflow and who should see it. We map what would land on the record. Hive stays beside it as an observer.
For entitlements, the first focus ICE named, there is also a 90-day test* on the table. * Entitlements only. Nothing has been agreed.
A SKETCH COVERS
- Volume
- Authorized source events
- Business question
- Reviewing roles
- Counting or review rule
- Responsibilities
- Retention
- Success criteria
IF HIVE IS UNAVAILABLE, ICE KEEPS OPERATING.
THE QUESTION
Could ICE and the customer reconstruct the agreed delivery question from one shared record more easily than with today's review process?
THE CONCRETE EXAMPLE
ICE and a customer may have different records around the same delivery. Hive gives selected events a signed common evidence package so both sides can reconstruct what happened and see exactly where a mismatch begins.