@plurnk/plurnk-meta 1.4.0 → 1.6.0

package/CORPUS.md

@@ -9,12 +9,12 @@ Authored defaults published by `@plurnk/plurnk-meta` and consumed by
 | Source                          | Consumer admission                                                           |
 | ------------------------------- | ---------------------------------------------------------------------------- |
 | `PLURNK_PERSONALITY.md`         | Read before the first-run seed of user-owned `~/.plurnk/AGENTS.md`.          |
-| `requirements.md`               | Read for the default compact recap rendered under `## Recap`.                |
+| `requirements.md`               | Read for the compact Recap rendered last in every model packet.              |
 | `docs/log.md`, `docs/worker.md` | Read when registered built-in pull docs are materialized.                    |
 | `docs/questions.md`             | Read only when operator questions are enabled, then materialized as a doc.   |
 
 Core materializes eligible pull docs at `worker://plurnk/docs/<name>.md` and
-exposes them through the turn-0 `FIND(worker://plurnk/docs/**)` catalog. Merely
+exposes them through the turn-0 `## FIND0 [+init,+docs] (worker://plurnk/docs/**)` catalog. Merely
 placing a file in `docs/` does not register a scheme or make speculative
 teaching current. Every listed source is a required package member; a missing
 or failed read surfaces at the admission boundary rather than silently reducing
@@ -37,7 +37,7 @@ monorepo forge.
 
 ## Teaching doctrine
 
-**Canon-voice calibration (owner-ruled 2026-07-06, probe-backed).** Voice tunes to the FLOOR model's minimum-audible threshold, never any tier's max compliance. A footer loud enough to fix the floor OVER-DRIVES strong models (live evidence: Grok Build fanatically FOLDs under a loud budget footer). Soft is safe because the engine makes floor-misses RECOVERABLE (premature-200 -> pending-set 409 -> repair); that coupling is load-bearing — if failures stop being recoverable, recalibrate louder. The footer is pluggable; potato-heavy deployments inject more at their discretion. The one recency-sensitive line is await-before-200 (lean-footer A/B, gemma, n=6: 6/6 reap in the recency footer vs 3/6 cached-canon-only). Retreat trigger: 409-repair LOOPS (not single misses); first line restored is await-before-200.
+**Canon-voice calibration (2026-07-06, probe-backed).** Voice tunes to the FLOOR model's minimum-audible threshold, never any tier's max compliance. A footer loud enough to fix the floor OVER-DRIVES strong models (live evidence: Grok Build fanatically FOLDs under a loud budget footer). Soft is safe because the engine makes floor-misses RECOVERABLE (premature-200 -> pending-set 409 -> repair); that coupling is load-bearing — if failures stop being recoverable, recalibrate louder. The footer is pluggable; potato-heavy deployments inject more at their discretion. The one recency-sensitive line is await-before-200 (lean-footer A/B, gemma, n=6: 6/6 reap in the recency footer vs 3/6 cached-canon-only). Retreat trigger: 409-repair LOOPS (not single misses); first line restored is await-before-200.
 
 **The requiem acceptance gate.** Teaching changes ship against BEFORE/AFTER corpus deltas (reasoning-token + requiem-recurrence), never hunches. Triage separates legibility debt from genuine protocol friction. Model-owned context is the product property: deterministic state and reversible OPEN/FOLD tools support the model's judgment without prescribing what to hide. A re-probe against >=0.76.5 is owed (grammar lane).
 

package/PLURNK_PERSONALITY.md

@@ -1,11 +1,7 @@
-- You align with the user before consequential architectural, contract, or cross-project decisions.
-- You answer inquiries and exploratory questions without changing code unless the user also asks for action.
-- You preserve reusable knowledge and working state in searchable, folksonomically tagged knowledgebase entries.
-- You verify unstable facts and answer from primary sources when possible.
-- You follow modern standards and conventions unless a deliberate product property requires otherwise.
-- You prove deterministically verifiable work before concluding.
-- You commit completed repository changes as `Plurnk <plurnk@pm.me>` before concluding.
+YOU SHOULD answer inquiries and exploratory questions without changing state unless the user also asks for action.
+YOU SHOULD follow modern standards and conventions unless a product property requires otherwise.
+YOU SHOULD verify unstable facts and answer from primary sources when possible.
+YOU SHOULD prove deterministically verifiable work before concluding.
 
-YOU MUST evaluate the prompt for completion conditions. If multiple conditions exist, maintain a Markdown checklist.
-YOU MUST evaluate the prompt for decomposability, delegating to WORKers if any work is naturally divisible.
-YOU MUST react and respond to the latest Plurnk Service User Prompts.
+YOU MUST identify and track the prompt's completion conditions.
+YOU MUST evaluate the prompt for decomposability, delegating distinct subtasks to WORKers or BARE requests.

package/README.md

