Days 1 to 14
Set up beside it
Agree one workflow. Hive connects to a read-only copy of the delivery events. Delivery doesn't change.
The entitlements test, modeled*
Here's what the 90 days look like. Starting takes four decisions.
We'd run it on one workflow with one customer who's willing to take part. Hive stays outside the delivery path, and either side can stop at any time.
Days 15 to 60
Let records build up
Every delivery lands on the record. A one-page report every Friday says if anything needs a person.
Days 61 to 80
Try to break it
Four planned tests, each approved by ICE: a forced retry, a withheld acknowledgement, an altered copy, a correction.
Days 81 to 90
You pick the events
ICE picks real events. Both sides rebuild them from their own copy. Then ICE decides go, change or stop.
Watch the 90 days
On most days, nobody has to do a thing.
A modeled run of the test on one end-of-day pricing workflow. The numbers are synthetic, and the assumptions are listed under the simulation.
Day1of 90
Phase · Set up beside it
All 90 days, one square each
- Deliveries, all checks pass
- Needs a person
- Planned break test
- Proof days
- Weekend
Deliveries on the record0
Retries tied to their delivery0
Missing acknowledgements flagged0
Corrections kept in order0
Planned break tests caught0 of 4
Record checks that pass0
What happened
Who is doing what this week
ICE
CUSTOMER
HIVE
Modeled assumptions
One end-of-day pricing workflow for one customer. . Retries on about 2 in 100 files, a missing acknowledgement on about 1 in 200, a correction on about 1 in 100. Four planned break tests between days 61 and 80. Weekends have no deliveries. Holidays are not modeled. These are placeholders for the simulation, not ICE figures. Day 1 of the real test replaces them with real figures.
Friday reportWeek 1
Setup week. Nothing to review.
One page, every Friday, to the ICE owner and the customer contact. If nothing needs a person, it says so in the first line.
Day 90 readoutModeled
Three questions, three answers.
- Did the record catch every agreed event?Shown on Day 90
- Could both sides rebuild the events ICE picked?Shown on Day 90
- Did it catch the planned break tests?Shown on Day 90
Then ICE decides
GoChangeStop
How to start
Four decisions. Hive does the rest.
Make the choices below and the page builds the plan, with real dates. You can copy it as a kickoff note.
* The 90-day test is offered for entitlements only, the first focus ICE named. Nothing has been agreed. For other ICE surfaces, see other options.
1
The workflow: entitlements
Our suggestion: end-of-day pricing. It runs every business day, so 90 days gives about 60 delivery days of real history.
2
Pick one customer
Best fit: a customer who already asks "did we get it" questions. The customer stays anonymous in anything Hive shows outside the test.
3
Name one owner at ICE
About an hour a week: read the Friday report, answer questions. That's our estimate, confirmed on Day 1.
4
Pick Day 1
A Monday works best. Everything else is dated from it.
Your test on one page
- Workflow
- Customer
- ICE owner
What Hive needs from ICE
- A read-only copy of the delivery events ICE already logs for that one workflow: request, entitlement decision, send, acknowledgement, correction
- No data content and no restricted fields. Fingerprints are made from the content, so the record never holds the content itself.
- Whatever feed is easiest for ICE, such as a daily file drop or an event stream
- A 60-minute kickoff and one customer contact
- A mutual NDA and a one-page test agreement, signed before Day 1
What Hive does
- Sets up beside the workflow, outside the delivery path
- Keeps the record and gives ICE and the customer their own copy, with ICE approving what the customer's holds
- Sends the Friday report
- Runs the planned break tests with ICE's approval
- Writes the Day 90 readout
Time on ICE's side
| Kickoff | 1 hour, once |
| Event copy setup | 1 to 2 days of engineering, once |
| Owner | About 1 hour a week |
| Day 90 readout | 1 hour |
Hive's estimate, confirmed on Day 1 once we see the workflow.
Ground rules
Nothing about ICE's delivery changes.
- Hive is never in the delivery path. If Hive is down, ICE keeps delivering.
- Either side can stop at any time
- ICE and customer systems stay the source of truth
- In the test, Hive signs as the third party. ICE can add its own signature at any time
- If ICE asks, Hive deletes its copy within 30 days and confirms in writing. The copies ICE and the customer hold stay theirs.
- ICE approves what goes in the customer's copy
- Where the record is kept, and who can reach it, is agreed on Day 1
- A mutual NDA and a one-page test agreement are signed before Day 1