@agentsfleet/orly 0.10.13 → 0.11.0

package/core/operating-model.md

@@ -91,7 +91,7 @@ Auto-memory is **disabled** (`autoMemoryEnabled: false` + `CLAUDE_CODE_DISABLE_A
 - `*.zig` → read `dispatch/write_zig.md`; ZIG GATE fires. <!-- oracle-packs:language.zig -->
 - Auth-flow (token-minting handlers, credential-typed spec dimensions, the repository's auth directories) → read the repository's `docs/AUTH.md` first, where it exists. <!-- oracle-packs:domain.auth -->
 <!-- oracle-packs:start persona.indy -->
-- **Indy's reference checkouts** (the machine-local half of the rule above): TypeScript → `oss/supabase/apps/studio` + `oss/supabase/packages/{ui,ui-patterns}` + `oss/cli`; Zig → `oss/ghostty/src/`; Rust → `oss/bun/src/` + `oss/exonum` + `oss/core_api-develop`. Missing checkout → ask, then clone into `~/Projects/oss/`.
+- **Indy's reference checkouts** (`~/Projects/`): TypeScript → `oss/supabase/apps/studio` + `oss/supabase/packages/{ui,ui-patterns}` + `oss/cli`; Zig → `oss/ghostty/src/`; Rust → `oss/rs/exonum` + `oss/rs/arrow-rs` + `agentsfleet/rustd/` + `oss/rs/builder/components/builder-core/`. Missing → search `oss/rs/`; ask before cloning.
 <!-- oracle-packs:end -->
 
 **Forge detection:** `github.com` → `gh`; `gitlab.com` → `glab`. Check `git remote -v`.
@@ -124,24 +124,24 @@ Guards fire pre-hoc regardless of lifecycle stage. Override: `<GATE>: SKIPPED pe
 
 **🚦 Gate-flag triage** — gate fires → never silence, never harness-patch. **Mechanical** (obvious deterministic fix: fmt, lint-autofix, literal → const, over-length → split, dead code): auto-apply + inform the user in one line. **Judgment** (design call / weakened guarantee / security boundary / possible false-positive): STOP, surface the ask — 📟 flagged (symbol·file·line) · 🔦 fix scope (files·lines·follow-on) · 📈 what we gain · 💥 if not fixed (debt·blockages) · ☠️ my call — the user decides fix-or-defer. Never unilaterally call a flag a false-positive.
 
-**Seeded `.oracle/orly.json`?** Complete it first — `verify.*`, `surfaces`, opt-in packs: `dispatch/lifecycle.md` §Bootstrap.
+**Seeded `.orly/orly.json`?** Complete it first — `verify.*`, `surfaces`, opt-in packs: `dispatch/lifecycle.md` §Bootstrap.
 
 **Rule paths resolve relative to this repository's root.** Every `dispatch/…`, `docs/…`, and `audits/…` path a rule cites is a real file here — `orly init`/`orly update` materialised it from the packs this repository selected. A path your repo lacks means its sources never selected that pack, not that the reference is broken.
 
 **Dispatch index — full rule prose in each `dispatch/<entry>.md` façade. Read the façade when its trigger fires — sectioned: scan headers, read the sections the diff touches.** Trigger-surface extensions: `*.zig`, `*.ts`, `*.tsx`, `*.js`, `*.jsx`, `*.py`, `*.rs`, `*.go`, `*.sh`, `*.sql`, `*.mdx`, and public OpenAPI prose. Latent `.md` per entry, deterministic `.sh` where mechanisable. Signals: 🟢 pass · 🟠 warn · 🔴 fail · 🛑 blocked · 🔥 critical · 🤔 judgment-only · 🟣 delegated. Output glyphs: 🧲 eval · 🛍️ evidence · 👮 security · ⛈️ rule · 💡 info · 📌 note. The router below **is** the gate set.
 
-**Legacy-workaround family** — four rules together: **RULE NDC** (no dead code at write time, `docs/greptile-learnings/RULES.md`), **RULE NLR** (touch-it-fix-it cleanup), **RULE NLG** (no new legacy framing pre-`0.30.0`), **Legacy-Design Consult Guard** (user A/B/C consult before patching/keeping/testing legacy). **No compatibility aliases** — old verbs, flag aliases, route wrappers, env aliases, fallback spellings — unless the user explicitly asks in-session.
+**Legacy-workaround family** — four rules together: **RULE NDC** (no dead code at write time, `docs/greptile-learnings/RULES.md`), **RULE NLR** (touch-it-fix-it cleanup), **RULE NLG** (no speculative compatibility framing; selected product version policy applies), **Legacy-Design Consult Guard** (user A/B/C consult before patching/keeping/testing legacy). **No compatibility aliases** — old verbs, flag aliases, route wrappers, env aliases, fallback spellings — unless the user explicitly asks in-session.
 
 | Trigger — when you… | Dispatch | Latent façade carries · override |
 |---|---|---|
-| write `*.zig` | `write_zig` | `dispatch/write_zig.md` — memory safety, init/deinit + `errdefer`, pub shape verdict (`FILE SHAPE DECISION` — auto-mode does NOT cover), tagged unions, length caps, cross-compile both linux targets · `ZIG GATE` / `PUB GATE` / `LIFECYCLE GATE: SKIPPED per user override (reason: ...)`. | <!-- oracle-packs:language.zig -->
+| write `*.zig` | `write_zig` | `dispatch/write_zig.md` — memory safety, init/deinit + `errdefer`, pub shape verdict (`FILE SHAPE DECISION` — auto-mode does NOT cover), tagged unions, length caps, declared cross-compile matrix · `ZIG GATE` / `PUB GATE` / `LIFECYCLE GATE: SKIPPED per user override (reason: ...)`. | <!-- oracle-packs:language.zig -->
 | write `*.ts`/`*.tsx`/`*.js`/`*.jsx` | `write_ts_adhere_bun` | `dispatch/write_ts_adhere_bun.md` — TS FILE SHAPE DECISION at PLAN, `const`/import/Bun-primitive discipline, raw-HTML → design-system primitive, `*-[...]` → token utility · `UI GATE` / `DESIGN TOKEN GATE: SKIPPED per user override (reason: ...)`; auto-mode does NOT cover; reason must cite a concrete external constraint. | <!-- oracle-packs:language.typescript,language.javascript -->
 | write `*.rs` | `write_rust` | `dispatch/write_rust.md` — ownership, justified `unsafe`, preserved error variants, feature combinations, deterministic concurrency tests · 🤔 judgment-only. | <!-- oracle-packs:language.rust -->
 | write `*.go` | `write_go` | `dispatch/write_go.md` — wrapped errors, goroutine exit paths, context first, defer at acquire, `-race` · 🤔 judgment-only. | <!-- oracle-packs:language.go -->
 | write `*.py` | `write_python` | `dispatch/write_python.md` — standard-library parsing, context-managed resources, boundary validation, specific exceptions · 🤔 judgment-only. | <!-- oracle-packs:language.python -->
 | write `*.sh` | `write_shell` | `dispatch/write_shell.md` — quoted expansions, array arguments, temp-file cleanup, no untrusted `eval`, shell compatibility · 🤔 judgment-only. | <!-- oracle-packs:language.shell -->
 | write `*.mdx` | `write_mdx` | `dispatch/write_mdx.md` — Markdown JSX structure, front matter, links, code fences, image descriptions, Mintlify isolation · 🤔 judgment-only. | <!-- oracle-packs:language.mdx -->
-| write `schema/*.sql` | `write_sql` | `dispatch/write_sql.md` — schema / migration rules + Schema Table Removal Guard (`DROP`/`ALTER` / `schema/embed.zig` / migration-array edits), STS/NSQ/SGR/ITF rules · `SCHEMA GUARD: SKIPPED per user override (reason: ...)`. | <!-- oracle-packs:domain.sql -->
+| write SQL or migration registration | `write_sql` | `dispatch/write_sql.md` — schema / migration rules, repository live-data policy and owner approval for destructive changes; product-specific Schema Table Removal Guard only when selected. | <!-- oracle-packs:domain.sql -->
 | write **any** source file | `write_any` | `dispatch/write_any.md` — File & Function Length, LOGGING, MILESTONE-ID, ERROR REGISTRY (repo-declared scheme, delegated), UFS named-constants, GREPTILE end-of-turn read, legacy family · `LENGTH` / `LOGGING` / `MILESTONE ID` / `UFS GATE: SKIPPED per user override (reason: ...)`; auto-mode does NOT cover. | <!-- oracle-packs:universal.authoring -->
 | write a spec under `docs/v*/…` | `write_spec` | `dispatch/write_spec.md` — required + prohibited spec sections (SPEC TEMPLATE GATE), `docs/TEMPLATE.md` shape · `SPEC TEMPLATE GATE: SKIPPED per user override (reason: ...)`; auto-mode does NOT cover; reason must cite a concrete external constraint. | <!-- oracle-packs:workflow.specifications -->
 | write `src/http/handlers/**` / OpenAPI | `write_http` | `dispatch/write_http.md` — REST API design rules; reads `docs/REST_API_DESIGN_GUIDELINES.md` before · 🟣 delegated. | <!-- oracle-packs:domain.http -->
@@ -152,7 +152,7 @@ Guards fire pre-hoc regardless of lifecycle stage. Override: `<GATE>: SKIPPED pe
 | claim "tests pass / ready / shipping" | `verify` | `dispatch/verify.md` — verification tiers (`make` canonical; package-scoped runners are **not** verification), done-message glyph format · 🤔 judgment-only, `VERIFY GATE: <target> skipped per environment constraint (reason: ...)` only when genuinely unrunnable. | <!-- oracle-packs:product.agentsfleet -->
 | name a stream/channel/Redis namespace/queue/RPC/Postgres schema, or describe a flow | `name_architecture` | `dispatch/name_architecture.md` — architecture-consult discipline; grep relevant `docs/architecture/` (chat brainstorming counts) · **no override** — doc wins until reconciled. | <!-- oracle-packs:universal.authoring -->
 | run a lifecycle stage (open→close a stream, worktree setup, milestone bootstrap) | `lifecycle` | `dispatch/lifecycle.md` — stage runbooks: CHORE(open/close) checklists, PLAN expansions, spec discipline, deferral format, pre-PR gates, LAND · 🤔 judgment-only. |
-| edit the governance (`core/**`, `packs/**`, `schemas/**`, `src/**`, `registry.json`, generated `AGENTS.md`, `dispatch/`, audits, hooks) | `edit_rules` | `dispatch/edit_rules.md` — runs `make audit`, the `audits/agents-md.md` questionnaire, live comprehension evaluation when semantics change, and generated evidence · **no override** from the agent (user-only push: `SKIP_INVARIANCE_PUSH=1`). | <!-- oracle-packs:workflow.governance -->
+| edit the governance (`core/**`, `packs/**`, `schemas/**`, `src/**`, `registry.json`, generated `AGENTS.md`, `dispatch/`, audits, hooks) | `edit_rules` | `dispatch/edit_rules.md` — runs `make audit`, the `audits/agents-md.md` questionnaire, live comprehension evaluation when semantics change, and generated evidence · **no override** from the agent. | <!-- oracle-packs:workflow.governance -->
 
 ---
 
@@ -169,7 +169,7 @@ Guards fire pre-hoc regardless of lifecycle stage. Override: `<GATE>: SKIPPED pe
 
 | Event | Action |
 |---|---|
-| New milestone, plan-{eng,ceo,design}-review, `TODO.md` attempt | Invoke `orly-spec-new`. Land in `docs/v{N}/pending/`, `Status: PENDING`, commit on main. |
+| New milestone, plan-{eng,ceo,design}-review, `TODO.md` attempt | Invoke `orly-spec-new`. Land in `docs/v{N}/pending/`, `Status: PENDING`, commit on the detected default branch. |
 | Begin implementation OR branch carries spec changes in `pending/` | CHORE(open): `pending/`→`active/`, `Status: IN_PROGRESS` + `Branch:`, create worktree, commit on feature branch. **No code until 4 steps committed.** |
 | Every commit during implementation | Mark completed Dimensions/Sections `DONE` same commit as the code. |
 | All work complete, before PR | CHORE(close). |
@@ -215,7 +215,7 @@ Edit only approved scope; no opportunistic refactors. Stay in active worktree. C
 
 ### CONFORM
 
-Runs after EXECUTE, before VERIFY. Invokes the `conform` commands the repository declares in `.oracle/orly.json` and aggregates every gate verdict. Any 🔴 returns to EXECUTE; the lifecycle does not advance. This is the `work` gate's tier and the pre-commit hook runs it at every commit: declare a `conform` costing seconds, not minutes.
+Runs after EXECUTE, before VERIFY. Invokes the `conform` commands the repository declares in `.orly/orly.json` and aggregates every gate verdict. Any 🔴 returns to EXECUTE; the lifecycle does not advance. This is the `work` gate's tier and the pre-commit hook runs it at every commit: declare a `conform` costing seconds, not minutes.
 <!-- oracle-packs:start product.agentsfleet -->
 In `agentsfleet` this stage is `make harness-verify`; its output block and end-of-turn audit detail live in `docs/HARNESS_VERIFY_OUTPUT.md`. Required rows: FILE SHAPE, PUB GATE, LENGTH GATE, MILESTONE-ID GATE, ZIG GATE, UI GATE, DESIGN TOKEN GATE, UFS GATE, SCHEMA GUARD, GREPTILE GATE, Architecture consult, Coverage, and `/orly-write-unit-test`.
 <!-- oracle-packs:end -->

package/dispatch/edit_rules.md

@@ -20,8 +20,7 @@ This dispatch fires for edits to:
 - `.githooks/pre-commit`, `.githooks/pre-push`, or governance `Makefile` targets
 - `README.md` setup or propagation instructions
 
-The agent has no override. Indy may use `SKIP_INVARIANCE_PUSH=1` for one push
-when the reason is recorded in the newest commit message.
+The agent has no override. Governance pushes run the required audit.
 
 ## Required action
 
@@ -33,7 +32,9 @@ when the reason is recorded in the newest commit message.
    push path by policy (the hook records `--llm-result not-required` with its
    rationale); run the matrix manually with `make llmevals` (or `SMOKE=1`)
    when semantics change.
-5. Run `orly verify --write-evidence --llm-result pass`.
+5. Write evidence with `orly verify --write-evidence --llm-result pass` only
+   after a passing live run. The push policy below uses `not-required`;
+   an owner-approved live deferral never becomes a passing result.
 6. Emit the invariance report before declaring the work complete.
 
 Render command (writes this checkout's root `AGENTS.md`; pack sources already
@@ -49,9 +50,10 @@ Any failure returns to the edit. Do not patch the checker to silence its result.
 
 ## Push enforcement
 
-Pre-commit records the doc-read proof when governance files are staged, and
-defers `make audit` to pre-push. Pre-push runs the deterministic chain, runs one live fixture per installed agent for semantic
-changes, and regenerates `.oracle/evidence.json` against the pushed commit.
+Pre-commit checks existing doc-read records when governance files are staged
+and defers `make audit` to pre-push. Pre-push runs the deterministic chain and
+regenerates `.orly/evidence.json` for checkout HEAD; it does not pass pushed
+revisions to the verifier. Live comprehension runs manually for semantic changes.
 
 Repository synchronization remains explicit. Governance verification never
 mutates a consumer repository or sibling worktree.

package/dispatch/lib.sh

@@ -49,6 +49,7 @@ DISPATCH_LANG=""
 DISPATCH_EXTS=()
 DISPATCH_FILES=()
 DISPATCH_RC=0
+source "$DISPATCH_SCRIPTS/scope.sh"
 
 # Rule-code gloss map — canonical short expansions (full text in RULES.md legend).
 # Keep in sync with RULES.md; dispatch-coverage.sh fails on a code with no
@@ -111,29 +112,37 @@ dispatch_init() {
 # orly's own length gate — audits/logging.sh is 444 lines against a 350 cap —
 # and the first commit of an adoption failed on the adoption itself.
 dispatch_managed_paths() {
-  local config="$TARGET_ROOT/.oracle/orly.json"
+  local config="$TARGET_ROOT/.orly/orly.json"
   [ -f "$config" ] || return 0
-  sed -n '/"managed"[[:space:]]*:[[:space:]]*\[/,/\]/p' "$config" \
-    | grep -oE '"[^"]+"' \
-    | sed -e 's/^"//' -e 's/"$//' \
-    | grep -vx 'managed' || true
+  bun -e 'const c = JSON.parse(await Bun.file(process.argv[1]).text());
+    if (!Array.isArray(c.managed) || c.managed.some(p => typeof p !== "string" || p.includes("\u0000")))
+      throw new Error("invalid managed ownership array");
+    for (const p of c.managed) process.stdout.write(p + "\u0000");' "$config"
 }
 
 # Resolve targets: explicit file args, or --staged self-discovery via git.
 # Explicit arguments are never filtered — naming a file is asking about it.
 dispatch_resolve_files() {
   DISPATCH_FILES=()
+  audit_scope_init --all "$@"
+  audit_index_snapshot "$@"
+  DISPATCH_STAGED=0
   if [ "${1:-}" = "--staged" ]; then
-    local pathspecs=() e managed
+    DISPATCH_STAGED=1
+    local pathspecs=() e f owned skip managed_file
     for e in "${DISPATCH_EXTS[@]}"; do pathspecs+=("$e"); done
-    managed="$(dispatch_managed_paths)"
-    while IFS= read -r f; do
-      [ -n "$f" ] || continue
-      [ -n "$managed" ] && grep -qxF "$f" <<<"$managed" && continue
+    managed_file="$(mktemp "${TMPDIR:-/tmp}/orly-managed.XXXXXX")"
+    if ! dispatch_managed_paths > "$managed_file"; then
+      rm -f -- "$managed_file"; exit 2
+    fi
+    while IFS= read -r -d '' f; do
+      case "$f" in */vendor/*|vendor/*|*/third_party/*|third_party/*|*/node_modules/*|node_modules/*|*/dist/*|*/build/*|*/.next/*|*/.zig-cache/*) continue ;; esac
+      skip=0
+      while IFS= read -r -d '' owned; do [ "$f" != "$owned" ] || skip=1; done < "$managed_file"
+      [ "$skip" -eq 0 ] || continue
       DISPATCH_FILES+=("$f")
-    done \
-      < <(git -C "$TARGET_ROOT" diff --cached --name-only --diff-filter=ACMRT -- "${pathspecs[@]}" \
-          | grep -vE '(^|/)(vendor|third_party|node_modules|\.zig-cache|dist|build|\.next)/' || true)
+    done < <(audit_scope_paths "${pathspecs[@]}")
+    rm -f -- "$managed_file"
   elif [ "$#" -ge 1 ]; then
     local f matched
     for f in "$@"; do
@@ -157,18 +166,20 @@ dispatch_resolve_files() {
 # dispatch must never claim a file its gates cannot parse.
 dispatch_add_shebang_files() {
   [ "${1:-}" = "--staged" ] || return 0
-  local f base path firstline managed
-  managed="$(dispatch_managed_paths)"
-  while IFS= read -r f; do
-    [ -n "$f" ] || continue
-    [ -n "$managed" ] && grep -qxF "$f" <<<"$managed" && continue
+  local f base path firstline owned skip managed_file
+  managed_file="$(mktemp "${TMPDIR:-/tmp}/orly-managed.XXXXXX")"
+  if ! dispatch_managed_paths > "$managed_file"; then rm -f -- "$managed_file"; exit 2; fi
+  while IFS= read -r -d '' f; do
+    skip=0
+    while IFS= read -r -d '' owned; do [ "$f" != "$owned" ] || skip=1; done < "$managed_file"
+    [ "$skip" -eq 0 ] || continue
     base="${f##*/}"
     case "$base" in *.*) continue ;; esac
     path="$TARGET_ROOT/$f"; [ -f "$path" ] || path="$f"; [ -f "$path" ] || continue
     IFS= read -r firstline < "$path" || true
     case "$firstline" in "#!"*) DISPATCH_FILES+=("$f") ;; esac