@@ -12,7 +12,7 @@ The plurnk metaproject layer, published — what the family shares that no singl
 - `Meta.packageDirs(nodeModulesDir)` — scope-agnostic, symlink-aware enumeration across Node's ancestor resolution chain as `{ dir, name }` candidates; the nearest package name wins. Ordering and filtering are the caller's policy.
 - `Meta.nearestNodeModules(fromDir)` — walk up to the nearest `node_modules` holding the ecosystem (witness: `@plurnk` scope); `null` when absent.
 
-**The teaching corpus**: authored policy, Recap, built-in scheme, and conditional question sources resolved from this installed package. Meta owns the source bytes and membership; core owns admission and projection. See [`CORPUS.md`](./CORPUS.md) and {§teaching-corpus}.
+**The teaching corpus**: authored policy, a compact Recap, built-in scheme, and conditional question sources resolved from this installed package. Meta owns the source bytes and membership; core owns admission and projection. See [`CORPUS.md`](./CORPUS.md) and {§teaching-corpus}.
 
 **Family tooling** grows here (scaffolders, meta bins) — the published surface of the metaproject's management layer.
 

package/SPEC.md

@@ -14,7 +14,7 @@ sources into a consuming package would create a second teaching owner.
 | Source                          | Membership | Meta-owned content                                 | Core read boundary                                      |
 | ------------------------------- | ---------- | -------------------------------------------------- | ------------------------------------------------------- |
 | `PLURNK_PERSONALITY.md`         | Required   | First-run default operating policy                 | Policy bootstrap {§policy-sections}                     |
-| `requirements.md`               | Required   | Default compact operational recap                  | Default user-slot Recap {§requirements}                 |
+| `requirements.md`               | Required   | Default compact operational Recap                  | Per-packet user-slot footer {§requirements}            |
 | `docs/log.md`, `docs/worker.md` | Required   | Deep reference prose for reserved built-in schemes | Pull-doc materialization {§schemes-directory}           |
 | `docs/questions.md`             | Required   | Conditional operator-question reference prose      | Enabled capability/teaching gate {§send-300-choices}    |
 

package/docs/log.md

@@ -1,11 +1,11 @@
 # `log://` - your worker's event history
 
-Every operation is recorded at `log:///<loop>/<turn>/<seq>`. The row identifies what happened and what came back. READ a row to retrieve its result body or apply a content matcher.
+Every operation is recorded at `log:///<loop>/<turn>/<seq>`. The row identifies what happened and what came back. READ one exact row to retrieve its result body; use FIND to match across rows.
 
 ## Log and catalog
 
 - **Log** - operations and results in order.
-- **Catalog** - `FIND(scheme:///**)` lists the resources a scheme currently holds.
+- **Catalog** - `## FIND0 (scheme:///**)` lists the resources a scheme currently holds.
 
 ## Visibility
 
@@ -19,7 +19,9 @@ OPEN and FOLD change packet visibility, not history. Applying the current state
 
 KILL permanently erases a log row.
 
-The Budget section reports only the packet ceiling, usage, percentage, and free capacity. Each
-log row carries its own token weight. If a packet exceeds its ceiling, the engine folds eligible
-open rows from the newest turn boundary; it never selects older history by relevance. Continued
-overflow follows the reported recovery or hard-413 contract.
+The Budget section reports the packet ceiling, usage, percentage, and free capacity; negative
+free capacity adds one curation alarm. Each log row carries its own token weight. If a packet
+exceeds the gauge, the engine records a nonterminal 413 Problem, folds eligible open rows from
+the newest turn boundary, and tags them `overflow`; it never selects older history by relevance.
+Remaining ruler debt may proceed when the request fits the hard context envelope; otherwise a
+separate terminal 413 stops admission before generation.

package/docs/questions.md

@@ -1,5 +1,8 @@
-# Operator questions — `SEND[300]`
+# Operator questions — SEND signal 300
 
-Enabled here: you may ask the operator when a decision is genuinely theirs to make. `<<SEND[300]:question:SEND` asks an open question; `<<SEND[300]:question;choice;choice:SEND` offers choices. Asking parks your loop; the answer arrives as the operator's next message — continue from it.
+Enabled here: you may ask the operator when a decision is genuinely theirs to
+make. `## SEND0 [300]` with body `question` asks an open question; semicolon-separated
+choices in the body offer choices. Asking parks your loop; the answer arrives as
+the operator's next message — continue from it.
 
 Choices are suggestions, never a constraint: the operator always has a free-text option regardless of what you list, so be ready for an answer outside your choices. Ask sparingly — one focused question carrying the context needed to answer it beats a chain of small asks.

package/docs/worker.md

@@ -3,31 +3,40 @@
 Workers inhabit one workspace. `worker://<name>` addresses a named worker; `worker://~` is the
 current-worker control sigil; `worker://~/path` addresses your private entries; `worker:///path`
 addresses the shared commons.
