conductor
ea3c20e205
The heading should not announce itself as 'plain English'; it should simply be the summary in everyday words. Meta-commentary removed from the heading line, instructions preserved in the comment block.
4.3 KiB
4.3 KiB
name, about, title, labels, assignees
| name | about | title | labels | assignees |
|---|---|---|---|---|
| Feature Request | New feature or improvement — plain English first, verifiable close conditions, version intent | [FEATURE] | feature | conductor |
<restate the issue title here in everyday words — this heading IS the plain-English summary; no meta-labels like "plain English" in it>
What is this about:
Why do we need it: <the itch — what happens today that shouldn't, or what becomes possible>
Why is it still open: <"not started yet" | "part done, X remains" | "deliberately parked as a future idea">
Example
What would let us close this
- <condition 1 — observable>
- <condition 2>
Version impact (declared at submission — verified at merge)
- major — breaking: changes a contract, schema, or interface others depend on
- minor — new capability: something becomes possible that wasn't
- patch — repair: same behaviour, done correctly
- none — touches no released artifact (docs, memory, process notes)
Technical details
WHAT: WHY: FILES: ACCEPTANCE: DEPENDENCIES:
Pipeline requirements
- TDD: frozen tests written first, red → green (N passed)
ruff checkandruff format --checkclean- Spec-compliance review gate: PASS
- Code-quality review gate: Approved
- Full orchestration suite regression green (suite total)
- Canary passes (name)
- Closed with a properly formatted closing comment + commit/PR references
Cognitive invariants (memory/cognition issues — both handoffs)
- Owner — which existing subsystem owns this (audit before creating modules)
- Trigger — what event activates it
- Read/write authority — which canonical state it reads/changes
- Provenance — derived state traceable to evidence
- Verification — how we know the change helped
- Failure visibility — how failure surfaces
- Reversibility — bad learned state can be superseded/replayed/rolled back
- Dormant cost — what it costs when irrelevant
- Benchmark + ablation — what measurable behaviour improves; what happens when disabled
- No duplicate authority — why extend vs create
Hard invariants: derived cognition preserves evidentiary ancestry · epistemic confidence ≠ attentional utility ≠ current applicability · retrieval never increases utility · self-model-induced behaviour is not independent evidence · historical truth survives present-state change · raw evidence is never destroyed by promotion.
Related umbrella
- Memory
- Governance
- Identity
- Growth
- Perception
- Infrastructure
- Life (Nick's)
- Custodian
- Orchestration
Priority (REQUIRED — the priority gate)
- P0 — critical — breaks the spine / core correctness, or blocks other work
- P1 — high — material user value or a real defect (money, correctness bugs, next-stage dependency)
- P2 — medium — quality/consolidation improvement (check the fold-into mapping first)
- P3 — low — measurement / benchmark / deferred policy