-  done < <(git -C "$TARGET_ROOT" diff --cached --name-only --diff-filter=ACMRT \
-            | grep -vE '(^|/)(vendor|third_party|node_modules|\.zig-cache|dist|build|\.next)/' || true)
+  done < <(audit_scope_paths)
+  rm -f -- "$managed_file"
 }
 
 dispatch_header() {
@@ -198,9 +209,8 @@ dispatch_length_gate() {
 # Delegate to a deterministic leaf helper in audits/. Normalizes the verdict.
 # CODE prints with its gloss (no naked codes — audit-enforced).
 #
-# Leaf helpers have NON-UNIFORM arg contracts (e.g. audit-deinit-pairs takes
-# --staged; audit-ufs takes --all/no-arg after M70). The caller MUST pass the
-# mode the helper actually accepts as the 3rd arg — never assume --staged.
+# Leaf helpers receive explicit targets when the caller names files. In
+# staged mode the third argument preserves the helper's declared wider scope.
 #   dispatch_run_helper UFS    ufs.sh          --all
 #   dispatch_run_helper DEINIT deinit-pairs.sh --staged
 dispatch_run_helper() {
@@ -213,9 +223,14 @@ dispatch_run_helper() {
     DISPATCH_RC=1
     return 1
   fi
-  local log="/tmp/dispatch-${DISPATCH_LANG}-${code}.log"
-  if bash "$DISPATCH_SCRIPTS/$script" $mode >"$log" 2>&1; then
-    printf '  %-8s 🟢 %s — pass (audits/%s %s)\n' "$code" "$g" "$script" "$mode"
+  local receipt_dir log args=()
+  receipt_dir="$(mktemp -d "${TMPDIR:-/tmp}/orly-dispatch.XXXXXX")" || return 1
+  log="$receipt_dir/receipt.log"
+  if [ "$DISPATCH_STAGED" -eq 1 ]; then [ -z "$mode" ] || args+=("$mode")
+  else args=("${DISPATCH_FILES[@]}"); fi
+  if (umask 077; bash "$DISPATCH_SCRIPTS/$script" ${args[@]+"${args[@]}"} >"$log" 2>&1); then
+    printf '  %-8s 🟢 %s — pass (audits/%s); receipt: %s\n' "$code" "$g" "$script" "$log"
+    cat "$log"
   else
     printf '  %-8s 🔴 %s — fail (audits/%s %s) — see %s\n' "$code" "$g" "$script" "$mode" "$log"
     DISPATCH_RC=1

package/dispatch/lifecycle.md

@@ -13,7 +13,7 @@ are entering, not the whole file.
 ## What runs at each stage
 
 This is the authoritative sequence. Commands come from the repository's
-`.oracle/orly.json`; the engine contains no product-specific build recipes.
+`.orly/orly.json`; the engine contains no product-specific build recipes.
 
 | Stage | Runs | Owner |
 |---|---|---|
@@ -145,7 +145,7 @@ into a separate tree.
 
 ## Bootstrap & milestone gates
 
-- **Complete `.oracle/orly.json` on first sight.** `orly init` seeds it
+- **Complete `.orly/orly.json` on first sight.** `orly init` seeds it
   mechanically — it reads the Makefile (following `include` one level) and
   `package.json` scripts, matches a fixed list of target names, and writes what
   it matched. It finds the obvious ones and misses the rest, and it never
@@ -166,6 +166,7 @@ into a separate tree.
   A documentation repository can declare `verify.docs` for its site and link
   checks without application unit or integration suites. `init` reports
   missing commands; `doctor` and the gates reject incomplete setup.
+<!-- oracle-packs:start product.agentsfleet -->
 - **Priming:** (1) Human runs `playbooks/founding/01_bootstrap/001_playbook.md`.
   (2) Agent runs `./playbooks/founding/02_preflight/00_gate.sh` (green before
   next). (3) Agent runs `playbooks/founding/03_priming_infra/001_playbook.md`.
@@ -176,6 +177,7 @@ into a separate tree.
 - **Agent-first sequencing** — minimize human steps; post-handoff steps
   retryable + idempotent. Vault is the inter-step interface; never pass creds
   by argument/env.
+<!-- oracle-packs:end -->
 
 ## PLAN — expansions
 
@@ -186,8 +188,8 @@ surface option + cost, the user picks. Read docs when behavior is unclear.
 
 **Surface-area checklist** — yes/no + reason each: OpenAPI changes (list paths)
 · the product's CLI · user-facing docs · release notes
-/ version bump · schema changes (≤100 lines/file, single-concern, update
-`schema/embed.zig` + migration array) · Schema Removal Guard output ·
+/ version bump · schema changes (the repository's migration registration,
+file limits and live-data policy) · Schema Removal Guard output where selected ·
 spec-vs-rules conflict (amend spec).
 
 ## EXECUTE — spec discipline expansions
@@ -204,8 +206,10 @@ spec-vs-rules conflict (amend spec).
   update spec first); every Acceptance Criterion → verifiable command ("works
   correctly" is not a criterion; "`make test` passes" is); no code commits
   without tests (`/orly-write-unit-test`); every Error Table row → negative test.
+<!-- oracle-packs:start persona.indy -->
 - **Recovery notes:** local Docker `ENOSPC` → `~/bin/mac-cleanup.sh`, verify
   `docker system df`, retry.
+<!-- oracle-packs:end -->
 
 ## CHORE (close) — required outputs
 
@@ -255,10 +259,18 @@ version-sync check passes where defined; branch contains `origin/main` HEAD
 **`orly gate pr` follows the spec through the close.** A spec moved to `done/`
 on this branch is still discovered — its `Branch:` header names the branch —
 and every spec criterion runs against it; skip-pass is only for genuinely
-spec-less branches. A deliberately folded spec retains the exact branch header
+spec-less branches. Branch and fold headers accept a plain token or an inline-code
+token. Active specs explicitly naming another branch do not displace the current
+branch's owner; an active spec without a branch declaration remains in scope.
+A deliberately folded spec retains the exact branch header
 and adds `**Folded-into:** \`M178_001\`` naming the owning spec. Discovery
 validates that relation and gates the sole non-folded owner; two non-folded
-specs on one branch remain a hard error. Mechanical criteria: `spec.moved`
+specs on one branch remain a hard error. **The same relation holds in
+`active/`, from the moment the fold is decided.** A second workstream may sit
+beside an open stream while it names that stream through `Folded-into`, and the
+gates run against the owner — a fold is not a second stream, and it was decided
+when the scope was, not when the spec moved. Extra `active/` specs without the
+header are still the hard error they were: one stream per worktree. Mechanical criteria: `spec.moved`
 (`Status: DONE` ⇒ the spec sits under `done/` and was moved on this branch) · `spec.baseline`
 (`Test Baseline:` recorded) · `spec.ordering` (the branch's first commit
 carries the spec — no code before CHORE(open)) · `spec.deferrals` (a deferral

package/dispatch/name_architecture.md

@@ -17,7 +17,7 @@ cardinality*. It is a pure **🤔 judgment** dispatch grounded in `docs/architec
 - Naming a stream / pub-sub channel / Redis key namespace / consumer group /
   queue / RPC method / Postgres schema / table.
 - Asserting cardinality ("one row per X", "exactly one consumer per stream",
-  "fleet-wide vs per-tenant").
+  "repository-wide vs per-tenant").
 - Describing a flow ("on crash → X reclaims via Y", "trigger source A lands on
   stream B with actor C").
 - Answering a user question about how data flows between components.
@@ -81,13 +81,18 @@ branch settles both before the Pull Request (PR) opens:
   branch that touched flow-defining code produces a non-empty
   `git diff origin/main..HEAD -- docs/architecture/`. Else PR Session Notes
   documents why nothing architectural changed.
-- **Docs project `~/Projects/docs/`** (user-facing, `docs.agentsfleet.net`). When
+- **Published docs** (the repository's declared `surfaces.docs`). When
   the change alters documented user-facing behaviour (endpoints, Command-Line
   Interface (CLI) surface, flags, flows users see), the affected pages are
-  revised per the CHORE(close) required
+  revised in their owning repository per the CHORE(close) required
   outputs in `AGENTS.md` — a changelog `<Update>` alone is insufficient.
   Internal-only reshaping with no documented-behaviour change → no docs-project
   edit, and Session Notes say so.
 
+<!-- oracle-packs:start product.agentsfleet -->
+For `agentsfleet`, the published docs repository is `~/Projects/docs/` at
+`docs.agentsfleet.net`; edits use its own branch and explicit authorization.
+<!-- oracle-packs:end -->
+
 Updating one home and not the other is the failure mode this section names: the
 internal doc drifts from what users are told, or vice versa.

package/dispatch/verify.md

@@ -27,7 +27,7 @@ pass".
 
 ## Repository commands are canonical
 
-The commands in `.oracle/orly.json` define full verification. Use repository
+The commands in `.orly/orly.json` define full verification. Use repository
 Make targets where declared; a repository may also declare its native tools
 directly. A narrower package run never substitutes for a declared full check.
 Documentation repositories may use `verify.docs` for site and link checks;

package/dispatch/write_any.md

@@ -346,7 +346,7 @@ ERROR REGISTRY GATE: <file>
 **Family:** Constant discipline. **Source:** `AGENTS.md` conformance enforcement
 + the selected language façade's Uniform Free Strings (UFS) clauses.
 
-**Triggers** — every `Edit`/`Write` to a source file under the repository's own source surfaces — the `surfaces.user` prefixes it declares in `.oracle/orly.json`, or its source roots where it declares none — matching `*.zig`, `*.ts`, `*.tsx`, `*.js`, `*.jsx`, `*.rs`, `*.go`. Excluded: `vendor/`, `third_party/`, `.zig-cache/`, `node_modules/`, `*.tsbuildinfo`. `*.py` and `*.sh` fire this façade but are held out of the UFS leaf — see Scope. Each repository binds its own prefixes; naming one repository's layout here is what sends every other repository a trigger list it cannot match.
+**Triggers** — every `Edit`/`Write` to a source file under the repository's own source surfaces — the `surfaces.user` prefixes it declares in `.orly/orly.json`, or its source roots where it declares none — matching `*.zig`, `*.ts`, `*.tsx`, `*.js`, `*.jsx`, `*.rs`, `*.go`. Excluded: `vendor/`, `third_party/`, `.zig-cache/`, `node_modules/`, `*.tsbuildinfo`. `*.py` and `*.sh` fire this façade but are held out of the UFS leaf — see Scope. Each repository binds its own prefixes; naming one repository's layout here is what sends every other repository a trigger list it cannot match.
 
 <!-- oracle-packs:start product.agentsfleet -->
 In this repository those surfaces are `src/` (Zig), `rustd/crates/*/src/` (Rust), `cli/src/` and `ui/packages/*/{src,app,lib,components,pages,tests}/` (TypeScript).
@@ -446,19 +446,26 @@ The test-seam match is deliberately narrow — `test` as a whole word or a `-`/`
 `audits/ufs.sh` is invoked at CONFORM by the agent. Convention follows the sibling audit scripts (`logging.sh`, `error-codes.sh`, `deinit-pairs.sh`, `spec-template.sh`) — none of them wire into `make lint`; the agent runs each as part of the gate ceremony, with the result feeding the CONFORM table. The script is generic — no manifest of known literals — so it scales as the codebase grows:
 
 ```bash
-bash audits/ufs.sh          # full-codebase scan (default and only mode)
+bash audits/ufs.sh          # full-codebase scan (default)
 bash audits/ufs.sh --all    # alias for default
+bash audits/ufs.sh --staged # indexed bytes of staged source files
+bash audits/ufs.sh -- src/example.ts # explicit working-tree source files
 ```
 
 The script emits a violations table. Empty table = pass. Each row is one of:
 
 - `string-dup-file <file> "<literal>" <count>` — same string ≥2× in one file
-- `string-dup-module <module> "<literal>" <count>` — same string ≥2× across a module/package
 - `numeric-suspect <file>:<line> <literal>` — power-of-ten or known unit-factor numeric not bound to a const (excludes anything on a `// pin test: literal is the contract` line)
 - `cross-runtime-orphan <const_name> <runtime>` — SCREAMING_SNAKE constant defined in one runtime, missing from a sibling runtime that the same diff touches
 
 Violations resolve by either (1) extracting to a named const + replacing all sites, (2) adding the constant in the missing sibling runtime same-commit, or (3) adding the `// pin test: literal is the contract` comment.
 
+Cross-file repeated strings are a reviewer check: the leaf does not emit
+`string-dup-module`. Review the changed module's callers and shared vocabulary;
+a clean per-file scan does not establish that each value has one definition.
+In staged mode, both source and configuration come from an owned index snapshot;
+unstaged edits cannot clear an indexed violation.
+
 #### CONFORM row
 
 > [DETERMINISTIC → UFS]

package/dispatch/write_changelog.md

@@ -2,7 +2,7 @@
 
 This is the prose the AGENT reads after `write_documentation.md` and
 `docs/DOCUMENTATION_RULES.md`, **before writing any `<Update>` entry in the
-changelog** (`~/Projects/docs/changelog.mdx`). Like `verify` and
+repository's declared changelog**. Like `verify` and
 `name_architecture`, it has **no deterministic `.sh` half** — voice is a judgment
 call no script can grade. It is a pure **🤔 judgment** dispatch: the agent reads
 this, drafts the entry, and self-audits against the rules below. The deep
@@ -12,9 +12,8 @@ reference is `docs/CHANGELOG_VOICE.md` (Mintlify-style) — read it before writi
 
 - 🤔 DECIDE — judgment-only; the agent writes to the voice below and self-audits.
   No script gates it — it blocks the *turn* (the changelog entry), not a commit.
-- 🟣 delegated — the changelog itself lives in `~/Projects/docs` (its own repo +
-  own-branch flow per AGENTS.md Operational defaults); dotfiles carries only the
-  voice discipline.
+- 🟣 delegated — edit the declared changelog in its owning repository with
+  that repository's branch rules and authorization.
 
 ## Trigger — read `docs/DOCUMENTATION_RULES.md`, then `docs/CHANGELOG_VOICE.md`
 
@@ -40,9 +39,13 @@ a gate skip.
   names, money amounts stay verbatim.
 - **Internal cleanup** gets aggressive trimming, not a paragraph.
 - **History is archived, not rewritten** — past entries are an immutable record.
+- **Rate claims** match the repository's canonical billing constants and
+  published rate tables, with both updated when the behavior changes.
+<!-- oracle-packs:start product.agentsfleet -->
 - **Rate constants** are declared once, in `afd_billing`'s `nanos.rs`, with the
   nanos denominator in `afd_core::money`. A changelog money or rate claim must
   match those — and `rates.mdx` in the docs repository, which no test reaches.
+<!-- oracle-packs:end -->
 
 ## Required output (self-audit line before committing the changelog)
 

package/dispatch/write_go.md

@@ -31,4 +31,4 @@ Both are carve-outs for what the *language* makes unfixable, not permission —
 a flag name or a label spelled inline twice is still the rule.
 
 The repository owns formatting, vet, lint, build, and test commands — it
-declares them in `.oracle/orly.json`.
+declares them in `.orly/orly.json`.

package/dispatch/write_http.md

@@ -7,19 +7,17 @@ self-contained product-surface design guide, so this façade *routes* to it rath
 than duplicating it. **Residence vs enforcement:** `orly init` materialises the
 guide into this repository under the `domain.http` pack — it is a real local
 file, not something read through another checkout. Its checks are *enforced*
-in the product repo (`make lint` / `/review` against the guide) — hence
+in the consuming repository (its declared checks and `/review` against the guide) — hence
 **🟣 delegated**.
 
 **Signal legend:**
 
-- 🟣 delegated — the REST checklist is enforced in the product repo (agentsfleet),
-  by `make lint` + adversarial `/review` against the guide. Dotfiles carries the
-  doc itself, the routing, and the discipline that the guide is a *checklist, not
-  background reading*.
+- 🟣 delegated — the consuming repository enforces the checklist through its
+  declared checks and adversarial review. The installed guide is a checklist.
 
 ## Trigger — read `docs/REST_API_DESIGN_GUIDELINES.md` before
 
-- Editing `src/http/handlers/**`, `public/openapi/**`, or any `route_*` file.
+- Editing the repository's HTTP handlers, route registration or OpenAPI sources.
 - Adding, modifying, or removing an HTTP endpoint or its OpenAPI shape.
 
 **Override:** none from dotfiles — the REST guide's own `MUST`/`SHOULD`
@@ -38,7 +36,7 @@ checklist run at `CHORE(close)` before `gh pr create`.
 ## Why route, not merge
 
 REST design rules bind the *product repo's* HTTP surface, but the doc has one
-canonical source in dotfiles — `orly init`/`orly update` materialise it here,
+canonical source in the selected pack — `orly init`/`orly update` materialise it here,
 so this repository's copy tracks that source. Merging its full text into
 this façade would create a second source of truth. The guide stays canonical;
 this façade is the dispatch entry that points the agent at it when the trigger

package/dispatch/write_python.md

@@ -7,4 +7,4 @@ context managers. Validate data at parse boundaries and preserve specific
 exception classes until the caller can decide how to respond.
 
 The repository owns formatting, linting, type checking, and tests — it declares
-them in `.oracle/orly.json`.
+them in `.orly/orly.json`.

package/dispatch/write_rust.md

@@ -10,10 +10,26 @@ Test the feature combinations the repository actually builds. Concurrency work
 needs a deterministic contention test, not only a happy-path asynchronous test.
 
 The repository owns formatting, Clippy, build, test, security, and benchmark
-commands — it declares them in `.oracle/orly.json`.
+commands — it declares them in `.orly/orly.json`.
 
 ## Reference guideline (mandatory in review)
 
+Before designing Rust modules, read the relevant implementation in Exonum,
+Apache Arrow's Rust implementation, or the local `agentsfleet` Rust workspace.
+Indy's checkouts are `~/Projects/oss/rs/exonum`,
+`~/Projects/oss/rs/arrow-rs`, `~/Projects/agentsfleet/rustd/`, and
+`~/Projects/oss/rs/builder/components/builder-core/`.
+Use Exonum for state and API boundaries and Arrow for typed data and workspace
+structure. Use `agentsfleet/rustd/crates/agentsfleetd/` specifically for errors
+and the command-line interface (CLI); inspect its actual call sites before designing.
+Use `afd_core::env::EnvSource` for injected process and test environments.
+Builder's `ConfigFile` trait supplies prior art for composable file loading and
+cause-preserving parsing. Read its call sites; retain current edition safety and
+library logging rather than copying its older global environment mutation or logger.
+Read only relevant modules and name the pattern applied or the reason to diverge.
+These are read-only references; consumer changes require their own authorization.
+Other machines locate the equivalent checkout before asking to clone one.
+
 Microsoft's Pragmatic Rust Guidelines are this pack's depth — thorough,
 agent-facing, and continuously maintained upstream. The local copy lives at
 `~/Projects/oss/rust-guidelines/all.txt`; fetch it when absent:

package/dispatch/write_shell.md

@@ -7,4 +7,4 @@ every exit path. Avoid `eval` for external input. Match the repository's require
 shell and macOS Bash compatibility level.
 
 The repository owns ShellCheck and executable tests — it declares them in
-`.oracle/orly.json`.
+`.orly/orly.json`.

package/dispatch/write_spec.md

@@ -35,6 +35,8 @@ parsed Markdown tree. Code examples and quoted headings cannot supply sections.
   decides their applicability from the actual branch diff. Additional
   spec-specific commands and explicitly named manual checks remain valid.
 
+## Scope
+
 `--staged` reads spec contents, configuration, and local references from the Git
 index. `--file <path>` checks the working copy. Missing runtime or configuration
 fails these readiness checks. Bulk `--all` and `--include-done` scans retain
@@ -88,4 +90,4 @@ Incident-derived rules the deterministic half can't check — apply while writin
 
 - `docs/TEMPLATE.md` — canonical Prohibited section + required sections.
 - `orly-spec-new` skill — creates specs from the template; inserts the banner.
-- `audits/spec-template.sh` — mechanical regex enforcement, runs in `make lint`.
+- `audits/spec-template.sh` — structural and prohibited-section checks; `orly gate pr` invokes it through `spec.gate`.

package/dispatch/write_sql.md

@@ -26,7 +26,21 @@ deterministic façade in this snapshot.
 
 > [JUDGMENT → SCH]
 
-Triggers on every `Edit`/`Write` to `schema/*.sql`, `schema/embed.zig` (`@embedFile` constants), and the canonical migration array in `src/cmd/common.zig`. **Before authoring DDL, read `docs/SCHEMA_CONVENTIONS.md`** (naming, types, schema-qualification). SQL embedded in handlers (`*.zig`) and integration-test fixtures is also governed by the companion rules below — those surfaces additionally fire `write_zig.md` and the GREPTILE GATE.
+Triggers on SQL files, embedded SQL and the repository's migration registration.
+Before writing schema changes, read `docs/SCHEMA_CONVENTIONS.md` and locate the
+repository's current migrations, registration and deployment policy.
+Embedded SQL also fires its selected language façade and the GREPTILE GATE.
+
+## Repository schema policy
+
+> [JUDGMENT → SCH]
+
+Preserve shipped migrations and live data under the repository's own policy.
+Destructive changes require the owner's approval for the specific change.
+A version number, missing `VERSION` file or another product's rebuild policy
+never proves that this repository's data is disposable.
+
+<!-- oracle-packs:start product.agentsfleet -->
 
 ## Merged from dissolved gate cards
 
@@ -44,7 +58,7 @@ The **Schema Table Removal Guard** card dissolves into this façade; its prose i
 
 - Creating, editing, or deleting any file under `schema/*.sql`.
 - Editing `schema/embed.zig` (any `@embedFile` constant).
-- Editing the canonical migration array in `src/cmd/common.zig`.
+- Editing the canonical migration array in `rustd/crates/afd_db/src/migration.rs`.
 - Writing `DROP TABLE`, `ALTER TABLE`, or `SELECT 1;` into any SQL file.
 - Accepting a spec dimension prescribing a "DROP migration", "ALTER migration", or "version marker".
 
@@ -60,7 +74,7 @@ To remove a table:
 
 1. `rm schema/NNN_foo.sql`
 2. Remove `@embedFile` from `schema/embed.zig`
-3. Remove the entry from the migration array in `src/cmd/common.zig` and update length + index-based tests.
+3. Remove the entry from the migration array in `rustd/crates/afd_db/src/migration.rs` and update its registration tests.
 
 **Forbidden:** `ALTER TABLE`, `DROP TABLE`, `SELECT 1;` markers, comment-only files, "keep file for slot numbering". Slot gaps are fine — the DB is wiped on rebuild.
 
@@ -82,6 +96,7 @@ SCHEMA GUARD: VERSION=<v> (<0.30.0 ? teardown : migrate)
 ```
 
 Below `0.30.0`, all three rm- lines appear. From `0.30.0`, replace them with `migration:schema/<NNN>_<change>.sql`.
+<!-- oracle-packs:end -->
 
 ## Companion SQL rules (retained in `docs/greptile-learnings/RULES.md`)
 
@@ -99,16 +114,23 @@ No string literal in `schema/**.sql` may name a value or identifier the applicat
 
 > [DETERMINISTIC → TODO-CHECK]
 
-No magic numbers; all SQL in handlers is schema-qualified (`core.table`, not `table`) — unqualified names fail when `search_path` differs across environments. (RULES.md `RULE NSQ`.)
+No magic numbers; qualify tables with the repository's actual schema —
+unqualified names fail when `search_path` differs across environments.
+(RULES.md `RULE NSQ`.)
 
 ### RULE SGR — Migrations include GRANT statements
 
 > [DETERMINISTIC → TODO-CHECK]
 
-Every `CREATE TABLE` migration ends with `GRANT`s for every role that queries the table (`api_runtime` / `worker_runtime`), mirroring the table's callers. PostgreSQL denies by default — a missing grant fails only at first runtime use. (RULES.md `RULE SGR`.)
+Every `CREATE TABLE` migration grants the required operations to the roles that
+actually query the table. PostgreSQL denies by default — a missing grant fails
+only at first runtime use. (RULES.md `RULE SGR`.)
 
 ### RULE ITF — Integration tests use the real schema
 
 > [JUDGMENT → ITF]
 
-An integration test touching a production table seeds rows through a shared `src/db/test_fixtures_<scope>.zig` module against the real schema — never a session-local `CREATE TEMP TABLE` mocking the production shape (the mock drifts and hides schema changes). Fixtures use semantic scope names, never milestone-numbered ones. (RULES.md `RULE ITF`.)
+An integration test touching a production table uses shared repository fixture
+helpers against the real schema — never a session-local `CREATE TEMP TABLE`
+mocking the production shape. Fixtures use semantic scope names.
+(RULES.md `RULE ITF`.)