@plurnk/plurnk-meta 1.4.0 → 1.5.0

package/CORPUS.md

@@ -9,7 +9,7 @@ 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.   |
 
@@ -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,9 @@
-- 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 distill reusable knowledge into searchable, folksonomically tagged knowledgebase entries.
+- You follow modern standards and conventions unless a product property requires otherwise.
 - 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 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 evaluate the prompt for completion conditions and track multiple conditions in a Markdown checklist.
+YOU MUST evaluate the prompt for decomposability, delegating to WORKers iff the work is naturally divisible.
+YOU MUST react and respond to the latest prompt listed under Active User Prompts.

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,6 +1,6 @@
 # `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
 

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.5.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,2 @@
-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 a PLAN.
+YOU MUST always end retrieval turns (with READ, FIND, ...) with a non-concluding status code.