arkgate 4.8.14 → 4.8.15

package/templates/skills/ark-explore.md

@@ -22,6 +22,18 @@ one bounded decision needs 2–3 enforceable options.
 ## Checklist
 
 - Doctor #1: if ENFORCE + empty plan A and gates are already installed → **Shape** (`/ark-explore` then `/ark-autopilot`). Do not say install-agent-gates.
+- When `--require-gates` / adopted-strict is on and doctor JSON has `adrPresence`,
+  the next step is a short note under `docs/adr/` (or `docs/decisions/`). Soft.
+  Not every change. Off when require-gates is off. No `/ark-adr`.
+- When doctor JSON has `statesTransitions` or `statusTransitionCatalog`, the
+  next step is a short states → transitions table (or one link) on the domain
+  doc already in play. Use catalog names when present. Soft. Silent when that
+  doc is absent or Domain has no status vocabulary. No `/ark-states`. Do not
+  invent states.
+- When doctor JSON has `noDomainFrontend`, Domain is empty and the UI holds the
+  rules. Next: one Domain file (`/ark-place`) then one small refactor
+  (`/ark-autopilot`). Soft. Silent when there is no frontend or Domain already
+  has files. No `/ark-domain`. Do not invent a Domain house.
 - Distinguish **missing** skills vs **stale** catalog. Installed ≠ stale.
 - Hook green is not tree green (scripted edits bypass PreToolUse).
 - Bug / false green / false red / missing doc / improvable behavior **in ArkGate itself** → draft one upstream GitHub issue (`pedroknigge/arkgate` or the installed package `repository.url`), **ask the human to confirm send**, then `gh issue create`. Never auto-file. Never file ArkGate defects on the consumer product repo.
@@ -179,13 +191,14 @@ ArkGate has **always-on Layers** plus opt-in extras. The user chooses extras; yo
 2. Never call an import-edge violation an “invariant” or an aggregate sensor a “layer deny.”
 3. Absence of `arkRules` is **valid** — do not force ArkRules unless the user wants them or residual inventory clearly wants a pilot.
 4. Editing `arkrules/*` or applying structure fixes is **`/ark-adopt`** / **`/ark-autopilot`** — explore does not write (never invent `mechanical-safe`).
-5. CLI helpers: `ark-check --rules-inventory --json`, doctor JSON `rulesUnderContract`, sensors emit `ARKRULE_*` / `INVARIANT_UNCOVERED` with `evidence.arkruleId`.
+5. CLI helpers: `ark-check --rules-inventory --json`, doctor JSON `rulesUnderContract`, sensors emit `ARKRULE_*` / `INVARIANT_UNCOVERED` / `INVARIANT_CATALOG_EMPTY` with `evidence.arkruleId`.
 6. Never write `arkRun` or `arkOrder` from this skill. When extras are present, label residual **`[ArkRun]`** / **`[ArkOrder]`**. Wire one kernel candidate via `/ark-runtime`; one order-plane candidate via `/ark-order`. Do not invent `/ark-run`.
 
 
 ### Explore + ArkRules
 - Always run sensors for **both** planes when present: coverage/doctor **and** `--rules-inventory` if `arkRules` exists or brownfield may hide spaghetti rules.
 - Ranked table kinds may include `arkrules-opportunity` and `invariant-gap`.
+- Empty `invariants[]` on a populated Domain while `arkRules` is on is residual (`INVARIANT_CATALOG_EMPTY`), not done. Point at `arkrules/<Domain>.json`.
 - Dual-plan **B** may include: place advisory structure rules, extract one inventory candidate to Domain + `arkrules` entry, promote one covered invariant.
 - Field path: note whether starters emit `arkrules/*`.
 

package/templates/skills/ark-place.md

@@ -22,9 +22,21 @@ right house. Skills never enforce — CLI / hooks / CI do.
 
 - `filePath` is known before the call. Description alone is not a path.
 - Golden pattern is load-bearing when present. Adopt generates it.
+- An included file that matches no layer is not a pass. The write gate denies it
+  (`CONFIG_UNCLASSIFIED_FILES`). Place it in a layer folder, or send include/layer
+  drift to `/ark-adopt`. Do not write into a loose include gap.
 - Do not default a repository to Presentation.
