Duck Server — Unsolved Log

Things the autonomous dev cycle (or a manual session) picked up, attempted, and could not close out on its own — a bug whose root cause wasn't found, a feature that hit a design roadblock, anything that isn't safe to just keep retrying unattended. One file per problem. Use TEMPLATE.md to add new ones.

This is distinct from docs/issues/, which is the bug log for things that were found and fixed (or are still open but actively being chased) within a normal run. An entry lands here specifically when it needs a human to look at it before more time is spent — this is the queue a person checks, fixes on a branch, and merges once it's verified clean.

Workflow

Automation (or a human) hits something it can't safely resolve in-cycle. It reverts any speculative RTL/code changes so main stays green, then logs an entry here via TEMPLATE.md — why the item was picked up, what went wrong, and the status of any fix attempt. Cross-link a docs/issues/ entry if one already documents the technical detail.
The item is pulled from docs/next_run.md's queue (see automation.md) so it isn't silently retried every cycle — it stays parked here until a human re-queues it.
A human reviews the entry and works the fix on a separate branch (e.g. fix/unsolved-001-<slug>) — never directly on main.
The fix branch must pass the full regression (make results.xml) with no new failures anywhere else in the suite before it's proposed for merge.
On approval (PR review / explicit human sign-off), merge to main, move the entry from Open to Resolved below with the branch/commit that fixed it, and re-add any related follow-up work to docs/next_run.md.

Open

ID	Title	Component	Since
UNSOLVED-001	MOESI TC-MOESI-1/TC-MOESI-2 fail — root cause not found	RTL	2026-07-19

Resolved

ID	Title	Component	Fixed In
none yet