Tracer bullet of the migration design (Gate 4, slice 1): pinned v0.1.1 baseline under docs/sources/upstream/ with provenance note, the Karpathy block moved verbatim to docs/sources/regelwerk/ (standing rule mapped onto the sources read-only mechanism), AGENTS.md assembled from the byte-true upstream sections plus the project section 6 (group rules condensed from the old CLAUDE.md), CLAUDE.md reduced to the upstream pointer, WORKFLOW.md and all four templates copied, schema.yaml extended (issue milestone/priority/status columns, component type, wiki area vision - all flagged in the header), validate.py and gen_status.py forked with marked extensions, pruefe_upstream_drift.py added, STATUS.md generated, CI gains the offline validate job, README directory link defused. Verified: validate 0 errors 0 warnings (the three pre-existing directory-link errors are gone), gen_status --check current, drift check 0 findings, baseline byte-identical to the reference checkout (10/10 files), four negative tests fire (WIP limit 3x in-progress, waiting without wartegrund, component slug mismatch, single-byte drift in WORKFLOW.md). gen_status needs Python >= 3.10 locally (write_text newline) - noted for the design AAR. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
30 lines
881 B
Markdown
30 lines
881 B
Markdown
---
|
|
type: issue
|
|
id: "0000"
|
|
status: open # open | in-progress | done | rejected
|
|
created: YYYY-MM-DD
|
|
related: [] # design docs, ADRs, other issues
|
|
---
|
|
|
|
<!-- Copy to docs/issues/NNNN-slug.md. Delete comments when filling in. -->
|
|
|
|
# Issue-0000: Title
|
|
|
|
## Problem / Motivation
|
|
|
|
<!-- What's wrong or missing, and why it matters. One paragraph. -->
|
|
|
|
## Acceptance
|
|
|
|
<!-- When is this issue done? Verifiable, like every other criterion
|
|
in this framework. -->
|
|
|
|
## Notes
|
|
|
|
<!-- Optional: context, links, findings gathered along the way.
|
|
Rules: status is the single source of truth and lives here in the
|
|
frontmatter — STATUS.md is generated, never edited. An issue that
|
|
starts real work links its design doc in `related`. Closed means
|
|
status: done (or rejected, with a one-line reason in Notes) —
|
|
the file stays; git is the history. -->
|