The record of 2026-11-06, and issue and PR templates #110
Assignees
rajames (Robert A. James (Captain Bob))
Clear assignees
rajames (Robert A. James (Captain Bob))
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: rajames/LithosAnanke#110
Reference in New Issue
Block a user
What and why
The record of 2026-11-06, and the issue and PR templates. Held back from #30 so its acceptance
run was not restarted.
docs/fabric/FABRIC-3.md§XLV andCHANGELOG.md: the day -- the gate, the nightlies andNexus, the runner's Debian default, one repository, Gitea.
.gitea/ISSUE_TEMPLATE/(Bug, Work item, Ruling needed, Board bring-up; the XWiki linked) and.gitea/pull_request_template.md, in the record's own form: Found, Ruled, Built, Verified.Gitea reads them from master, so they apply when this merges.
Closes #108
Acceptance
The Acceptance check runs on this PR by itself. Nothing here touches the build: two
documents and five template files.
The record
docs/fabric/FABRIC-3.md-- this PR is the recordCHANGELOG.md🤖 Generated with Claude Code
https://claude.ai/code/session_01GE3SDvQn5EoxdGufk84zz2
Issues follow the record's Found / Ruled / Built / Verified (docs/fabric/FABRIC-3.md): the reporter writes what was found and its evidence; Captain Bob rules; the commits build it; the acceptance logs verify it. A finding is not a request to fix it (.claude/CLAUDE.md). .gitea/ISSUE_TEMPLATE/ 1-bug.yaml Found, where, system (v4/v3), seen on (ISA, stick, hardware), evidence (the log lines), how found 2-work.yaml what, why (the ruling or design section), done when (with the acceptance protocol and its logs), area, priority 3-ruling.yaml the question, the options and their costs, a recommendation, where the ruling will be recorded, what waits on it 4-board.yaml board, the image booted (Nexus version or commit), what happened, the serial log, the BRINGUP.md item config.yaml blank issues still allowed; the XWiki linked for design and discussion .gitea/pull_request_template.md what and why, Closes #, acceptance (the check runs itself; hand-run logs; hardware), the record (FABRIC-3.md, CHANGELOG), no unrequested fixes Gitea reads these from the default branch: they apply once on master. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GE3SDvQn5EoxdGufk84zz2Issues follow the record's Found / Ruled / Built / Verified (docs/fabric/FABRIC-3.md): the reporter writes what was found and its evidence; Captain Bob rules; the commits build it; the acceptance logs verify it. A finding is not a request to fix it (.claude/CLAUDE.md). .gitea/ISSUE_TEMPLATE/ 1-bug.yaml Found, where, system (v4/v3), seen on (ISA, stick, hardware), evidence (the log lines), how found 2-work.yaml what, why (the ruling or design section), done when (with the acceptance protocol and its logs), area, priority 3-ruling.yaml the question, the options and their costs, a recommendation, where the ruling will be recorded, what waits on it 4-board.yaml board, the image booted (Nexus version or commit), what happened, the serial log, the BRINGUP.md item config.yaml blank issues still allowed; the XWiki linked for design and discussion .gitea/pull_request_template.md what and why, Closes #, acceptance (the check runs itself; hand-run logs; hardware), the record (FABRIC-3.md, CHANGELOG), no unrequested fixes Gitea reads these from the default branch: they apply once on master. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GE3SDvQn5EoxdGufk84zz2