Shiplog · decision and release log
Shiplog records each decision's context, alternatives, and owner, and links it to the release it shaped.
Record a decision, then link it to the release it shaped. The example records are invented and use no customer or production data. Records you add stay in this browser.
The decision and release log · the product this page carries
Shiplog records decisions, tracks the releases they shape, and keeps the link between them. A teammate who arrives six months late opens the release and reads the reasoning behind it, instead of reconstructing it from chat history. Recording, searching, filtering, exporting, and importing the log are all further down this page.
How a team gets Shiplog: by asking the team that operates it. There is no self-serve signup and no published price — Shiplog is a demonstration product built and operated by Wawalu, so whether it is available for your team and what it would cost are both answered on request. The follow-up form at the foot of this page sends your work email to that team and nothing else.
Example records These invented records demonstrate Shiplog. They use no customer or production data.
Does the real record of this deployment name the running build’s version?
Checking the running build now…
It reads the running build when the page loads. The example decision and release above are invented; this answer is not.
New record
Records you add stay in this browser only. This is a demo workflow, not a customer result.
Next, record the release this decision shaped. The new decision will be listed under Linked decisions there, already ticked.
Record a release on ReleasesThis decision is stored in this browser only. It is a demo record, not a customer result.
Decisions and releases
Includes example records to demonstrate Shiplog. They use no customer or production data.
Checking the log for an open decision past its review point…
Search updates as you type. Use ↑ and ↓ to move between records, and Home and End to jump. Press Enter to open details. Every row keeps its linked decisions or releases, whatever the filters hide.
10 records
Loading all decisions…
Export history
Counting locally stored records…
The file follows your history filters by default. Choose the second option to export every stored record, whatever the filters hide.
The JSON file includes only decisions, releases, and their preserved links stored in this browser.
See what this browser is keeping — the retained records, how sure the page is about them, and how to erase them.
Compare that file against the stored records listed above, in this browser. Example rows are not part of the file, so they are not compared. Nothing is downloaded and nothing is sent.
Not checked yet.
Import history
Choose a JSON file exported from Shiplog; only its decisions, releases, and their links are restored. It is read in this browser only — nothing is uploaded, and nothing is saved until you confirm the summary.
Representative release
This example uses the same release model and linked decision records as the full release history. Expand it to inspect the associated decisions.
Finding the latest release…
Engineering teams need to explain why work shipped without reconstructing decisions from chat history. Shiplog records the context, alternatives, and owner of a decision and links it to the release it shaped, so teammates can trace shipped work back to its reasoning.
Decisions and releases you add stay in this browser; they are not shared hosted records. Shiplog is a demonstration product built and operated by Wawalu. Availability and pricing are provided on request.
The example decisions and releases are invented, use no customer or production data, and are not customer results. To verify what this site shipped, open the real record of this deployment.
Share this brief and the page link with a manager or procurement stakeholder.
Download Shiplog evaluation brief
One plain-text file with the brief, blank pilot scorecard, and public links, ready to forward. No visitor records or form entries are included. If your browser opens the file, use Save As to keep it.
Select the text and use your device’s copy command.
For your evaluating team to complete during a pilot and share with a manager. Set your own targets before measuring; all targets, results, and owners below are blank. No pilot outcome is claimed.
Your evaluating team must time how long it takes to find a selected release’s linked decision and identify its context and alternatives.
Your evaluating team must count sampled decisions with context, alternatives, owner, and status, and sampled releases with the expected decision links; record counts and sample sizes.
Your evaluating team must hand a record to a teammate as a file: press “Download JSON” on the Home page to export it, send the file to your teammate, and have them open it with “Choose JSON file” on the Home page in their own browser and confirm the summary. Both controls are on the Home page only: the Releases page has a separate “Export releases as JSON” button and no import control. Count their unanswered questions about why the work shipped and who owns it.
Your evaluating team must compare browser-local storage, retention controls, and export behavior with your data-handling requirements; record requirements checked and any gaps.
The example decisions and releases are invented, use no customer or production data, and are not customer results.
Page: https://labs.wawalu.org/
Copy this blank template, then fill it in with your team outside Shiplog. The copy also says where to ask about availability and pricing, and includes no visitor records or form entries.
Select the text and use your device’s copy command. Fill in the blanks in your shared copy.
Runs on your own work
AI FinOps publishes a worked decision that answers one question: where do we stand on AI spend, and what should we do first? It is a bundled synthetic example. Reading it takes no export of yours, no sign-in, and no account.
Your files do not leave this tab. Exports are read and analyzed in this browser. No upload, no credentials, no account. The file itself is never saved; monthly totals stay on this device only if you choose to keep them.
It answers where AI spend stands, how much of it is recoverable, and the one action to take first. Open it to check the benchmark, the confidence, the provenance, the limits, and the arithmetic behind that figure.
The example decision is being assembled in this tab, which takes a moment. Its three synthetic months ship with this page.
The printable briefing appears when the example is finished.
Your own numbers: analyze a provider export in AI FinOps, then read the same briefing built from the months you kept on this device.
AI FinOps reads a provider export from OpenAI, Anthropic, Azure OpenAI, Google Vertex AI, or AWS Bedrock, as CSV, TSV, JSON, or JSONL. No export to hand? The bundled synthetic example opens on a finished result, so you can read the whole analysis before you find a file.
Shiplog is the decision and release log. The browser tools and demonstrations listed below share this site but are not part of it.
These two pages are Shiplog itself: the log of decisions, and the record of the releases those decisions produced. Asking Wawalu about getting Shiplog means asking for these. Everything else on this site runs beside them, not inside them.
Two separate tools. Each one runs in this browser tab on what you give it, each is useful on its own, and neither is part of Shiplog: you can keep a decision and release log without them.
The posts and images already published on Social and People are invented sample content, as are the Agent observatory’s personas and prompt trace. The observatory’s merged pull request count is the exception: it is counted, not invented. A post you publish on Social is real: anyone who visits Shiplog can read it.
We designed, built and shipped Social, People, Paint and Agent observatory, and recorded the decisions and releases behind them here: they demonstrate the build-and-ship loop this site is for. They are demonstrations, not features of Shiplog.
Counted, not invented
Counting the merged pull requests from public GitHub now.
This block counts merged pull requests in AndrewLikesTea/paint-lab and AndrewLikesTea/wawalu-agent-lab, and links the public GitHub event feeds it counts them from.
These merged pull requests built and changed the pages of this site.
The one counted figure on this page Every other number here belongs to a bundled synthetic example, computed from invented data for an invented company. This one is counted from public GitHub activity when the page loads. When GitHub does not answer, the last count this browser took is shown with the time it was taken, and nothing at all is shown if there has never been one.
Prompt coach · nothing to install, nothing to upload
The Prompt coach scores one prompt for intent, efficiency, and model fit against a bundled rubric, names the single change worth making first, and lets you revise and grade again. A worked example is already graded when you arrive, so there is a real result to read before you paste anything. No sign-in, no upload, no storage, and no request to a model.
Open the prompt coachAlready have an export of your own AI history? Read weeks of your own prompts in Personal AI history. It runs the same rubric over that export in this browser tab, then names the one habit worth changing first and whether it is moving.
Keep reasoning with the work
Each card below opens the full record it summarizes.
Background work was lost on deploys. The team compared a managed queue, database polling, and in-process retries before choosing a durable path.
The durable queue shipped alongside a read cache, keeping the release outcome connected to the decisions that shaped it.
Field notes
Field notes come from the Wawalu team that operates Shiplog. Each note is a short write-up of what the team changed or learned building it. There is no schedule. The first note goes out when it is written.