@techgoblin/gobstack 0.5.0-beta.8 → 0.6.0-alpha.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@techgoblin/gobstack",
-  "version": "0.5.0-beta.8",
+  "version": "0.6.0-alpha.2",
   "description": "Agent-discipline toolkit: one verify command, an enforcement matrix, and LIMITS. bash engine, npm shim.",
   "bin": {
     "goblin": "bin/goblin.js",
@@ -23,6 +23,8 @@
     "automations/",
     "bans/",
     "docs/",
+    "extras-catalogue/catalogue.tsv",
+    "extras-catalogue/payload/",
     "roles.yaml",
     "VERSION",
     "CHANGELOG.md"

package/presets/electron-overlay.yaml

@@ -2,13 +2,13 @@
 #
 # The `desktop` class is gone; F was merged into software because their classes.tsv need
 # columns are IDENTICAL on all 10 parts (measured). Everything F added beyond software lives in
-# plain goblin.yaml config keys, so it is an OVERLAY, not a class: `gob install --class software
+# plain frontmatter config keys, so it is an OVERLAY, not a class: `gob install --class software
 # --electron` (or the `--class desktop` / `F` alias, which sets --electron) renders the keys
 # below OVER the software preset. An absent key falls through to presets/software.yaml; a key
 # present here — including an empty one like sec_write_routes: "" — wins.
 #
 # The prose F carried (label / done_means / notes) is preserved here for the record; it is not a
-# rendered template key, so it never reaches a target's goblin.yaml.
+# rendered template key, so it never reaches a target's gob block.
 label: Desktop shell
 done_means: the renderer is isolated from Node, the main process is not busy, and the packaged bundle ships no dev dependency
 # software's A-only second gate (the TODO ceiling) is NOT applied: F never had it.

package/presets/fleet.yaml

@@ -9,16 +9,17 @@ scaffold_checks: no
 gate_name: commit
 gate_cmd: git rev-parse --verify --quiet HEAD
 ratchet_name: todo_markers
-# The harness's own vendored directories are excluded: without it, a fresh class-E install
-# counts the ratchet command line itself (`.goblin/goblin.yaml` holds the literal TODO|FIXME)
-# and goblin-stack's own skill prose (`.hermes/skills/*/SKILL.md`), so its gate was born RED
-# against a ceiling measured before those files were written (D8). The fleet's real config —
-# `*.yaml`/`*.yml`/`*.sh` at the root and under `profiles/` — is still counted.
-ratchet_cmd: grep -rniE '\b(TODO|FIXME)\b' --include='*.sh' --include='*.yaml' --include='*.yml' --include='*.md' --exclude-dir=.goblin --exclude-dir=.hermes . 2>/dev/null | wc -l
+# The harness's own vendored directories are excluded, and so is root AGENTS.md: in v2 the
+# config IS the AGENTS.md gob block, so the ratchet command line itself (the literal
+# TODO|FIXME inside `ratchet_cmd:`) lives in a *.md file at the root — without the exclude a
+# fresh install counts its own gate and is born RED against a ceiling measured before the
+# file was written (D8). The fleet's real config — `*.yaml`/`*.yml`/`*.sh` at the root and
+# under `profiles/` — is still counted.
+ratchet_cmd: grep -rniE '\b(TODO|FIXME)\b' --include='*.sh' --include='*.yaml' --include='*.yml' --include='*.md' --exclude-dir=.gob --exclude-dir=.hermes --exclude=AGENTS.md . 2>/dev/null | wc -l
 ratchet_ceiling: measure
 replay_env: GOBLIN_PRE_COMMIT
 replay_cmd: node checks/{name}.mjs
-runtime_data: .goblin/state.json
+runtime_data: .gob/state.json
 # A fleet config has no client surface; the secret family still matters (a profile file is one
 # `git add` away from a live token), so SC-01/SC-02 are the rows that bite here.
 sec_gitignore_family: yes

package/presets/game.yaml

@@ -14,7 +14,7 @@ ratchet_cmd: grep -rniE '\b(TODO|FIXME)\b' --include='*.cs' --include='*.ts' --i
 ratchet_ceiling: measure
 replay_env: GOBLIN_PRE_COMMIT
 replay_cmd: node checks/{name}.mjs
-runtime_data: .goblin/state.json
+runtime_data: .gob/state.json
 sec_gitignore_family: yes
 sec_build_output: Builds Library
 sec_audit_cmd: ""

package/presets/research.yaml

@@ -15,7 +15,7 @@ ratchet_cmd: ""
 ratchet_ceiling: 0
 replay_env: GOBLIN_PRE_COMMIT
 replay_cmd: node checks/{name}.mjs
-runtime_data: .goblin/state.json
+runtime_data: .gob/state.json
 # A knowledge repo has no client surface and no dependency manifest, so SC-03's build-output
 # clause, SC-05..SC-08 skip with a reason. The SECRET FAMILY is not one of those: a note file is
 # one `git add` away from a pasted token, so SC-02 is required here too and the installer writes

package/presets/service.yaml

@@ -14,7 +14,7 @@ ratchet_cmd: grep -rniE '\b(TODO|FIXME)\b' --include='*.ts' --include='*.tsx' --
 ratchet_ceiling: measure
 replay_env: GOBLIN_PRE_COMMIT
 replay_cmd: node checks/{name}.mjs
-runtime_data: .goblin/state.json
+runtime_data: .gob/state.json
 # A service has real inputs and real dependencies, so the security rows bite here.
 sec_gitignore_family: yes
 sec_build_output: dist

package/presets/software.yaml

@@ -24,7 +24,7 @@ ratchet_cmd: find .next/static dist/assets dist -type f -name '*.js' -exec cat {
 ratchet_ceiling: measure
 replay_env: GOBLIN_PRE_COMMIT
 replay_cmd: node checks/{name}.mjs
-runtime_data: .goblin/state.json
+runtime_data: .gob/state.json
 # SC-02 requires the whole secret family to be ignored; SC-03 clause 2 scans `sec_build_output`
 # for secret-shaped literals; SC-07 runs `sec_audit_cmd` once, deliberately, via goblin-audit.
 sec_gitignore_family: yes

package/skills/goblin-bootstrap/SKILL.md

@@ -16,10 +16,10 @@ Use when adopting goblin-stack in a repo, or starting one.
    no agent skills. Opt in per platform afterwards with `gob emit --platform <p>` (or vendor the
    Hermes project tier with `--skills yes`).
 3. **`goblin-verify`** — a default software-class install (no agent skills) verifies green:
-   `38 passed, 0 failed, 11 advisory, 33 skipped`, exit 0, once `HANDOFF.md` names a commit that
+   `37 passed, 0 failed, 11 advisory, 34 skipped`, exit 0, once `HANDOFF.md` names a commit that
    exists; before that edit the
    scaffold's `0000000` placeholder is `HP-05`'s one expected day-one red (`37 passed, 1 failed`).
-   Thirty-three rows skip with a reason, and the reason matters: the five skill rows
+   Thirty-four rows skip with a reason, and the reason matters: the five skill rows
    (`SK-01`..`SK-04`, `AU-04`) skip on the `playbooks` opt-out a skills-free install records,
    then `HS-02`
    (no pinned pre-change commit yet, so the REPLAY is not provable), `AU-02`/`AU-03` (no report

package/templates/AGENTS.md.tmpl

@@ -3,31 +3,21 @@
 This repository uses **gobstack** (class `{{CLASS}}`, installed {{DATE}}). It is a pointer,
 not a rule dump — the rules live in one executable place, and facts beat requirements.
 
-- **Harness entry point:** `.goblin/bin/goblin-verify` — exit 0 pass, 1 a check failed,
+- **Harness entry point:** `.gob/bin/goblin-verify` — exit 0 pass, 1 a check failed,
   2 could not run, 3 the manifest is broken. Run it before you commit; the gate is the
   same run.
-- **Rules and their checks:** `.goblin/manifest/enforcement.tsv` (one row per rule; every row
+- **Rules and their checks:** `.gob/manifest/enforcement.tsv` (one row per rule; every row
   carries a runnable check or the literal `advisory`).
-- **Forbidden code (the ban list):** `.goblin/bin/goblin-bans` runs the bans named by `bans:` in
-  `.goblin/goblin.yaml`; each ban's mechanism lives in `.goblin/manifest/bans.tsv`. Run it before
+- **Forbidden code (the ban list):** `.gob/bin/goblin-bans` runs the bans named by `bans:` in
+  this file's gob block; each ban's mechanism lives in `.gob/manifest/bans.tsv`. Run it before
   you write the line, not after — a ban is a gate, and `goblin-verify` only reports it once the
   code exists.
 - **Session state:** `HANDOFF.md` at the repo root. Read it before touching anything.
-- **Project config:** `.goblin/goblin.yaml` (class, branch, gates, ratchet, runtime data,
-  replay, opt-outs). Edit it in place; the installer never overwrites it.
-- **The referenced standard**, if configured, is named by `practice:` in `.goblin/goblin.yaml`.
+- **Project config:** the `<!-- gob:begin --> … <!-- gob:end -->` block in this file
+  (class, branch, gates, ratchet, runtime data, replay, opt-outs). Edit it in place; the
+  installer never rewrites the block after the first install and never touches the prose.
+- **The referenced standard**, if configured, is named by `practice:` in the gob block.
   Read it before starting work; this repo carries no copy of it.
 
-**Agent skills are opt-in, per platform.** A default install ships none — this is a neutral
-harness on purpose, so nothing here assumes which coding agent you use. To install the
-procedure skills for your tool:
-
-    gob sync --platform <p>
-
-(`--scope project` writes them inside this repo; `--scope global` writes them for your user.)
-Run `gob sync` with no platform to see the list (`gob emit` is the same command under its
-original name). If skills were installed here, they live
-under the platform's own directory, and `gob verify` hashes them.
-
 Two things this repo does not do: it does not choose models (a role resolves through the
 mapping file named by `models_file:`), and it does not write outside its own tree.

package/templates/HANDOFF.md.tmpl

@@ -7,10 +7,10 @@
 ## ▶ START HERE (new session)
 
 - Working dir: the repo root.
-- Gate set: `{{GATE_NAME}}` — `{{GATE_CMD}}`, plus whatever you add in `.goblin/goblin.yaml`.
-- Run the gates and the manifest checks: `.goblin/bin/goblin-verify`
-- One line of measured numbers for the round: `.goblin/bin/goblin-verify --only GT-02` writes `.goblin/last-gate-line`.
-- Read before working: the referenced standard, if `.goblin/goblin.yaml` declares `practice:`.
+- Gate set: `{{GATE_NAME}}` — `{{GATE_CMD}}`, plus whatever you add in `AGENTS.md`.
+- Run the gates and the manifest checks: `.gob/bin/goblin-verify`
+- One line of measured numbers for the round: `.gob/bin/goblin-verify --only GT-02` writes `.gob/last-gate-line`.
+- Read before working: the referenced standard, if `AGENTS.md` declares `practice:`.
 
 ## State
 
@@ -25,7 +25,7 @@
 Every number here is a measurement with a date, never a copy from a previous round.
 
 - `{{GATE_NAME}}` = 0 · measured {{DATE}}
-- ratchet — declared in `.goblin/goblin.yaml`; re-measure it, do not copy it.
+{{GATE2_LINE}}
 - Example of the required form: `typecheck=0 · build=0 · ratchet <n> (ceiling <c>) · <n>/<n> harnesses green · measured {{DATE}}`
 
 ## Next steps

package/templates/agents-block.tmpl

@@ -0,0 +1,45 @@
+<!-- gob:begin (gobstack config — edit in place; the parser reads only this block) -->
+class: {{CLASS}}
+electron: {{ELECTRON}}
+branch: {{BRANCH}}
+models_file: {{MODELS_FILE}}
+practice: {{PRACTICE}}
+practice_sha256: {{PRACTICE_SHA}}
+owner_email: {{OWNER_EMAIL}}
+archive: {{ARCHIVE}}
+max_dirty: {{MAX_DIRTY}}
+advisory_ceiling: {{ADVISORY_CEILING}}
+security.gitignore_family: {{SEC_GITIGNORE_FAMILY}}
+security.build_output: {{SEC_BUILD_OUTPUT}}
+security.audit_cmd: {{SEC_AUDIT_CMD}}
+security.audit_max_age_days: {{SEC_AUDIT_MAX_AGE}}
+security.waiver_max_age_days: {{SEC_WAIVER_MAX_AGE}}
+security.write_routes: {{SEC_WRITE_ROUTES}}
+perf.metric: {{PERF_METRIC}}
+perf.cmd: {{PERF_CMD}}
+perf.baseline_commit: {{PERF_BASELINE_COMMIT}}
+perf.baseline_value: {{PERF_BASELINE_VALUE}}
+perf.measured: {{PERF_MEASURED}}
+perf.host_gate: {{PERF_HOST_GATE}}
+harness_dir: {{HARNESS_DIR}}
+scaffold_checks: {{SCAFFOLD_CHECKS}}
+feature_map: {{FEATURE_MAP}}
+source_root: {{SOURCE_ROOT}}
+verify_doctor: {{VERIFY_DOCTOR}}
+reference_manifest: {{REFERENCE_MANIFEST}}
+quarantine_root: {{QUARANTINE_ROOT}}
+loop_max_turns_ceiling: {{LOOP_MAX_TURNS}}
+gate_{{GATE1_NAME}}_cmd: {{GATE1_CMD}}
+gate_{{GATE2_NAME}}_cmd: {{GATE2_CMD}}
+ratchet.name: {{RATCHET_NAME}}
+ratchet.cmd: {{RATCHET_CMD}}
+ratchet.ceiling: {{RATCHET_CEILING}}
+runtime_data: [{{RUNTIME_DATA}}]
+bans: [{{BANS}}]
+bans_exempt:
+layers:
+replay.env: {{REPLAY_ENV}}
+replay.cmd: {{REPLAY_CMD}}
+replay.commit: ""
+disabled: [{{DISABLED}}]
+<!-- gob:end -->

package/templates/audit-waiver.tsv.tmpl

@@ -1,10 +1,10 @@
-# .goblin/audit-waiver.tsv — one line per accepted dependency advisory (SC-07).
+# .gob/audit-waiver.tsv — one line per accepted dependency advisory (SC-07).
 #
 # package	severity	id	date	reason
 #
 # The date is the day the decision was taken, and SC-07 refuses a waiver older than
 # security.waiver_max_age_days: a waiver with no expiry is a permanent blind spot. A
-# high|critical line in .goblin/audit.tsv with no matching row here is a RED.
+# high|critical line in .gob/audit.tsv with no matching row here is a RED.
 #
 # example:
 # next	high	GHSA-xxxx-yyyy-zzzz	2026-09-24	no fixed release yet; the vulnerable path is the dev server only

package/templates/boundary-waivers.tmpl

@@ -1,4 +1,4 @@
-# .goblin/boundary-waivers — write routes that deliberately do NOT validate input (SC-05).
+# .gob/boundary-waivers — write routes that deliberately do NOT validate input (SC-05).
 #
 # One repo-relative path per line, with the reason after a '#'. A waiver is a DECISION recorded
 # where the row can read it; it is not a silence. SC-05 prints the waiver count on its gate line

package/templates/checks/gate.sh.tmpl

@@ -5,8 +5,8 @@
 set -uo pipefail
 ROOT=$(git rev-parse --show-toplevel 2>/dev/null || pwd)
 # shellcheck source=/dev/null
-. "$ROOT/.goblin/bin/goblin-lib.sh"
-CONFIG="$ROOT/.goblin/goblin.yaml"
+. "$ROOT/.gob/bin/goblin-lib.sh"
+CONFIG="$ROOT/AGENTS.md"
 
 line=""
 bad=0
@@ -16,13 +16,13 @@ while IFS=$'\t' read -r name cmd; do
   rc=$?
   line="$line $name=$rc"
   [ "$rc" -eq 0 ] || bad=1
-done < <(g_yaml_gates "$CONFIG")
+done < <(g_agents_gates "$CONFIG")
 
-rname=$(g_yaml_block_scalar "$CONFIG" ratchet name)
-rcmd=$(g_yaml_block_scalar "$CONFIG" ratchet cmd)
+rname=$(g_agents_read "$CONFIG" ratchet.name)
+rcmd=$(g_agents_read "$CONFIG" ratchet.cmd)
 if [ -n "$rname" ] && [ -n "$rcmd" ]; then
   rval=$( cd "$ROOT" && bash -c "$rcmd" 2>/dev/null | tr -d '[:space:]' )
-  line="$line · $rname $rval (ceiling $(g_yaml_block_scalar "$CONFIG" ratchet ceiling))"
+  line="$line · $rname $rval (ceiling $(g_agents_read "$CONFIG" ratchet.ceiling))"
 fi
 
 printf '%s · measured %s\n' "${line# }" "$(date +%F)"

package/templates/install-hooks.allowlist.tmpl

@@ -1,4 +1,4 @@
-# .goblin/install-hooks.allowlist — dependencies whose install-time script is accepted (SC-08).
+# .gob/install-hooks.allowlist — dependencies whose install-time script is accepted (SC-08).
 #
 # One package name per line. SC-08 enumerates package-lock.json for "hasInstallScript": true and
 # requires every one of them to appear here. An install hook is arbitrary code that runs on every

package/templates/ci/goblin-gate.yml.tmpl

@@ -1,46 +0,0 @@
-# .github/workflows/goblin-gate.yml — written once by goblin-stack for class {{CLASS}}.
-#
-# WHAT THIS IS. One job that runs the gate set this project DECLARES in `.goblin/goblin.yaml`.
-# `.goblin/bin/goblin-verify` executes every declared gate (GT-02) and every rule that carries a
-# command, so CI and a local verify cannot report two different truths about one SHA (PG-06).
-# The job carries NO `if:` at any level, on purpose: GitHub reports a SKIPPED job as Success even
-# when it is a required check, so a conditional here would be a green light with no bulb (PG-05).
-#
-# A WORKFLOW FILE IS NOT A GATE. Four things make it one, and all four are yours to do:
-#   1. REQUIRED CHECK — mark the `gate` job required for this branch (Settings -> Branches, or a
-#      ruleset). Until then the job runs and nothing waits for it.
-#   2. NO BYPASS — tick "Do not allow bypassing the above settings". Without it the restriction
-#      does not apply to admins, and an admin push skips the check entirely.
-#   3. A PUSH IDENTITY — a required check binds nobody while the only committer is the repo's
-#      sole admin. Push from a non-admin account or token, or accept that the gate is advisory
-#      for your own pushes. This is a forge change, not a file change: that is why PG-04 is the
-#      row that records it, and why PG-04 is advisory rather than a gate.
-#   4. NEVER CONDITIONAL — keep every job and step unconditional (PG-05 enforces it).
-#
-# WHAT IT CANNOT SEE. It runs on a runner you do not own, from a checkout of your repo. Any gate
-# that needs a display, a licence, a GPU or a signed-in session is a HOST gate: declare it in the
-# HANDOFF's measured numbers, do not try to run it here. On a private repo the minutes are billed
-# to your account, so a long job is not free.
-#
-# For a zizmor-clean workflow, pin `uses:` to a commit SHA instead of a tag:
-#   gh api repos/actions/checkout/git/refs/tags/v4 --jq .object.sha
-# (left as a tag here so the file is readable; nothing in goblin-stack reads a workflow's SHA).
-name: goblin-gate
-on:
-  push:
-    branches: [{{BRANCH}}]
-  pull_request:
-permissions:
-  contents: read
-concurrency:
-  group: goblin-gate-{{BRANCH}}
-  cancel-in-progress: true
-jobs:
-  gate:
-    name: the declared gate set
-    runs-on: ubuntu-latest
-    timeout-minutes: 20
-    steps:
-      - uses: actions/checkout@v4
-      - name: run the declared gate set
-        run: bash .goblin/bin/goblin-verify

package/templates/goblin.yaml.tmpl

@@ -1,146 +0,0 @@
-# .goblin/goblin.yaml — the project config. Generated once by goblin-install, then YOURS.
-# It is never overwritten after the first install: edit it in place.
-#
-# Format: a flat, line-oriented YAML subset, parsed by .goblin/bin/goblin-lib.sh. No YAML
-# library, no network, no npm. Keep one key per line and keep comments on their own line.
-
-# Which class this project is: software | service | game | research | fleet.
-# The letters A-E and the older names app/agent/desktop are READ-TIME aliases, so an old
-# value keeps verifying; `desktop`/`F` resolve to software. Selects the required parts
-# (manifest/classes.tsv).
-class: {{CLASS}}
-
-# Electron opt-in (software class). true turns on the electron ban set (BN-06..09) even if the
-# bans: list below omits them, and requires a declared perf.host_gate (PF-01 fails without one).
-# The `desktop`/`F` install alias sets this true; a text-editor app leaves it false.
-electron: {{ELECTRON}}
-
-# The default branch, DECLARED, never assumed. A preset that assumes the wrong branch
-# silently skips a repo.
-branch: {{BRANCH}}
-
-# The model mapping — the ONE install-time machine input. goblin-stack READS this file and
-# never writes it. Absent on another machine: every model-dependent check reports advisory.
-models_file: {{MODELS_FILE}}
-
-# The global engine (optional, W1). Where the ENGINE tier lives on this machine — an
-# absolute path or ~/-prefixed. Absent by default: a fresh per-repo install is
-# byte-compatible with today, and verify resolves its engine exactly as it always did.
-# Declared but unusable (relative path, missing directory, no manifest inside) is
-# verify exit 2 with NO fallback — a repo must not be judged by an engine it did not
-# declare. Authored by hand (or by `goblin upgrade`, W3); goblin-install never writes it.
-# engine_dir: ~/.goblin/engine
-
-# The referenced standard (optional). goblin-stack carries no copy of it; it pins its hash.
-practice: {{PRACTICE}}
-practice_sha256: {{PRACTICE_SHA}}
-
-# The commit identity this repo expects (CM-01).
-owner_email: {{OWNER_EMAIL}}
-
-# archive: true -> verify requires no HANDOFF and no gates, and says so.
-archive: {{ARCHIVE}}
-
-# Uncommitted entries allowed at verify time (CM-03). 0 means commit as you go.
-max_dirty: {{MAX_DIRTY}}
-
-# Unenforceable rules are counted; this is the cap that stops the matrix decaying into prose.
-advisory_ceiling: {{ADVISORY_CEILING}}
-
-# Whether this class requires a client-visible surface to be secret-free (SC-01..SC-09 read the
-# `security:` block below). Declared, never inferred: a stack-specific rule guessed from the
-# files on disk is how a matrix starts lying.
-security:
-  gitignore_family: {{SEC_GITIGNORE_FAMILY}}
-  build_output: {{SEC_BUILD_OUTPUT}}
-  audit_cmd: {{SEC_AUDIT_CMD}}
-  audit_max_age_days: {{SEC_AUDIT_MAX_AGE}}
-  waiver_max_age_days: {{SEC_WAIVER_MAX_AGE}}
-  write_routes: {{SEC_WRITE_ROUTES}}
-
-# The performance budget (PF-01). The NUMBER lives in `ratchet:` above — this block only names
-# the commit it was measured on, so "I raised the ceiling" cannot silently become "I never
-# measured again". An empty baseline_commit means "not measured yet" and PF-01 skips with that
-# reason; a baseline_commit that does not resolve to an ancestor of HEAD is a RED.
-perf:
-  metric: {{PERF_METRIC}}
-  cmd: {{PERF_CMD}}
-  baseline_commit: {{PERF_BASELINE_COMMIT}}
-  baseline_value: {{PERF_BASELINE_VALUE}}
-  measured: {{PERF_MEASURED}}
-  host_gate: {{PERF_HOST_GATE}}
-
-# Where the asserting harnesses live.
-harness_dir: {{HARNESS_DIR}}
-
-# Whether this class scaffolds that directory. A declared harness_dir that is absent FAILS
-# (HS-01) when this is yes; a class that ships no harness dir skips with a reason.
-scaffold_checks: {{SCAFFOLD_CHECKS}}
-
-# The feature map (P6's inventory, authored by skills/goblin-feature-map).
-# feature_map: the map's README, relative to this repo. EMPTY means "no map declared yet" and
-# makes FM-01/FM-02 SKIP with that reason - a fresh install has no map and must not be born RED.
-# source_root: entry paths in the map resolve against this.
-# verify_doctor: the command the map's own instructions say to run. EMPTY -> VA-01 SKIPs.
-feature_map: {{FEATURE_MAP}}
-source_root: {{SOURCE_ROOT}}
-verify_doctor: {{VERIFY_DOCTOR}}
-
-# The reference corpus (P15). `reference_manifest:` names the manifest RC-01/RC-02/RC-04 read: a
-# hash-only record of the quarantined corpus, never the corpus itself. EMPTY means "no reference
-# corpus is declared" and makes RC-01, RC-02 and RC-04 SKIP with that reason - a repo with no
-# corpus must not be born RED. A key that IS set but names a missing or unparseable file is a
-# FAIL, never a skip, so losing the manifest cannot read as "no corpus". RC-01 also reads the
-# `security: build_output:` list above: a file there whose sha256 appears in an entry fails the
-# build.
-# `quarantine_root:` is the quarantine directory the procedure extracts into (outside this repo).
-# No row reads it; it is declared so the procedure has a machine-readable anchor instead of a path
-# in prose.
-reference_manifest: {{REFERENCE_MANIFEST}}
-quarantine_root: {{QUARANTINE_ROOT}}
-
-# The loop ceiling (G2, LP-03). The most turns ONE loop record may declare in its budget, so a
-# runaway loop cannot buy itself unlimited iterations. 20 is the engine's own default for a
-# kanban goal loop, measured; a ceiling that does not match the engine's default is a number
-# someone made up. It bounds one loop's turns, never how many loops exist.
-loop_max_turns_ceiling: {{LOOP_MAX_TURNS}}
-
-# The gate set. DECLARED, never inferred from the stack. Replace the default below with the
-# real commands for this project; each must exit 0. The whole block is rendered by one
-# placeholder (a class may declare a second gate - A's TODO ceiling), so a second, empty
-# placeholder line below it leaked an unsubstituted token into every class's installed config
-# and nothing rendered it (Z1-3).
-gates:
-{{GATES}}
-
-# A count that must not rise, with its ceiling. The ceiling was measured at install time.
-ratchet:
-  name: {{RATCHET_NAME}}
-  cmd: {{RATCHET_CMD}}
-  ceiling: {{RATCHET_CEILING}}
-
-# Paths a probe must never write (DS-01/DS-02 hash them around every gate run).
-runtime_data:
-{{RUNTIME_DATA}}
-
-# The ban list (G5). Which bans this project turns on; an unlisted ban SKIPs with a reason.
-# A ban's mechanism lives in .goblin/manifest/bans.tsv; the engine is .goblin/bin/goblin-bans.
-bans: [{{BANS}}]
-
-# Narrow, explicit, reviewed exceptions (Dune rule 5): "- <ban id> <path prefix>".
-bans_exempt:
-{{BANS_EXEMPT}}
-
-# What BN-05 reads: "<from> <to>" layer pairs. Empty -> BN-05 SKIPs with a reason.
-layers:
-{{LAYERS}}
-
-# How a harness proves RED on the pre-change tree (HS-02). Set commit: to the pinned
-# pre-change SHA once the round it guards has landed; until then HS-02 is skipped with a reason.
-replay:
-  env: {{REPLAY_ENV}}
-  cmd: {{REPLAY_CMD}}
-  commit: ""
-
-# Parts recorded as opt-out. Their required checks report SKIP (opt-out) rather than passing.
-disabled: [{{DISABLED}}]

package/templates/loop/decisions.tsv.tmpl

@@ -1 +0,0 @@
-ts	phase	decision	why	evidence	result

package/templates/loop/predicate.tmpl

@@ -1,16 +0,0 @@
-# .goblin/loop/predicate — the loop's exit condition. Copy this file to that path and edit it.
-#
-# ONE command. Exits 0 == the loop is finished. Comments are allowed here; the command is the
-# single non-blank, non-comment line (LP-01 checks exactly that).
-#
-# A duration is NOT a finish condition, and neither is a description of one.
-# Run it once BEFORE iteration 1 and record the result in .goblin/loop/first-run as
-# "exit=<n> ts=<ISO8601>": the run-once rule is how you know the command is runnable and
-# currently red, which is what makes a later green mean anything.
-# Then pin it: sha256sum .goblin/loop/predicate | cut -d' ' -f1 > .goblin/loop/predicate.sha256
-# Never edit the predicate mid-loop — archive it under .goblin/loop/closed-<date>/ together with
-# the pin it was closed under, then open a new loop whose predicate.sha256 names the archived
-# digest on a `previous: <digest>` line (LP-02: a silent relaxation FAILs; the chain is the record).
-#
-# Replace the line below with the real condition. Example shape only:
-node tools/check-cycles.mjs