+- When doctor JSON has `noDomainFrontend`, the new file is a Domain rule — not
+  another UI helper. Soft. Silent when Domain already has files or there is no
+  frontend. No `/ark-domain`.
 - When the matched layer has `layers[].description`, print that caption next to the
   layer name and globs. Omit when absent — do not invent a caption or `/ark-describe`.
+- When the matched layer has `layers[].trustBoundary`, print `trust: <tag>` next
+  to the layer name and globs. Omit when absent — do not invent a tag or `/ark-trust`.
+- When the matched layer has `layers[].owners`, print `owner: @handle` next
+  to the layer name and globs. Omit when absent — do not invent a person or `/ark-owners`.
+  When `requireLayerOwners` is on and the house has no owners, send that gap to
+  `/ark-adopt` before writing.
 - When `arkRun` is on: scaffold through the kernel (no `new` of managed types; declare
   `uses` / `reactsTo` / `raises` / `sends`; factory only in `arkRun.kernelRoots`,
   `compositionRoots` alias). Extra off → do not introduce the kernel. Enable it
@@ -69,6 +81,21 @@ When `ark_place` / the contract includes `layers[].description`, print that capt
 next to the layer name and globs. Omit it when the field is absent. Do **not** invent
 a caption or `/ark-describe`.
 
+## Layer trust (process)
+
+When the matched layer has `layers[].trustBoundary` (`public` | `auth` |
+`admin` | `internal`), print `trust: <tag>` next to the layer name and globs.
+Omit it when the field is absent. Do **not** invent a tag or `/ark-trust`.
+The tag is guidance, not an import-rule deny.
+
+## Layer owners (process)
+
+When the matched layer has `layers[].owners`, print `owner: @handle` (or
+`owner: name@host`) next to the layer name and globs. Omit when absent.
+Do **not** invent a person or `/ark-owners`. When `requireLayerOwners` is
+on and this house has no owners, do not write — hand off `/ark-adopt` to
+name who owns the folder.
+
 ## Deep modules (process)
 
 - Place so new code stays **deep**: one small public surface per concern; hide implementation details.
@@ -92,7 +119,9 @@ and — if they asked to build it — scaffold it there correctly.
 **No artifact given?** If the skill is invoked with nothing to place, don't error
 and don't guess — the artifact is the one thing only the user knows. Read the
 contract (step 1) and print the placement map from it: one row per declared layer
-with layer name, globs, and `layers[].description` when present (omit when absent),
+with layer name, globs, `layers[].description` when present,
+`layers[].trustBoundary` when present, and `layers[].owners` when present
+(omit any when absent),
 what belongs there, its directory, and which layers it may/may not import,
 plus the not-yet-adopted `suggestedLayers` as a footnote. Then ask what they want
 to place. That map is derived entirely from the repo, so producing it is real work,
@@ -134,7 +163,7 @@ ArkGate has **always-on Layers** plus opt-in extras. The user chooses extras; yo
 2. Never call an import-edge violation an “invariant” or an aggregate sensor a “layer deny.”
 3. Absence of `arkRules` is **valid** — do not force ArkRules unless the user wants them or residual inventory clearly wants a pilot.
 4. Missing layer home: add it via **`/ark-adopt`** in this session if needed, then write the file; never invent `mechanical-safe`.
-5. CLI helpers: `ark-check --rules-inventory --json`, doctor JSON `rulesUnderContract`, sensors emit `ARKRULE_*` / `INVARIANT_UNCOVERED` with `evidence.arkruleId`.
+5. CLI helpers: `ark-check --rules-inventory --json`, doctor JSON `rulesUnderContract`, sensors emit `ARKRULE_*` / `INVARIANT_UNCOVERED` / `INVARIANT_CATALOG_EMPTY` with `evidence.arkruleId`.
 6. Absence of `arkRun` is **valid**. Do not introduce the kernel speculatively. Skills never enforce this extra.
 7. Absence of `arkOrder` is **valid**. When on: Domain stays plane-free; first freeze ξ with `release()`; later ξ is `proposeRelease` then `apply`; never `update`/`patch`/`set` the pattern. Import `createOrderPlane` from `arkgate/order` (same npm package). Evaluate / wire one candidate via **`/ark-order`**.
 
