How work lands / Page 37 of 70
This page is one part of The Ishoo manual. The complete manual is a single page, short enough to read in one go: ishoo.app/docs/
Tests and the trace
An agent says it's done when its own view says so; nothing outside checks. Ishoo records the tests each landing says it ran, counts landings that named none, and runs the full check on main every night, finding the landing that broke it. Every landing is traced.
“Done” from an agent means the agent believes it's done. Sometimes it ran nothing; sometimes it ran tests that didn't cover the change; sometimes it fixed the symptom. Ishoo doesn't try to stop every one of those at the door, because a gate on every landing slows every agent all day. It does three cheaper things instead.
Write down the claim
Each landing carries the tests the agent says it ran, in its own words. A claim that's written down can be checked, and a landing that names none is marked.
Count what's unchecked
Landings with no tests named go on the untested list. The window shows how many, and the nightly check owes them a run.
Check main while nobody waits
ishoo nightlyruns the full check on main. If it fails, it bisects the commits since the last green run and names the landing that broke it.
The trace#
Every landing writes one file to the store under .ishoo/landings/. This is a real one:
{
"issue": "DOCS-06",
"agent": "agent-517794",
"person": "junovhs",
"at": "2026-11-08T06:43:41Z",
"plan_name": "Project memory",
"base": "230fcb52add8…",
"commit": "f2157074ebeb…",
"files": ["docs/decisions/DEC-14.md", "docs/rules/product.md"],
"note": "Recorded DEC-14 at the owner's request: the manual is locked to the code…",
"tests": ["cargo test --workspace: 70 core + 10 app passed"],
"events": [{ "kind": "decided", "text": "The manual stays locked to the code" }],
"fixes_main": false
}| Field | Why it's kept |
|---|---|
base and commit | Exactly which code the change started from and what it became. Enough to revert it, or to bisect over it. |
files | What it touched. Search uses this to rank past issues for the files you're working on. |
note | What changed and why, in the agent's words. It's also the commit message. |
tests | What the agent says it checked. Empty means the nightly check owes it a run. |
events | Up to five headlines (shipped, fixed, decided, broke, blocked) for Home's Highlights. |
person and plan_name | Who the agent worked for, and which plan the work moved. |
Home shows the trace as a timeline, and each issue's details show its landing. Because it's plain JSON on the store, any script can read it too.