Adopt a durable job queue
Background work was lost on deploys. The team compared a managed queue, database polling, and in-process retries before choosing a durable path.
- Owner
- Kai
- Why
- Reliable retries
Shiplog · decision and release log
Keep the reasoning behind what shipped.
Shiplog links engineering decisions to releases, preserving the reasoning behind shipped work. Record the context, alternatives, and owner of a decision, then link it to the release it shaped so teammates can understand why it shipped.
Start with example records, then record a release and inspect its linked decisions. The example records are invented and use no customer or production data. Records you add stay in this browser.
Shiplog evaluation brief
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.
Shiplog pilot scorecard
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.
-
Release reasoning retrieval
Your evaluating team must time how long it takes to find a selected release’s linked decision and identify its context and alternatives.
- Buyer target
- ________
- Observed result
- ________
- Owner
- ________
-
Record completeness
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.
- Buyer target
- ________
- Observed result
- ________
- Owner
- ________
-
Team handoff
Your evaluating team must ask a teammate to review a handed-off record and count unanswered questions about why the work shipped and who owns it.
- Buyer target
- ________
- Observed result
- ________
- Owner
- ________
-
Data-handling requirements
Your evaluating team must compare browser-local storage, retention controls, and export behavior with your data-handling requirements; record requirements checked and any gaps.
- Buyer target
- ________
- Observed result
- ________
- Owner
- ________
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. Copying 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: understand your AI spend.
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.
The decision the AI FinOps example produces.
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.
Building the example decision
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.
The decision and release log · further down this page
Know why it shipped. Decide what’s next.
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. Ask Wawalu about getting Shiplog: the follow-up form at the foot of this page, which sends your work email to that team and nothing else.
One recorded decision, and the release that shipped it
- Decision
- Adopt a durable job queue · Accepted
- Shipped in
- Release v1.3.0 · Completed
- Owner
- Kai
Example records These invented records demonstrate Shiplog. They use no customer or production data.
Deployment check
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.
Where everything is
Shiplog is the decision and release log. The browser tools and demonstrations listed below share this site but are not part of it.
The Shiplog product
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.
- Decisions Record a decision with its context, alternatives, and owner, then search and filter the history.
- Releases Every release, newest first, with its linked decisions.
Browser tools
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.
- AI FinOps Find where to act first on your AI spend: score your provider export in this browser tab.
- Prompt coach Grade a prompt against a bundled rubric in your browser tab, then revise and grade again.
Demos
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.
- Social Read posts and images, or publish your own post under a display name.
- People Pick a display name, see its image posts, newest first.
- Paint Create and export your own image, then publish it in a Social post under a display name.
- Agent observatory Watch a synthetic engineering team build and review work, beside merged pull requests counted from public GitHub activity.
Counted, not invented
Merged pull requests
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
Grade a prompt in your browser.
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
Follow one decision from record to release.
Each card below opens the full record it summarizes.
v1.3.0 · Throughput and latency
The durable queue shipped alongside a read cache, keeping the release outcome connected to the decisions that shaped it.
- Owner
- Kai
- Linked
- 2 decisions
Field notes
What we changed, and what we learned
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.
New record
Record a decision
Decisions and releases
All records
10 records
Includes example records to demonstrate Shiplog. They use no customer or production data.
Checking the log for an open decision past its review point…
Applies to decisions. Choosing a status shows decision records only.
Shows decisions associated with the selected release.
- Proposed
- Someone wrote it up. The team has not committed to it.
- Pending
- Under review. Waiting on the owner to call it.
- Accepted
- The team committed to it. Build against this one.
- Superseded
- A later decision replaced it. It stays in the log as history.
- Current only
- Hides every decision that another decision names under Replaces, whatever its status.
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 decisions
Loading all decisions…
Portable history
Export your Shiplog records
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.
Which records differ
Portable history
Import from JSON
Choose a file exported from Shiplog. It is read in this browser only — nothing is uploaded, and nothing is saved until you confirm the summary.
Representative release
See decisions move into a release
This example uses the same release model and linked decision records as the full release history. Expand it to inspect the associated decisions.
Loading release
Finding the latest release…