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
Decision and release log for engineering teams
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.
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
Representative synthetic records These invented records demonstrate Shiplog. They are not customer or internal operational data.
Also on this site · separate demo
AI FinOps is a spend demo, not part of the log: score your own provider export in AI FinOps for intent, efficiency, and model fit. Your files do not leave this tab.
Score your provider export in AI FinOpsWhere everything is
- Decisions Record a decision with its context, alternatives, and owner, then search and filter the history.
- Social Social is a shared demo feed of short posts about the work the team ships, each with an optional image.
- Profile Social narrowed to one display name: its image posts only. Ari is a demo name, not your account.
- Releases Every release, newest first, with the decisions it carried.
- Paint Draw or crop an image in this tab, export a PNG, then hand it to a Social post yourself.
- AI FinOps Score a provider export for intent, efficiency, and model fit, then see where the spend is not working.
- Agent observatory Watch a synthetic engineering team plan, build, review, and deliver work.
Keep reasoning with the work
From a hard call to a shipped outcome.
Shiplog preserves what the team knew, what it considered, and who owned the call—then connects that reasoning to the release. New teammates get context without archaeology, and future decisions start with evidence instead of memory.
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
Decision-making, unpacked
See how teams make better decisions
Get a concise field note on the habits, templates, and tradeoffs behind durable engineering decisions.
New record
Record a decision
Decisions and releases
All records
10 records
Includes representative example records to demonstrate Shiplog. They are not customer or internal operational data.
Applies to decisions. Choosing a status shows decision records only.
- 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.
Loading decisions
Loading all decisions…
Portable history
Export your Shiplog records
Counting locally stored records…
The JSON file includes only decisions, releases, and their preserved links stored in this browser.
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…