Proof

Every decision,
its cost, and what it did.

The record is your product's whole story, written down as it happens. What changed, why CORA thought it would help, what it cost, and what the numbers did afterwards. It is how the stack shows its work.

Apply for the Launch Pad See how the stack works

What's on it

Nine questions a useful record should answer.

Use the same structure to compare changes over time. If a cost or result has not been measured, the entry should say so.

What changed

The change itself, described the way you would describe it to someone who does not work on your product.

Why CORA thought it would help

The reasoning, written down before the result was known — so you can argue with it, and so it can be marked right or wrong later.

What informed the decision

The relevant product history, evidence, and assumptions available when the change was proposed.

What it cost

The price of building and shipping this change, in money, sitting next to the result it bought.

Who approved it

The person who said yes, and the moment they said it.

When it shipped

The date and time it reached real customers, and how much of your traffic saw it first.

What the numbers did

The measurement afterwards, against the one thing the change was meant to move.

Whether it stayed

Kept or reversed. A change that did not earn its place comes back out, and the record says so.

What it taught the next one

The lesson CORA carries forward, so the next improvement starts from this one instead of from nothing.

Improvement · zbstack.xyz · #0001Real · our own site

What we saw: On five pages, the top image was told to load last. On slow connections, visitors saw a blank space first.
Why it happened: A “load later” setting — right further down a page, wrong for the first thing on screen. Copied onto every page built after it.
What we already knew: The largest image on the first screen should never wait. The kind of rule CORA carries from one system to the next.
What we changed: All five images now load immediately.
Who said yes: A person on the team — 22 July 2026.
What happened: The image loads the moment the page does. We didn’t measure it against live traffic, so we won’t quote you a number.
Who found it: A person, during a review. Not CORA.

Every change to this site is recorded this way

This entry documents a fix identified by a person reviewing our own site. The public entry does not report a cost, and the performance effect was not measured against live traffic. It illustrates the record format; it is not evidence of CORA independently finding or delivering the improvement.

Why it compounds

Keep the reasoning, not just the release history.

Product knowledge gets lost when decisions live across conversations, tickets, and individual memories. The record keeps the reason for a change next to what happened after it shipped.

That gives the next decision a stronger starting point and gives a future teammate a clearer handover. Its value comes from the quality of the evidence it preserves.

Each decision should start with the evidence the last one left behind.

Straight talk

What is real here, and what is illustrative.

Simulated demonstration · illustrative figures · not a customer result

The entry above documents work on our own website. The ceramics-store demonstration is scripted and uses fictional costs, timelines, and results. Those figures explain the product experience; they are not customer outcomes or pricing commitments.

Start a record
of your own.