hns-lsel-applier — LSEL APPLY engine
Namespace: hns-lsel-* is user-owned dogfood (CLAUDE.local.md §24). This skill
is NOT mirrored into internal/template/templates/ — it lives only in this repo.
Graduation to moai-lsel-* + 16-language distribution is a separate SPEC
(out of scope per spec.md §G).
Token discipline. This body deliberately avoids the literal identifier of the
frozen Go applier's write-flag and the literal name of the orchestrator-only
user-question channel. Both are referenced by location and role (e.g. "the write-flag
at internal/harness/applier.go:22", "the orchestrator's synchronous user gate") so
the REQ-LSEL-003 invariant-grep and the E4 subagent-boundary grep over LSEL surfaces
read zero literal matches. The invariants themselves are stated in plain English.
What this skill does
The LSEL loop's PROPOSE→APPLY seam was dead in production: Applier.Apply never ran
(manifest.jsonl absent), CuratorDispatch had 0 production callers, and the frozen
Go applier's write-flag at internal/harness/applier.go:22 (kept false) is the
apply dead-switch (REQ-LSEL-003 — M3 keeps it false by BYPASS, never unfreeze). The
M3 closure routes APPLY through a parallel user-owned applier that writes only to
the six evolvable surfaces (spec.md §B.3), while the frozen Go applier stays
byte-for-byte frozen. Design SSOT:
.moai/reports/moai-local-self-evolution-design-20260804.html §4 ("동결된 Go applier를
우회하는 병렬 사용자 소유 applier를 세운다" — build a parallel user-owned applier that
bypasses the frozen Go one) + §7 (the two-round critique moved the allowlist OUT of
the evolvable skill files into a frozen meta file, and added execution-meta files to
the forced-gate set).
The APPLY engine is the playback hook .moai/hooks/lsel-apply.sh plus this skill's
model-mediated judgment (target validation nuance, approval-marker provenance, blast-
radius reasoning the mechanical hook cannot see). The hook is the load-bearing safety
floor; this skill is the consumer-facing surface that decides WHICH approved decision
to feed it next and how to interpret refusal.
The APPLY pipeline
lsel-apply.sh <decision.json> performs five steps. Steps 1-2 are the safety floor;
steps 3-5 are the playback.
- Frozen-allowlist hard-reject (REQ-LSEL-001 / AC-LSEL-001). The target path in
decision.json is matched against the frozen_patterns regex list in
.claude/lsel/frozen-allowlist.json. A match → REFUSE: a row is appended to
.moai/logs/lsel-reject.log naming the rejected path and category frozen-path,
NO file is written, and the hook exits 2.
- Execution-meta forced-gate (REQ-LSEL-002 / AC-LSEL-005 D3 self-amending-
handcuffs). If the target matches one of the four
execution_meta categories —
(i) the frozen allowlist meta file itself, (ii) an applier/curator skill body
(hns-lsel-applier/, hns-lsel-curator/), (iii) the apply hook
(.moai/hooks/lsel-*.sh), (iv) the settings.local.json hook-registration
subblock — the hook checks decision.json for a synchronous-approval marker (a
synchronous_approval object with decision: "approved", produced by the
orchestrator's synchronous user gate). No marker → REFUSE: reject-log row with
category execution-meta, exit 3, no write. With marker → proceeds (the refusal
is keyed on the absent marker, NOT on the category match alone). The refusal
semantics mirror the M2 csa_refusal_test.sh fixture exactly.
- Apply the diff.patch via
git apply (playback of an already-approved decision).
Only the paths declared in the patch are staged — never git add -A (working-tree
hygiene).
- Append the apply-ledger row to
.moai/state/lsel/apply-ledger.jsonl:
{proposal_id, target_surface, ts, result:"applied", commit_sha, category}. This
is the manifest the frozen Go applier never produced, finally real in user-owned
space.
- Commit the staged change as ONE
feat(lsel-<proposal-id>): ... Conventional
Commit on the current (feature) branch (REQ-LSEL-004). The ledger row's
commit_sha is backfilled from the commit's short SHA.
A no-arg invocation is a clean no-op (exit 0) so an empty approved-queue does not
derail a loop pass.
The model-mediated layer (you, when invoked)
When this skill is invoked to drive an APPLY pass, your job on top of the mechanical
hook is:
- Read the proposal's
proposal.md + self-critique.md at
.moai/state/lsel/proposals/<id>/. A proposal with status: blocked (any
UNRESOLVED self-critique objection) MUST NOT be fed to the hook — return a blocker
report instead.
- Confirm the approval marker's provenance. The
synchronous_approval object must
carry a real orchestrator-produced approval artifact (the synchronous user-question
channel the orchestrator owns per CLAUDE.md §8). A marker the loop fabricated for
itself is the self-amending-handcuffs failure mode (REQ-LSEL-002); the hook's
mechanical check is the floor, your provenance judgment is the ceiling. This skill
is a subagent mechanism and NEVER invokes the orchestrator-only user-question
channel; return a blocker report and let the orchestrator run the gate.
- Re-verify the frozen-allowlist invariant by grepping the write-flag at
internal/harness/applier.go:22 — it MUST stay false. If M3's bypass ever drifts
toward unfreezing the Go applier, return a blocker (AP-LSEL-002).
What this skill does NOT do
- No unfreezing of the Go applier — the write-flag at
internal/harness/applier.go:22 stays false (REQ-LSEL-003). The bypass is
parallel and user-owned; the frozen applier is reference-only.
- No edits to frozen doctrine —
internal/template/templates/**,
.claude/rules/moai/**, CLAUDE.md, retained agents, moai-* skills, the frozen
Go applier / curator_dispatch.go, and .moai/config/sections/** are
byte-for-byte untouched. The allowlist hard-rejects them (step 1).
- No new-apply / self-approve / allowlist-amend primitive in
lsel-apply.sh
(REQ-LSEL-008). The hook only consumes already-approved decisions; it does not
author proposals or bless them. The M4 verify.sh runs only AFTER an apply has
committed — it does not create a new apply; it never self-approves.
- No user-question invocation — subagent boundary (CLAUDE.md §8). Return a
blocker report; the orchestrator runs the synchronous gate.
VERIFY stage (M4 — REQ-LSEL-013 / AC-LSEL-015)
After an apply commits a proposal, VERIFY proves the apply was safe. VERIFY has
two layers — both MANDATORY:
(a) Mechanical layer — verify.sh (bash-testable)
verify.sh --proposal-dir <p> --repo-root <r> [--timeout SECS] [--feedback-file <f>]
runs the proposal's frontmatter verify_command with a timeout-retry-once
policy and auto-reverts on a second failure:
- 2-attempt policy. Attempt 1 runs. On SUCCESS →
verified:true, stop. On
TIMEOUT-class failure → attempt 2 (flaky tolerance — report §10 P3: "retry
once on timeout so a correct proposal isn't flipped by noise"). On
NON-TIMEOUT-FAIL → attempt 2 (allows the "second non-timeout failure" of
AC-LSEL-015 clause 3 to materialize before revert fires).
- Attempt 2: SUCCESS →
verified:true. Any failure (timeout OR non-timeout) →
verified:false + auto git revert lsel-<proposal-id> + the proposal's
feedback_*.md is marked verified: false.
- The outcome is appended to the apply ledger as a
{"stage":"verify","verified":true|false,...} row — the load-bearing signal.
(b) MANDATORY /moai gate superset (model-mediated)
/moai gate (lint+format+type+test) is MANDATORY after every apply — it is
NOT optional. A bash hook cannot invoke a Claude Code slash command directly,
so the gate runs MODEL-SIDE: when this skill drives an APPLY pass, the
orchestrator/model runs /moai gate after the mechanical apply + verify. The
proposer-authored verify_command alone is circular (report §11 mustFix
B#6 / AP-LSEL-004): a proposer can author a verify_command that its own change
satisfies. /moai gate is the independent check — lint, format, type-check,
and the test suite exercise surfaces the proposal never touched. Treat a
mechanical verify_command PASS without a green /moai gate as an unverified
apply.
Model-mediated layer (you, when invoked)
- After
lsel-apply.sh commits and verify.sh reports, run /moai gate
(the MANDATORY superset). If the gate fails, the apply is unverified even if
verify.sh reported verified:true — treat it as a VERIFY failure and revert.
- A revert (whether auto-fired by
verify.sh or gate-driven) MUST be surfaced
to the orchestrator as a blocker report — the orchestrator, not this skill,
confirms a revert with the user. Never run /moai gate's user-facing surface
from inside this subagent mechanism; return a blocker report.
Verification (run before declaring an APPLY+VERIFY pass complete)
# M4 VERIFY characterization test (AC-LSEL-015) — hermetic temp repo:
.claude/skills/hns-lsel-applier/verify_test.sh
# the verify ledger row carries the outcome:
grep '"stage":"verify"' .moai/state/lsel/apply-ledger.jsonl
Verification (run before declaring an APPLY pass complete)
# 1. APPLY characterization test (AC-001/002/005/008/013) — hermetic temp repo:
.claude/skills/hns-lsel-applier/apply_test.sh
# 2. Rollback-rehearsal SHIP GATE (AC-014):
.claude/skills/hns-lsel-applier/rollback_rehearsal_test.sh
# 3. REQ-LSEL-003 frozen-flag re-verify (post-apply). The frozen Go applier's
# write-flag at internal/harness/applier.go:22 MUST read `false`, and no LSEL
# surface (skills/hooks/state/allowlist) references that identifier as mutable.
# (The literal identifier is intentionally not written here; find it at line 22
# of the frozen file and grep LSEL surfaces for it — expect zero hits.)
sed -n '22p' internal/harness/applier.go # MUST show the `= false` write-flag line
# 4. The apply ledger carries the new row:
tail -1 .moai/state/lsel/apply-ledger.jsonl
Cross-references
- SPEC:
.moai/specs/SPEC-LSEL-LOCAL-EVOLUTION-001/{spec,plan,acceptance,progress}.md
- Design report (SSOT):
.moai/reports/moai-local-self-evolution-design-20260804.html
§4 (user-owned parallel applier), §7 (allowlist relocation + execution-meta forced
gate), §10 P3, §11 mustFix A#1/A#5/A#8.
- Frozen applier (reference only):
internal/harness/applier.go:22 (the frozen
write-flag), internal/harness/curator_dispatch.go.
- Curator (PROPOSE stage, M2):
.claude/skills/hns-lsel-curator/SKILL.md
(CSA forced-gate doctrine + the Tier-4 DEAD finding).
- CSA refusal fixture:
.claude/skills/hns-lsel-curator/csa_refusal_test.sh
(the refusal rule this hook enforces mechanically).
- Namespace guard:
internal/template/split_namespace_test.go,
internal/template/internal_content_leak_test.go (must NOT flag a hns-lsel-applier
leak — this skill is dogfood, never templated).
1---
2name: hns-lsel-applier
3description: >
4 Local Self-Evolution Loop (LSEL) APPLY engine — the playback-only consumer of
5 approved decision.json records that drives `.moai/hooks/lsel-apply.sh` for the
6 GOOS-local PROPOSE→APPLY seam closure (SPEC-LSEL-LOCAL-EVOLUTION-001 M3). Reads
7 an approved decision.json, validates the target against the frozen allowlist
8 (.claude/lsel/frozen-allowlist.json), mechanically refuses execution-meta
9 targets lacking a synchronous-approval marker, applies the referenced
10 diff.patch, appends an apply-ledger.jsonl row, and commits one
11 lsel-<proposal-id>-tagged Conventional Commit on the feature branch. M3 scope:
12 APPLY bypass closure only (the frozen Go applier stays frozen — its write-flag
13 at internal/harness/applier.go:22 stays false; REQ-LSEL-003).
14allowed-tools: Read, Grep, Glob, Bash
15user-invocable: false
16metadata:
17 source: https://skillmd.com/skills/modu-ai/hns-lsel-applier
18 version: "0.1.0"
19 category: "harness"
20 status: "active"
21 updated: "2026-08-04"
22 tags: "lsel,self-evolution,apply,harness,dogfood"
23---
24
25# hns-lsel-applier — LSEL APPLY engine
26
27> **Namespace:** `hns-lsel-*` is user-owned dogfood (CLAUDE.local.md §24). This skill
28> is NOT mirrored into `internal/template/templates/` — it lives only in this repo.
29> Graduation to `moai-lsel-*` + 16-language distribution is a separate SPEC
30> (out of scope per spec.md §G).
31
32> **Token discipline.** This body deliberately avoids the literal identifier of the
33> frozen Go applier's write-flag and the literal name of the orchestrator-only
34> user-question channel. Both are referenced by location and role (e.g. "the write-flag
35> at `internal/harness/applier.go:22`", "the orchestrator's synchronous user gate") so
36> the REQ-LSEL-003 invariant-grep and the E4 subagent-boundary grep over LSEL surfaces
37> read zero literal matches. The invariants themselves are stated in plain English.
38
39## What this skill does
40
41The LSEL loop's PROPOSE→APPLY seam was dead in production: `Applier.Apply` never ran
42(`manifest.jsonl` absent), `CuratorDispatch` had 0 production callers, and the frozen
43Go applier's write-flag at `internal/harness/applier.go:22` (kept `false`) is the
44apply dead-switch (REQ-LSEL-003 — M3 keeps it `false` by BYPASS, never unfreeze). The
45M3 closure routes APPLY through a parallel **user-owned** applier that writes only to
46the six evolvable surfaces (spec.md §B.3), while the frozen Go applier stays
47byte-for-byte frozen. Design SSOT:
48`.moai/reports/moai-local-self-evolution-design-20260804.html` §4 ("동결된 Go applier를
49우회하는 병렬 사용자 소유 applier를 세운다" — build a parallel user-owned applier that
50bypasses the frozen Go one) + §7 (the two-round critique moved the allowlist OUT of
51the evolvable skill files into a frozen meta file, and added execution-meta files to
52the forced-gate set).
53
54The APPLY engine is the **playback hook** `.moai/hooks/lsel-apply.sh` plus this skill's
55model-mediated judgment (target validation nuance, approval-marker provenance, blast-
56radius reasoning the mechanical hook cannot see). The hook is the load-bearing safety
57floor; this skill is the consumer-facing surface that decides WHICH approved decision
58to feed it next and how to interpret refusal.
59
60## The APPLY pipeline
61
62`lsel-apply.sh <decision.json>` performs five steps. Steps 1-2 are the safety floor;
63steps 3-5 are the playback.
64
651. **Frozen-allowlist hard-reject** (REQ-LSEL-001 / AC-LSEL-001). The target path in
66 `decision.json` is matched against the `frozen_patterns` regex list in
67 `.claude/lsel/frozen-allowlist.json`. A match → REFUSE: a row is appended to
68 `.moai/logs/lsel-reject.log` naming the rejected path and category `frozen-path`,
69 NO file is written, and the hook exits 2.
702. **Execution-meta forced-gate** (REQ-LSEL-002 / AC-LSEL-005 D3 self-amending-
71 handcuffs). If the target matches one of the four `execution_meta` categories —
72 (i) the frozen allowlist meta file itself, (ii) an applier/curator skill body
73 (`hns-lsel-applier/`, `hns-lsel-curator/`), (iii) the apply hook
74 (`.moai/hooks/lsel-*.sh`), (iv) the `settings.local.json` hook-registration
75 subblock — the hook checks `decision.json` for a synchronous-approval marker (a
76 `synchronous_approval` object with `decision: "approved"`, produced by the
77 orchestrator's synchronous user gate). No marker → REFUSE: reject-log row with
78 category `execution-meta`, exit 3, no write. With marker → proceeds (the refusal
79 is keyed on the absent marker, NOT on the category match alone). The refusal
80 semantics mirror the M2 `csa_refusal_test.sh` fixture exactly.
813. **Apply the diff.patch** via `git apply` (playback of an already-approved decision).
82 Only the paths declared in the patch are staged — never `git add -A` (working-tree
83 hygiene).
844. **Append the apply-ledger row** to `.moai/state/lsel/apply-ledger.jsonl`:
85 `{proposal_id, target_surface, ts, result:"applied", commit_sha, category}`. This
86 is the manifest the frozen Go applier never produced, finally real in user-owned
87 space.
885. **Commit** the staged change as ONE `feat(lsel-<proposal-id>): ...` Conventional
89 Commit on the current (feature) branch (REQ-LSEL-004). The ledger row's
90 `commit_sha` is backfilled from the commit's short SHA.
91
92A no-arg invocation is a clean no-op (exit 0) so an empty approved-queue does not
93derail a loop pass.
94
95## The model-mediated layer (you, when invoked)
96
97When this skill is invoked to drive an APPLY pass, your job on top of the mechanical
98hook is:
99
100- **Read the proposal's `proposal.md` + `self-critique.md`** at
101 `.moai/state/lsel/proposals/<id>/`. A proposal with `status: blocked` (any
102 UNRESOLVED self-critique objection) MUST NOT be fed to the hook — return a blocker
103 report instead.
104- **Confirm the approval marker's provenance.** The `synchronous_approval` object must
105 carry a real orchestrator-produced approval artifact (the synchronous user-question
106 channel the orchestrator owns per CLAUDE.md §8). A marker the loop fabricated for
107 itself is the self-amending-handcuffs failure mode (REQ-LSEL-002); the hook's
108 mechanical check is the floor, your provenance judgment is the ceiling. This skill
109 is a subagent mechanism and NEVER invokes the orchestrator-only user-question
110 channel; return a blocker report and let the orchestrator run the gate.
111- **Re-verify the frozen-allowlist invariant** by grepping the write-flag at
112 `internal/harness/applier.go:22` — it MUST stay `false`. If M3's bypass ever drifts
113 toward unfreezing the Go applier, return a blocker (AP-LSEL-002).
114
115## What this skill does NOT do
116
117- **No unfreezing of the Go applier** — the write-flag at
118 `internal/harness/applier.go:22` stays `false` (REQ-LSEL-003). The bypass is
119 parallel and user-owned; the frozen applier is reference-only.
120- **No edits to frozen doctrine** — `internal/template/templates/**`,
121 `.claude/rules/moai/**`, `CLAUDE.md`, retained agents, `moai-*` skills, the frozen
122 Go applier / `curator_dispatch.go`, and `.moai/config/sections/**` are
123 byte-for-byte untouched. The allowlist hard-rejects them (step 1).
124- **No new-apply / self-approve / allowlist-amend primitive** in `lsel-apply.sh`
125 (REQ-LSEL-008). The hook only consumes already-approved decisions; it does not
126 author proposals or bless them. The M4 `verify.sh` runs only AFTER an apply has
127 committed — it does not create a new apply; it never self-approves.
128- **No user-question invocation** — subagent boundary (CLAUDE.md §8). Return a
129 blocker report; the orchestrator runs the synchronous gate.
130
131---
132
133## VERIFY stage (M4 — REQ-LSEL-013 / AC-LSEL-015)
134
135After an apply commits a proposal, VERIFY proves the apply was safe. VERIFY has
136**two layers** — both MANDATORY:
137
138### (a) Mechanical layer — `verify.sh` (bash-testable)
139
140`verify.sh --proposal-dir <p> --repo-root <r> [--timeout SECS] [--feedback-file <f>]`
141runs the proposal's frontmatter `verify_command` with a **timeout-retry-once**
142policy and auto-reverts on a second failure:
143
144- **2-attempt policy.** Attempt 1 runs. On SUCCESS → `verified:true`, stop. On
145 TIMEOUT-class failure → attempt 2 (flaky tolerance — report §10 P3: "retry
146 once on timeout so a correct proposal isn't flipped by noise"). On
147 NON-TIMEOUT-FAIL → attempt 2 (allows the "second non-timeout failure" of
148 AC-LSEL-015 clause 3 to materialize before revert fires).
149- Attempt 2: SUCCESS → `verified:true`. Any failure (timeout OR non-timeout) →
150 `verified:false` + **auto `git revert lsel-<proposal-id>`** + the proposal's
151 `feedback_*.md` is marked `verified: false`.
152- The outcome is appended to the apply ledger as a
153 `{"stage":"verify","verified":true|false,...}` row — the load-bearing signal.
154
155### (b) MANDATORY `/moai gate` superset (model-mediated)
156
157**`/moai gate` (lint+format+type+test) is MANDATORY after every apply — it is
158NOT optional.** A bash hook cannot invoke a Claude Code slash command directly,
159so the gate runs MODEL-SIDE: when this skill drives an APPLY pass, the
160orchestrator/model runs `/moai gate` after the mechanical apply + verify. The
161proposer-authored `verify_command` alone is **circular** (report §11 mustFix
162B#6 / AP-LSEL-004): a proposer can author a verify_command that its own change
163satisfies. `/moai gate` is the independent check — lint, format, type-check,
164and the test suite exercise surfaces the proposal never touched. Treat a
165mechanical verify_command PASS without a green `/moai gate` as an unverified
166apply.
167
168### Model-mediated layer (you, when invoked)
169
170- After `lsel-apply.sh` commits and `verify.sh` reports, **run `/moai gate`**
171 (the MANDATORY superset). If the gate fails, the apply is unverified even if
172 `verify.sh` reported `verified:true` — treat it as a VERIFY failure and revert.
173- A revert (whether auto-fired by `verify.sh` or gate-driven) MUST be surfaced
174 to the orchestrator as a blocker report — the orchestrator, not this skill,
175 confirms a revert with the user. Never run `/moai gate`'s user-facing surface
176 from inside this subagent mechanism; return a blocker report.
177
178### Verification (run before declaring an APPLY+VERIFY pass complete)
179
180```bash
181# M4 VERIFY characterization test (AC-LSEL-015) — hermetic temp repo:
182.claude/skills/hns-lsel-applier/verify_test.sh
183
184# the verify ledger row carries the outcome:
185grep '"stage":"verify"' .moai/state/lsel/apply-ledger.jsonl
186```
187
188## Verification (run before declaring an APPLY pass complete)
189
190```bash
191# 1. APPLY characterization test (AC-001/002/005/008/013) — hermetic temp repo:
192.claude/skills/hns-lsel-applier/apply_test.sh
193
194# 2. Rollback-rehearsal SHIP GATE (AC-014):
195.claude/skills/hns-lsel-applier/rollback_rehearsal_test.sh
196
197# 3. REQ-LSEL-003 frozen-flag re-verify (post-apply). The frozen Go applier's
198# write-flag at internal/harness/applier.go:22 MUST read `false`, and no LSEL
199# surface (skills/hooks/state/allowlist) references that identifier as mutable.
200# (The literal identifier is intentionally not written here; find it at line 22
201# of the frozen file and grep LSEL surfaces for it — expect zero hits.)
202sed -n '22p' internal/harness/applier.go # MUST show the `= false` write-flag line
203
204# 4. The apply ledger carries the new row:
205tail -1 .moai/state/lsel/apply-ledger.jsonl
206```
207
208## Cross-references
209
210- **SPEC:** `.moai/specs/SPEC-LSEL-LOCAL-EVOLUTION-001/{spec,plan,acceptance,progress}.md`
211- **Design report (SSOT):** `.moai/reports/moai-local-self-evolution-design-20260804.html`
212 §4 (user-owned parallel applier), §7 (allowlist relocation + execution-meta forced
213 gate), §10 P3, §11 mustFix A#1/A#5/A#8.
214- **Frozen applier (reference only):** `internal/harness/applier.go:22` (the frozen
215 write-flag), `internal/harness/curator_dispatch.go`.
216- **Curator (PROPOSE stage, M2):** `.claude/skills/hns-lsel-curator/SKILL.md`
217 (CSA forced-gate doctrine + the Tier-4 DEAD finding).
218- **CSA refusal fixture:** `.claude/skills/hns-lsel-curator/csa_refusal_test.sh`
219 (the refusal rule this hook enforces mechanically).
220- **Namespace guard:** `internal/template/split_namespace_test.go`,
221 `internal/template/internal_content_leak_test.go` (must NOT flag a `hns-lsel-applier`
222 leak — this skill is dogfood, never templated).