A walkthrough of provLedger: a colleague asks for a discount rate on the weekly tile, and the record shows it was built in May and taken out in June — why, what was tried instead, who said so and how widely it was shared — before the session drafts the reply. The ledger shown is a worked example, not a live database.
Yes. A discount rate was built for the weekly tile on 14 May and removed on 30 June. #e38 #e52
You said why on 3 June: “take the discount rate off the weekly tile until the v2 feed carries discounts again.” #40
The v2 orders feed had stopped carrying orders.discount; data platform said so on 29 May. #r7
Backfilling it from the v1 archive was tried and dropped: the archive keeps 90 days, the quarter needs 190. #43
An estimate from list_price was tried too: expected within half a point, measured 8.1% against 14.7%. #x5 #o5
A rule has stood on the tile since then: do not depend on orders.discount. #41
Hi Priya — we did build this. A weekly discount rate went on the tile on 14 May and came off on 30 June #e38 #e52.
It came off because the v2 orders feed stopped carrying orders.discount: Mei Lin on data platform wrote that on 29 May #r7, and the Q2 metrics review agreed to take it off the tile until v2 carries discounts #r8 #40.
Two ways around it were tried. Backfilling from the v1 archive did not work: it keeps 90 days and the quarter needs 190 #43. Estimating it from list_price was expected to land within half a point and came out at 8.1% against 14.7% #x5 #o5.
So it comes down to one thing nobody has recorded since: whether v2 carries discounts now unstated. That is worth checking with data platform before we build it again.
One project, seen three ways — and every piece of knowledge it holds carries the source it came from.
A request that sounds new, and the record showing it was already tried. The ledger in this walkthrough is a worked example, not a live database.
People forget. Your agent doesn't.
Not just what changed — the decision behind it.
claude plugin marketplace add yizhao95/prov_ledger
Interface wording is the product's own; the ledger shown here is a worked example, not a live database. The dashboard is read-only and opens the database read-only, so it can never block or change what it is showing. The reply is written by the session's own model from the material provLedger assembles — provLedger writes none of it, and nothing is ever sent automatically. The command's name is still provisional. Try it with claude plugin marketplace add yizhao95/prov_ledger.