Files
LithosAnanke/.gitea/ISSUE_TEMPLATE/2-work.yaml
T
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

41 lines
1.3 KiB
YAML

name: Work item
about: A piece of planned work -- a step of a design, or something a ruling asked for.
title: ""
labels: ["kind/feature"]
body:
- type: textarea
id: goal
attributes:
label: What
description: The work, in a sentence or two.
validations:
required: true
- type: textarea
id: why
attributes:
label: Why -- the ruling or the design it comes from
description: Captain Bob's ruling (quoted, with its date) or the document and section, e.g. `docs/v4.0.0/ENGINE.md` section 5, step 3.
validations:
required: true
- type: textarea
id: done
attributes:
label: Done when
description: What will be true, and how it is shown. Every change to the kernel or v4 is accepted by the acceptance protocol -- the three ISA boots, the PC stick loaded high, test-32 -- with its logs committed.
value: |
- [ ]
- [ ] Acceptance passes, logs in `logs/`
validations:
required: true
- type: dropdown
id: area
attributes:
label: Area
multiple: true
options: ["kernel", "v4", "v3", "capsules", "proofs", "docs", "CI and build"]
- type: dropdown
id: priority
attributes:
label: Priority
options: ["must -- needed for the milestone", "should -- needed for the product", "nice to have"]