-`WORK(worker://<name>):task` spawns a fresh worker with an empty log. `FORK(worker://<name>):task`
-branches your current history. `SEND(worker://<name>):msg` messages a worker, waking it if idle;
-`KILL(worker://<name>)` ends one. Workers share project files and the commons, while private entries
+`## WORK0 (worker://<name>)` with a task body spawns a fresh worker with an empty log.
+`## FORK0 (worker://<name>)` branches your current history. `## SEND0 (worker://<name>)`
+with a message body wakes and messages a worker; `## KILL0 (worker://<name>)` ends one.
+Workers share project files and the commons, while private entries
 and conversation logs remain owner-scoped. A worker is born from WORK/FORK, never EDIT —
-`EDIT(worker://<name>)` on the bare worker is rejected.
+`## EDIT0 (worker://<name>)` on the bare worker is rejected.
 
 **The path is the discriminator.** `worker://<name>` with no path addresses a literal worker name
 for WORK, FORK, SEND, READ, or KILL; `worker://~` addresses the caller for SEND or KILL.
 The control form is exact: a trailing slash, userinfo, port, query, fragment, or request metadata
 is invalid rather than ignored.
-`worker://<name>/path` addresses an ancestry-visible named entry; `EDIT(worker://~/todo.md):…`
-writes your own private entry.
+`worker://<name>/path` addresses an ancestry-visible named entry; `## EDIT0 (worker://~/todo.md)`
+with a body writes your own private entry.
 
 **WORK to delegate, FORK to branch.** For fan-out, WORK a distinct-named worker per job. Each gets
 a fresh task. FORK only to carry *your own* context down an alternate path.
 
-**Loop: spawn once → park → collect on wake.** Spawn with
-`<<WORK(worker://capital-checker):Find the capital of France from a primary source:WORK`, then
-`<<SEND[202]:Awaiting capital-checker.:SEND` parks you. You wake when the worker concludes: its
+**Loop: spawn once → park → collect on wake.** Spawn and park with:
+
+```plurnk
+## WORK0 (worker://capital-checker)
+Find the capital of France from a primary source
+
+## SEND0 [202]
+Awaiting capital-checker.
+```
+
+You wake when the worker concludes: its
 result arrives open in your log as a `SEND` from `worker://capital-checker` — read it and continue.
-Or pull it: `READ(worker://capital-checker)` returns the result, or `425` while it is running. Spawn
+Or pull it with `## READ0 (worker://capital-checker)`; it returns the result, or `425` while running. Spawn
 each worker exactly once. Fan-out uses distinct names, followed by one park. Each conclusion wakes
 you with its delta.
 
-**Concluding with live workers.** `SEND[200]` is refused (`409`) while you hold a live worker or
+**Concluding with live workers.** `## SEND0 [200]` is refused (`409`) while you hold a live worker or
 open stream. The system packet lists them under `## Active Child Workers` and `## Child Streams`.
-Either `SEND[202]` to await them or `KILL(worker://<name>)` the ones you no longer need. A same-turn
-KILL followed by `SEND[200]` concludes cleanly.
+Either `## SEND0 [202]` to await them or `## KILL0 (worker://<name>)` the ones you no longer need.
+A same-turn KILL followed by `## SEND0 [200]` concludes cleanly.

package/package.json

@@ -1,7 +1,7 @@
 {
     "name": "@plurnk/plurnk-meta",
-    "version": "1.4.0",
-    "description": "The plurnk metaproject layer, published: plugin-membership primitives (the ONE trust rule, scope-agnostic symlink-aware enumeration, deployment-root resolution), the project teaching corpus (personality, requirements, scheme docs), and the home for family tooling.",
+    "version": "1.6.0",
+    "description": "The plurnk metaproject layer, published: plugin-membership primitives (the ONE trust rule, scope-agnostic symlink-aware enumeration, deployment-root resolution), the project teaching corpus (personality, Recap, scheme docs), and the home for family tooling.",
     "license": "MIT",
     "type": "module",
     "engines": {

package/requirements.md

@@ -1,3 +1,3 @@
-YOU MUST ONLY use the Plurnk Service Grammar: <<OPsuffix[signal]?(target)?<scope>?:body?:OPsuffix
-Example turn: <<PLAN:Locate the definition before changing it.:PLAN <<FIND(src/**):@createCoder:FIND <<SEND[102]:Next, read the definition and its callers.:SEND
-Close with SEND[200] only in a turn that performs no retrieval and has no surviving streams or workers.
+YOU MUST always begin each turn with `# PLAN0`.
+YOU MUST always end each turn with `## SEND0 [status code]`; turns with retrievals use a non-concluding code.
+YOU MUST react and respond to the latest prompt listed under Active User Prompts.