Ship changes to
old systems without breaking
what works.
Ask for a change in plain words. bibup maps your system, makes the change, and shows you it still works.
bibup · Split one order into two shipments
- 5places the change touches, mapped
- 4 journeys work the same on old and new
- 1 could not be checked: the carrier did not answer
01The problem
Every change to a legacy system is a gamble. Nobody sees everything it touches.
The rules live in people's heads, old tickets and code nobody has read in years. The tests pass, and something else breaks in production.
Before release
Every test passes.
$ run tests
- PASSsplit one order into two shipments
- PASSeach shipment gets its own label
- PASSthe order shows both shipments
3 passed, 0 failed
The next morning
Orders stop shipping.
Your order
Order 00419
Delayed. It has not left the warehouse.
- Ordered
- Packed
- Shipped
- Delivered
Orders that were never split stopped shipping. They wait for a split that never comes.
The tests checked the new feature. Nobody checked the orders it was not meant to touch.
02How it works
Map, plan, change, prove, learn. One loop.
It reads your code and documents, finds everything the change touches, and asks your team what it cannot find.
- 01Map
It reads your code and docs, maps the business rules, and finds every service, table and event a change reaches.
- 02Plan
You ask in plain words. bibup asks what it does not know, and your team approves the plan.
- 03Change
An agent makes the change from the approved plan, in an isolated workspace.
- 04Prove
Old and new run side by side. You get what passed, what failed, and what could not be checked.
- 05Learn
Each proven change teaches bibup your system and trains your company's own model on its code.
- Code
- HTTP
- Events
- Data
- Observed
- Derived
- Inferred
- Unknown
03What it learns
It learns the rules your team never wrote down.
Before it changes anything, bibup collects the rules, the dependencies and the history behind your system.
Rules
What the code must keep doing.
A rule
A shipment carries items from one order only.
Found in the orders code and in an old ticket
Dependencies
Everything the change reaches.
Shipping, the shipment event and order history all depend on orders.
History
Why the system is the way it is.
A past decision
Splitting by warehouse was removed.
Why, who decided it, and what it changed
04Kept apart
One agent builds. Another checks.
Both work from the plan your team approved. The one that checks never talks to the one that built it, so the check stays independent.
05Old and new
Old and new, side by side.
bibup runs the same journeys on your current system and on the changed one, then compares the results.
| The same journey | Your system today | With the change | Result |
|---|---|---|---|
| A split order ships as two shipments | Not possible | Two shipments | New, as asked |
| An order that is not split | One shipment | One shipment | Same |
| Stored orders and the shipment event | Match | Match | Same |
| Order history | Gets every change | Gets every change | Same |
| Carrier label | Label printed | No answer | Could not check |
When something cannot be checked, bibup says so, and tells you how to close it: here, one real label before release.
06What you receive
You get the change, the proof, and what's still open.
Your team reviews it like any other pull request, and decides what ships.
The change
A draft pull request in each repository it touches.
Pull requests
ordersThe split action and its statusDraftshippingOne shipment per group of itemsDraft
The proof
Every journey, run on old and new, with the result.
Evidence
- 4 work the same, or as asked
- 1 could not be checked
What is still open
What bibup could not check, and how to close it.
Open
- Carrier label: confirm with one real label before release.
07Learn
Each proof teaches bibup your system.
Every proven change adds to what bibup knows about your system. Your company gets its own model, trained on its code and its proven changes.
Your company's model
Writes your next change.
- Trained on your code and its proven changes
- Better with every proof
08Questions
Questions people ask first.
What does bibup do?
You ask for a change in plain words. bibup maps your system, makes the change, and shows you it still works.
What kind of software is it for?
Legacy, complex software that cannot go down, where one change reaches many services, tables and events.
How do I know the change did not break anything?
bibup runs every journey on your system today and on the changed one, and shows you the result of each.
Who checks the work?
A second agent. It works from the plan your team approved and never talks to the agent that built the change.
Does bibup merge or deploy?
No. The first release ends at pull requests. Your team merges and deploys.
What if something cannot be checked?
bibup says so, and tells you how to close it.
What do I receive?
A draft pull request in each repository the change touches, the proof for every journey, and what is still open.
Can I use it today?
Not yet. We are building it now. Join the waitlist and we will write when it is ready.
Built for the software that can’t take a day off.
09Early access
We are building it now.
The first release ends at pull requests. Your team merges and deploys.
By joining you agree to receive emails about bibup. Leave anytime, in one click. Privacy notice
You are in. Early access opens in batches.We will follow up with you when your place in the list comes up.
- Ends at pull requestsYour team merges and deploys.
- Checked by a second agentIt never talks to the one that built it.
- Says what it could not checkAnd how to close it.