Files
rajamesandClaude Opus 5.5 c1bc1c8041
Acceptance / Acceptance (pull_request) Canceled after 0s
Build / Image RASPI (push) Successful in 4m35s
Build / Image PC (push) Successful in 4m30s
Build / Image MILKV (push) Successful in 4m33s
Build / v4 tests (32- and 64-bit cells) (push) Successful in 11m7s
gitea: issue forms and a PR template, in the project's own form
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_01GE3SDvQn5EoxdGufk84zz2
2026-11-06 17:15:25 +00:00

42 lines
1.3 KiB
YAML

name: Ruling needed
about: A decision only Captain Bob can make -- an open question, a trade-off, a design choice.
title: "[ruling] "
labels: ["status/blocked"]
body:
- type: markdown
attributes:
value: |
Lay out the question so it can be ruled on. The ruling is recorded as it always is --
**Ruled (Captain Bob, date)** -- in the document it belongs to, and the issue closed with a
link to that record.
- type: textarea
id: question
attributes:
label: The question
validations:
required: true
- type: textarea
id: options
attributes:
label: The options, and what each costs
description: Each choice with its consequences -- code size, speed, what it rules out later.
validations:
required: true
- type: textarea
id: recommendation
attributes:
label: Recommendation
description: Which option, and why. A recommendation, not a decision.
- type: input
id: record
attributes:
label: Where the ruling will be recorded
placeholder: "docs/v4.0.0/DECOMPOSITION.md section 3, D-4"
validations:
required: true
- type: textarea
id: waits
attributes:
label: What waits on it
description: Issues or work that cannot go on until this is ruled.