jschoubben
c0b35652d0
papa-hq reads 01 research -> 03 decision -> 02 design. The order is a scar, not a choice: 02-DESIGN existed from its initial commit, and when adr/ was finally promoted on 2026-07-13 it took the next free number rather than its place in the sequence. By then design was too settled to renumber. hal-hq was three commits old, so it is not. adr/ becomes 02-DECISIONS and 02-DESIGN becomes 03-DESIGN, and following the folder numbers now walks the process in the order it happens: research produces a decision, the decision authorises a design. 00-GENESIS becomes 00-META, matching papa's rename from the same restructure. Every path reference rewritten across documents, frontmatter, playbooks and skills. All links resolve; all 58 frontmatter blocks parse and their path fields still point at files that exist.
48 lines
1.8 KiB
Markdown
48 lines
1.8 KiB
Markdown
---
|
|
name: hal-new-issue
|
|
description: Use when something is wrong with the HAL mesh at the level of design or governance — a rule enforced by nothing, a stated behaviour that does not happen, a failure the design lets pass silently. Triggers on "this is broken", "open an issue", "that rule isn't enforced", "this reports success and does nothing".
|
|
---
|
|
|
|
# hal-new-issue
|
|
|
|
Opens a numbered issue. **Authoritative playbook:**
|
|
[`00-META/process/03-issues.md`](../../../00-META/process/03-issues.md).
|
|
|
|
## First, decide it belongs here
|
|
|
|
| Belongs in `04-ISSUES` | Belongs in the knowledge base |
|
|
|---|---|
|
|
| The design permits a failure to be silent | How to fix one occurrence of it |
|
|
| A documented rule is enforced by nothing | A command that works around it |
|
|
| A stated invariant is false in practice | A node-specific quirk |
|
|
| Finding the owner needs the whole mesh in view | Symptom → fix, once the answer is known |
|
|
|
|
**Search the knowledge base first** for the literal symptom text. If the answer is already
|
|
there, this is not an issue — it is a lookup. If the answer is a general lesson, it belongs in
|
|
both.
|
|
|
|
## Steps
|
|
|
|
1. Next free number. Create `04-ISSUES/NNN-short-name/00-report.md` with:
|
|
|
|
```yaml
|
|
---
|
|
status: open
|
|
opened: YYYY-MM-DD
|
|
located-in: []
|
|
fixed-by:
|
|
amended-design:
|
|
---
|
|
```
|
|
|
|
2. Write the symptom **as observed**, in plain terms, with the evidence that it happened —
|
|
what was run, what came back, when.
|
|
3. Say why it matters beyond the instance. An issue that is only one occurrence is a knowledge
|
|
base entry.
|
|
4. End with open questions rather than a proposed fix. Diagnosis is a separate step.
|
|
|
|
## Do not
|
|
|
|
- Do not name nodes, domains, addresses or paths. This repository is public.
|
|
- Do not guess the owner — `located-in:` is filled by diagnosis, not by opening.
|