A register that goes stale is worse than none — it tells you something was checked when the product it described no longer exists. These are the mechanisms that keep it honest as you ship.
Shipping re-arms assumptions
An entry can declare the paths it depends on. When Sightspool sees commits touching those paths on your default branch, matching entries revert from holds or refuted back to untested and are re-measured. It compares against the last commit it saw, so direct pushes to main re-arm exactly like pull requests do.
Connecting a repository never re-arms your history: the cursor starts at the current commit, so you are not flooded with re-arms for everything you shipped before Sightspool existed.
The register also works forward
The same commit scan runs the other way. When you ship something no assumption covers, Sightspool drafts candidate entries for that surface — a belief, a question, a signal and a threshold — for you to accept, amend or dismiss. Drafts only; it never commits anything on your behalf.
Your dispositions are recorded
Every drafted assumption and published finding can be accepted, amended, challenged or dismissed. These are append-only: an amendment records what changed rather than overwriting, and nothing is silently retracted. The proportion you accept without amendment is shown on the register — if the agent's drafts need constant correction, you should be able to see that plainly rather than infer it.
The weekly digest
Once a week the workspace owner gets an email covering verdicts ruled, entries re-armed, the honest current state of the register, decisions waiting on you and any open escalations. It quotes the watch's real notes, so "still gathering" arrives as "still gathering" and never as progress.
Write-back to your coding agent
Settled verdicts export as a block you paste into your CLAUDE.md or AGENTS.md, so the agent writing your code knows what has been disproven. Verified and refuted read firmly; a provisional holds is marked provisional with its observed value and sample size. Anything still gathering, untested or in draft is never exported — the block only ever carries what has actually been settled.
<!-- sightspool:verdicts:start -->
## Sightspool — settled verdicts
Do NOT assume: users who start an assessment complete it unaided.
Refuted — observed 0.41 (threshold: at least 0.70), n = 214.
Rely on this: teams who connect a source in week one stay active.
Verified — observed 0.78 (threshold: at least 0.60), n = 96.
<!-- sightspool:verdicts:end -->