@@ -180,7 +209,11 @@ the same files or weaken the gate.
    its forbidden globals, and exactly which layers the file may / must not import,
    straight from the contract (no guessing). When the matched layer has
    `layers[].description`, print that caption next to the layer name and globs;
-   omit it when absent. When present, also honor optional
+   omit it when absent. When the matched layer has `layers[].trustBoundary`,
+   print `trust: <tag>` next to the layer name and globs; omit it when absent.
+   When the matched layer has `layers[].owners`, print `owner: @handle`; omit
+   when absent.
+   When present, also honor optional
    **`goldenPattern`** (from `.ark/golden-pattern.json`) for **NEW code only** —
    advisory layout norm; never overrides the gate and never clears design-weak.
    Absent golden is normal. Otherwise load `ark.config.json`; after the matched preflight,
@@ -215,6 +248,8 @@ the same files or weaken the gate.
    `patterns`), intent-name prefix if the layer declares `intentPrefixes`, and
    which layers it may/may not import (from `rules`). When present, print
    `layers[].description` next to the layer name and globs; omit when absent.
+   Print `layers[].trustBoundary` as `trust: <tag>` when present; omit when absent.
+   Print `layers[].owners` as `owner: @handle` when present; omit when absent.
 4. **If the layer isn't adopted yet** (suggested but no directory): write the
    layer into `ark.config.json` (session-0 honesty — same as `/ark-adopt` for
    that glob) **then** write the file. Don't silently drop the code into a

package/templates/skills/ark-runtime.md

@@ -34,8 +34,10 @@ grind (`/ark-autopilot`); wire the order plane (`/ark-order`).
 | **ArkRun extra** (`arkRun` on `ark.config.json`, schema `1.2+`) | Gate contract: kernel usage + complete declarations | A score; Layers / ArkRules replacement; merge teeth while `advisory` |
 | **Kernel** `arkgate/runtime` | Kernel you construct with `createStrictArkKernel` (one instance per call) | A process-wide `getKernel()`; shipped cloud broker SDKs; production durability |
 
-Absence of the extra is **silent** — Layers and ArkRules verdicts stay identical. Doctor / status
-`arkRun` is always `notAScore`. Never invent 0–10 scores or pass/fail from this skill.
+Absence of the extra is **silent** — Layers and ArkRules verdicts stay identical. Compact
+doctor names ArkRun only when the extra is on (experimental, in-memory, not Postgres;
+`/ark-runtime` when residual remains). Doctor / status `arkRun` is always `notAScore`.
+Never invent 0–10 scores or pass/fail from this skill.
 
 ## Improvement compass note
 

package/templates/skills/ark-upgrade.md

@@ -143,7 +143,7 @@ ArkGate has **always-on Layers** plus opt-in extras. The user chooses extras; yo
 2. Never call an import-edge violation an “invariant” or an aggregate sensor a “layer deny.”
 3. Absence of `arkRules` is **valid** — do not force ArkRules unless the user wants them or residual inventory clearly wants a pilot.
 4. After upgrade, leftover architecture work is **`/ark-autopilot`** (never invent `mechanical-safe`).
-5. CLI helpers: `ark-check --rules-inventory --json`, doctor JSON `rulesUnderContract`, sensors emit `ARKRULE_*` / `INVARIANT_UNCOVERED` with `evidence.arkruleId`.
+5. CLI helpers: `ark-check --rules-inventory --json`, doctor JSON `rulesUnderContract`, sensors emit `ARKRULE_*` / `INVARIANT_UNCOVERED` / `INVARIANT_CATALOG_EMPTY` with `evidence.arkruleId`.
 6. Schema `1.3` extras stay off unless already on. Pin teaches `arkgate/runtime` and `arkgate/order` (same tarball), not a second install. Wire after upgrade via `/ark-runtime` / `/ark-order`. Do not invent `/ark-run`.