43 lines
4.2 KiB
Markdown
43 lines
4.2 KiB
Markdown
---
|
||
name: skill-harvest-register-proposed-skills-awaiting-steward-authorization
|
||
description: "Standing register of skill create/patch/retire proposals surfaced by /wrap-up §1.6, awaiting steward authorization. The governed analog of PENDING.md, turned on our own tooling — propose → authorize → build → record. Surfaced every wake via this MEMORY entry."
|
||
metadata:
|
||
node_type: memory
|
||
type: reference
|
||
originSessionId: a8eb1d46-314e-4545-a133-f747c69ad5b4
|
||
---
|
||
|
||
# Skill-harvest register
|
||
|
||
The single place proposed skills live so they don't evaporate between sessions. `/wrap-up` §1.6 *proposes* here; the steward *authorizes*; only then is a skill created/patched/retired (never autonomously — the loop is load-bearing, per PENDING-23). `/wake-up` surfaces the open proposals via this entry. The governed analog of `~/PENDING.md`, for our own tools.
|
||
|
||
**Status legend:** `PROPOSED` (awaiting steward) · `AUTHORIZED` (proceed to build) · `BUILT` (done; move to the built-log) · `DEFERRED` (reason + condition) · `REJECTED` (reason; don't revisit without new input).
|
||
|
||
## Open proposals
|
||
|
||
| Skill | Kind | One-line | Origin | Status |
|
||
|-------|------|----------|--------|--------|
|
||
| `/spec-code-audit` | create | Audit live code against a spec-contract section clause-by-clause; classify each gap (FIX-now / route-to-authority / ships-with-promotion); verified-vs-inferred marked; deliverable = gap-map, not pass/fail. Reusable beyond ARC (e.g. L1 code-vs-amendment). | 2026-05-29 (code-represents-spec audit) | PROPOSED |
|
||
| `bmf-diagnose` | create | The N6 read-only `EXPLAIN`-first root-cause method for L1/BMF storage pathologies (measure before cut). | 2026-05-27 | PROPOSED |
|
||
| `/arc-typeset` | create | Codified ARC typesetting discipline (the per-piece typographic pass). | 2026-05-28 (morning) | PROPOSED |
|
||
| `/pre-build-audit` | create | The four-pass *scope-claimed-vs-scope-tested per claim, with substrate evidence* discipline that prevents frame-inheritance before a build. | 2026-05-28 | PROPOSED |
|
||
| `/vignette` | create | Phase-α vignette genome generation under Symmetria (read essay + spec + corpus → genome JSON → validate-and-save). **Phase 2 of the vignette build** — author it *with* Phase 2, after the audits, not standalone. | 2026-05-28 | DEFERRED (until vignette Phase 2) |
|
||
| Symmetria §3 `trust-prior-pass-frame` | patch | Add the contamination flag: frame-inheritance from a prior verification into an untested domain. (Feedback memory already saved.) | 2026-05-28 | PROPOSED |
|
||
| `mcp-drop-diagnose` | create | When an MCP server drops silently mid-session: read its per-server `mcp-logs` for desync signatures (`-32000` / "unknown message ID" / multi-second slow calls) + grep the **upstream repo's issues** for the symptom BEFORE hand-rolling mitigations. Proved out on the #1495 MemPalace cold-load fix (the upstream-issue check WAS the answer). Could fold into `bmf-diagnose`. | 2026-06-02 | PROPOSED |
|
||
|
||
## Built / authorized (lineage — for context, not action)
|
||
|
||
- `/landscape-scan` + `/tooling-scan` (the scan-skill family, per-workstream lens cards) — built + in use (2026-05-27).
|
||
- `/wrap-up` §1.6 skill-harvest step + `/wake-up` §2.a/§3 glance — the practice itself (PENDING-23, 2026-05-27).
|
||
- Chaîne-d'union clasp across wake / Symmetria / wrap (2026-05-26).
|
||
- `/wrap-up` §4.0 — MemPalace liveness-ping-before-diary; steward-authorized + applied (2026-06-02; #1495 cold-start drop resilience, so a silent drop never eats the wrap filing).
|
||
|
||
## Candidate patches not yet proposed (watch-list)
|
||
|
||
- **AUTHORIZED (steward 2026-05-29) — apply at the next `/wrap-up`:** wire `/wrap-up` §1.6 to *append here* and `/wake-up` §2.a to *read here*, so the register is the canonical surface rather than digging session memories. (Each patched skill carries a one-line provenance note.)
|
||
- A Symmetria §3 flag for `verify-counts-two-ways` / mechanical-sweeps-finicky (saved as `feedback-verify-counts-two-ways.md`; may graduate to a flag if it recurs).
|
||
|
||
---
|
||
|
||
*Discipline reminder: "no harvest" is a valid outcome; do not manufacture proposals to fill the table (the inverse of Hermes's autonomous self-write). The yardstick is the steward's: did the steward have to re-explain something a skill could have carried?*
|