@etiquekit/etq 1.0.12 → 1.0.14

package/AGENTS.md

@@ -1,37 +1,30 @@
 # Etiquette Agent Guide
 
-## If you installed this package
+This repo is the Etiquette source repo. Keep the all-developer onboarding path small.
 
-You are reading the INSTALLED copy of the Etiquette CLI (npm or tarball) —
-"this repo" below refers to Etiquette's source repository, not your project.
-As an agent working in a project governed by Etiquette:
+## Default Rule
 
-1. Read [README.md](README.md), then [QuickStart.md](QuickStart.md).
-2. Orient with `etq whereami`; join your assigned seat; read the task
-   envelope and the project's `docs/work/runbooks/WORKING_DISCIPLINE.md`.
-3. Respect allowed writes, run the named validation, write the receipt at
-   the path `pickup` names, post it, and pass `etq return check` before
-   claiming completion.
-
-Commands record evidence; they never grant, merge, close, publish, or
-promote.
-
-## If you are working on the Etiquette source repo
-
-Keep the all-developer onboarding path small. New engineers start with:
+New engineers should start with:
 
 1. [README.md](README.md)
 2. [docs/SEAT_PROVISIONING.md](docs/SEAT_PROVISIONING.md)
 3. [templates/etiquette-vanilla-v0/README.md](templates/etiquette-vanilla-v0/README.md)
 
-Do not send new seats through internal history, old coordination lanes, or
-maintainer-only notes.
+Do not send new seats through internal history, old coordination lanes, or maintainer-only notes.
+
+## Ownership
+
+This repo owns:
+
+- the minimal vanilla seat scaffold;
+- optional runtime seat-pack scaffolds;
+- shared task, readiness, and receipt contracts;
+- vendor-neutral seat rebind guidance for interrupted, resumed, swapped, or
+  migrated sessions;
+- validation scripts for release hygiene.
+
+This repo does not own product repos, product lane state, secrets, hosted services, or runtime vendor setup.
 
-This repo owns: the minimal vanilla seat scaffold; optional runtime seat-pack
-scaffolds; shared task, readiness, and receipt contracts; validation scripts
-for release hygiene. It does not own product repos, product lane state,
-secrets, hosted services, or runtime vendor setup.
+## Editing Rule
 
-Release-facing docs must stay role-based and portable. Do not introduce
-person names, local machine paths, historical bus references, or
-project-specific lane IDs into the default onboarding surface.
+Release-facing docs must stay role-based and portable. Do not introduce person names, local machine paths, historical bus references, or project-specific lane IDs into the default onboarding surface.

package/LICENSE

@@ -1,4 +1,3 @@
-
                                  Apache License
                            Version 2.0, January 2004
                         http://www.apache.org/licenses/
@@ -138,8 +137,8 @@
 
    6. Trademarks. This License does not grant permission to use the trade
       names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
+      except as required for reasonable and customary use in describing
+      the origin of the Work and reproducing the content of the NOTICE file.
 
    7. Disclaimer of Warranty. Unless required by applicable law or
       agreed to in writing, Licensor provides the Work (and each

package/NOTICE

@@ -1,5 +1,7 @@
-Etiquette (etq)
-Copyright 2026 The Etiquekit Authors
+Etiquette
+Copyright (c) 2026 Leepick Inc, US.
 
-Local-first, git-backed agent-workflow governance toolkit.
-Distributed under the Apache License, Version 2.0.
+This product includes software developed by Leepick Inc.
+
+Etiquette, Etq, and the Etiquette name are trademarks of Leepick Inc.
+Use of these names does not grant trademark rights.

package/QuickStart.md

@@ -1,53 +1,51 @@
 # Quick Start
 
-For a clean repo, a team canary, or a new Etiquette developer.
+Get from zero to a governed working project in about two minutes.
 
-Prereqs: `git >= 2.40` and `bun >= 1.3` on `PATH`. macOS and Linux.
+Prereqs: Git, Node 18+ (for npm install) or Bun `>=1.3.0`.
 
 ## 1. Get The CLI
 
+The published package:
+
 ```sh
-npm install -g @etiquekit/etq                      # etq + etiquette on PATH
-curl -fsSL https://etiquekit.com/install.sh | sh   # or: native installer
+npm install -g @etiquekit/etq
+# or project-local: npm install @etiquekit/etq && alias etq=./node_modules/.bin/etq
+etq --help
 ```
 
-The installer verifies every artifact against a pinned public key before
-anything executes and installs under `~/.etiquette`. Offline or air-gapped:
-download `etiquette-<version>.tgz` plus `SHA256SUMS` and `SHA256SUMS.sig`
-from `https://etiquekit.com/releases/`, verify them (see the README's
-"Verify releases"), then:
+Bootstrap a project and run your first cycle:
 
 ```sh
-ETQ_LIB="$HOME/.etiquette/lib/etiquette-<version>"
-mkdir -p "$ETQ_LIB" "$HOME/.etiquette/bin"
-tar -xzf etiquette-<version>.tgz --strip-components=1 -C "$ETQ_LIB"
-ln -sfn "$ETQ_LIB/bin/etiquette" "$HOME/.etiquette/bin/etiquette"
-export PATH="$HOME/.etiquette/bin:$PATH"
+cd your-repo
+etq bootstrap local --project . --task-prefix DEMO --ask
+etq doctor --project .            # expect: rig_doctor: pass
+# then follow the printed join/pickup commands
 ```
 
+Private or air-gapped rollout: use [docs/TEAM_HANDOFF.md](docs/TEAM_HANDOFF.md).
+
 ## 2. Initialize A Project
 
 From the project repo:
 
-Same core order as the README quickstart; `handoff`/`whereami` are optional
-orientation verbs. `bootstrap local` does not replace `init`.
-
 ```sh
-etq init --project "$PWD"
-etq doctor --project "$PWD"
-etq bootstrap local --project "$PWD" --profile codex-cc-gemini --task-prefix APP
-etq setup --target auto --project "$PWD"
-etq handoff --project "$PWD" --profile codex-cc-gemini --task-prefix APP
-etq whereami --project "$PWD" --seat codex-seat --task APP-001
-etq join --project "$PWD" --seat codex-seat
-etq pickup --project "$PWD" --seat codex-seat --task APP-001 --allow-current-project --text
-etq console board --project "$PWD" --text
+ETQ=${ETQ:-etiquette}
+"$ETQ" setup --target codex --project "$PWD"
+"$ETQ" handoff --project "$PWD" --task-prefix APP
+"$ETQ" bootstrap local --project "$PWD" --task-prefix APP --ask
+"$ETQ" whereami --project "$PWD" --seat impl-seat --task APP-001
+"$ETQ" doctor --project "$PWD"
+"$ETQ" join --project "$PWD" --seat impl-seat
+"$ETQ" pickup --project "$PWD" --seat impl-seat --task APP-001 --allow-current-project --text
+"$ETQ" console board --project "$PWD" --text
 ```
 
 `bootstrap local` creates repo-local state, seats, task envelopes, pickup docs,
 events, and runbooks. It does not grant, publish, merge, close, or promote.
-`handoff` is a read-only guide: it prints install, bootstrap, and pickup
-commands without changing anything.
+With `--ask`, it asks for the first-run shape, explains that seats are roles and
+runtimes are temporary occupants, confirms the default write boundary, and stays
+non-blocking in CI or scripted runs.
 
 ## 3. Orient The Live Seat
 
@@ -55,24 +53,21 @@ Run `whereami` whenever a developer or agent resumes, changes directories, or
 inherits a worktree:
 
 ```sh
-etq whereami --project "$PWD" --seat codex-seat --task APP-001
-etq pickup --project "$PWD" --seat codex-seat --task APP-001 --allow-current-project --text
+"$ETQ" whereami --project "$PWD" --seat impl-seat --task APP-001
+"$ETQ" pickup --project "$PWD" --seat impl-seat --task APP-001 --allow-current-project --text
 ```
 
 Runner resume recovers chat context; `whereami` confirms the repo, branch, task
 envelope, and runbook. For branch hygiene, read [docs/WORKTREE_QOL.md](docs/WORKTREE_QOL.md).
+For in-session pickup UX, use the `seat-session-bootstrap` skill.
 
 ## 4. Check And Record Evidence
 
-Completion gate: write the receipt at the path `pickup` names (`etq receipt scaffold --task <ref> --seat <id>` writes a starter stub), post it
-(`etq post --role implementation-return --lane <task> --from <seat> --to <seat>`),
-then `etq return check`. Separately, `dispatch check` gates ROUTING before
-work begins — create checkable dispatch examples, then run the generated
-command:
+Create checkable dispatch examples, then run the generated command:
 
 ```sh
-etq dispatch scaffold --project "$PWD" --task-id APP-001 --seat codex-seat
-etq dispatch check --project "$PWD" \
+"$ETQ" dispatch scaffold --project "$PWD" --task-id APP-001 --seat impl-seat
+"$ETQ" dispatch check --project "$PWD" \
   --mode docs/work/dispatch/APP-001/mode.yaml \
   --task docs/work/dispatch/APP-001/task.yaml \
   --sandbox-receipt docs/work/dispatch/APP-001/receipt.yaml \
@@ -82,14 +77,7 @@ etq dispatch check --project "$PWD" \
 `dispatch record` writes local metadata and receipt refs; it does not merge,
 close, publish, or grant.
 
-## 5. Seat Packs And Stop Conditions
-
-Per-runtime integrations are explicit, never automatic: `provision-seat claude-code`,
-`provision-seat codex`, `provision-seat gemini`, `provision-seat ollama`,
-`provision-seat openrouter`.
-
-Stop when authority is unclear, validation cannot run, writes exceed the
-envelope, a secret appears, or the session is unbounded.
+## 5. Stop Conditions
 
-Going further: `etq help advanced` catalogs the advanced subsystems — the memory journal, supervision sessions, release gates, sync outbox, and webhooks.
-Docs: https://etiquekit.com/docs/ · Agents start at: https://etiquekit.com/llms.txt
+Seat packs: `provision-seat claude-code`, `provision-seat codex`, `provision-seat gemini`, `provision-seat ollama`, `provision-seat openrouter`.
+Stop when authority is unclear, validation cannot run, writes exceed the envelope, a secret appears, or the session is unbounded.

package/README.md

@@ -1,80 +1,80 @@
 # Etiquette
 
-**Govern agent-assisted engineering work with seats, evidence, and promotion
-gates.** Local-first: your repo is the ledger, receipts are the proof, and no
-server ever sees your code.
-
-When several coding agents (and humans) work the same repository, the hard
-part isn't running them — it's knowing **who did what, on whose authority,
-and what proved it worked**. Etiquette gives each participant a *seat*, each
-unit of work a *task envelope*, each completion a *receipt*, and each merge a
-*promotion gate* — recorded as plain files and git history you can audit.
-
-Docs: https://etiquekit.com/docs/ · Agents start at: https://etiquekit.com/llms.txt · Going further (memory journal, supervision, release gates): `etq help advanced`
+Etiquette is a local-first workflow and evidence CLI for teams that use coding
+agents. Each task gets a named seat, bounded write scope, validation contract,
+and receipt. Agents execute and report evidence; your human or Git gate still
+decides what becomes canonical.
 
 ## Install
 
+Prerequisites: Git `>=2.40` and Bun `>=1.3`.
+
 ```sh
-npm install -g @etiquekit/etq        # etq, etiquette, etiquette-core on PATH
-curl -fsSL https://etiquekit.com/install.sh | sh   # or: native installer
+npm install --global @etiquekit/etq
+etq --version
 ```
 
-Requires `bun >= 1.3` and `git >= 2.40`. macOS and Linux. The installer
-verifies signatures against a pinned key before executing.
+`etq` and `etiquette` are aliases for the same CLI.
 
-## Sixty seconds to a governed workspace
+## Start A Governed Task
+
+Run inside a Git repository:
 
 ```sh
-etq init --project .                  # provision folders, journal, roster
-etq doctor --project .                # readiness — green before work
-etq bootstrap local --project . \
-    --profile codex-cc-gemini --task-prefix APP
-etq setup --target auto --project .   # register your agent CLI (explicit)
-etq join --seat codex-seat --project . # profile seats: codex/cc/gemini/manager
-etq console board --project . --text  # the live task board
+etq bootstrap local --project . --task-prefix APP --ask
+etq doctor --project .
+etq whereami --project . --seat impl-seat --task APP-001
+etq join --project . --seat impl-seat
+etq pickup --project . --seat impl-seat --task APP-001 --allow-current-project --text
 ```
 
-Per-runtime seat packs: `provision-seat claude-code` · `provision-seat codex`
-· `provision-seat gemini` · `provision-seat ollama` · `provision-seat openrouter`.
+The default is one implementation seat and one bounded task. Etiquette asks
+before adding review seats and remains non-interactive in CI. A seat is a
+durable role; Claude Code, Codex, Gemini, or another runtime is its temporary
+occupant.
 
-The daily loop:
+## Daily Loop
 
-```sh
-etq pickup --seat codex-seat --task APP-001 --expect-project-id <id> --text
-# ... do the work; write the receipt at the path pickup names ...
-etq post --role implementation-return --lane APP-001 \
-    --from codex-seat --to manager-seat --project .
-etq return check --task APP-001 --seat codex-seat   # the completion gate
+```text
+orient -> pick up bounded work -> implement -> validate -> return a receipt -> promote through the existing gate
 ```
 
-(`dispatch check` gates routing BEFORE work; `return check` gates completion.)
-Every step appends to the workspace journal — an append-only event log inside
-your repo. Nothing leaves your machine: no backend, no telemetry, no account.
-
-## Concepts in one breath
+Use `whereami`, `status`, `console board`, and `return check` to inspect work.
+Read commands do not initialize directories or rewrite event streams. Explicit
+setup, bootstrap, post, and lifecycle commands own their writes.
 
-| Concept | Answers |
-| --- | --- |
-| Seat | What durable work role is acting? |
-| Task envelope | What writes, validation, and stop conditions are allowed? |
-| Session | Which bounded run produced the evidence? |
-| Receipt | What proves the work happened? |
-| Promotion gate | Where does candidate work become accepted truth? |
+## Core Records
 
-Commands initialize, check, record evidence, and project read models. They
-**never** grant, merge, close, publish, or promote — evidence, not authority.
+- **Seat:** durable work identity, independent of model or vendor.
+- **Task envelope:** allowed writes, required validation, and stop conditions.
+- **Receipt:** evidence of what ran and changed; evidence is not authority.
+- **Local ledger:** Git-readable events and packet references.
+- **Promotion gate:** the existing decision that accepts candidate work.
 
-## Verify releases
+Etiquette is not a hosted executor, transport service, portal, or replacement
+for source-control permissions. Consumers may bind packet profiles and their
+own transport; the package does not silently write a global ledger.
 
-The signing key's SHA-256 fingerprint — cross-check against the copy at
-https://etiquekit.com/docs/ before trusting a downloaded key:
+## Author A Draft Without Project State
 
+```sh
+etq post --profile ./packet-profile.yaml --draft \
+  --out /tmp/review-return.md --kind review-return --work-id APP-001 \
+  --author impl-seat --recipient review-seat \
+  --summary "Implementation complete." --evidence "Checks passed." \
+  --next-step "Review the candidate."
 ```
-917fbced1d6a82897ec3441a1d12947803ca4d42a6bc63d3412dee8bf8c3ce31
-```
 
-Then `openssl dgst -sha256 -verify <key> -signature SHA256SUMS.sig SHA256SUMS`
-and `shasum -a 256 -c SHA256SUMS`. If any step fails: stop, do not install.
+Draft mode writes only the requested output. It does not create `.etiquette`,
+emit an event, grant authority, merge, close, or publish.
+
+Optional runtime packs: `provision-seat claude-code`, `provision-seat codex`, `provision-seat gemini`, `provision-seat ollama`, `provision-seat openrouter`.
+## Documentation
+
+[Quick start](QuickStart.md) | [Concepts](docs/CONCEPTS.md) |
+[Core profile](docs/CORE_PROFILE.md) | [Seats](docs/SEAT_PROVISIONING.md) |
+[Worktrees](docs/WORKTREE_QOL.md)
 
 ## License
-Apache-2.0 (see LICENSE); distributed as compiled bundles for convenience.
+
+Apache-2.0. See [LICENSE](LICENSE) and [NOTICE](NOTICE).

package/bin/etiquette

@@ -14,12 +14,8 @@ done
 ROOT=$(CDPATH= cd -- "$(dirname -- "$SELF")/.." && pwd)
 
 if ! command -v bun >/dev/null 2>&1; then
-  echo "etiquette requires bun >= 1.3 on PATH (https://bun.sh)." >&2
-  echo "install: curl -fsSL https://bun.sh/install | bash" >&2
+  echo "etiquette requires bun on PATH" >&2
   exit 127
 fi
 
-if [ -f "$ROOT/lib/etiquette.js" ]; then
-  exec bun "$ROOT/lib/etiquette.js" "$@"
-fi
 exec bun "$ROOT/packages/control/src/cli.ts" "$@"

package/bin/etiquette-core

@@ -14,12 +14,8 @@ done
 ROOT=$(CDPATH= cd -- "$(dirname -- "$SELF")/.." && pwd)
 
 if ! command -v bun >/dev/null 2>&1; then
-  echo "etiquette-core requires bun >= 1.3 on PATH (https://bun.sh)." >&2
-  echo "install: curl -fsSL https://bun.sh/install | bash" >&2
+  echo "etiquette-core requires bun on PATH" >&2
   exit 127
 fi
 
-if [ -f "$ROOT/lib/etiquette-core.js" ]; then
-  exec bun "$ROOT/lib/etiquette-core.js" "$@"
-fi
 exec bun "$ROOT/packages/control/src/core-cli.ts" "$@"

package/docs/ARCHITECTURE.md

@@ -22,9 +22,9 @@ Execution returns evidence; it never mints authority.
 ```
 
 Execution is a substrate, not an authority layer. In Core it is the local shell,
-worktree, or runner. In Full it may be a managed execution container,
-EKS/kind sandbox, or managed runner. In every profile, execution remains
-authority-false until the promotion gate accepts evidence.
+worktree, or runner. In Full it may be a runtime cell, EKS/kind sandbox, or
+managed runner. In every profile, execution remains authority-false until the
+promotion gate accepts evidence.
 
 ## Authority
 
@@ -52,11 +52,11 @@ role occupants or composite gates and fails closed.
 
 ## Consumers
 
-Consumers may read, render, route bounded work, start bounded runners, and return
+Consumers may read, render, route bounded work, spawn bounded runners, and return
 receipts. They must not grant, close, merge, rewrite ledgers, or become the bus.
 
 Good first consumers are verification-first managed runners, local coding seats,
-context workbenches, dashboards, and MCP readers. Start remote as evidence-only.
+context workbenches, dashboards, and MCP readers. Start remote as witness-only.
 
 ## Package Boundary
 

package/docs/CODEX_CLIENT_COMPATIBILITY.md

@@ -23,7 +23,7 @@ Source: https://developers.openai.com/codex/changelog
 | Remote-runtime app-server/exec-server canaries | `0.141.0` required | Block that canary until upgraded. |
 | Plugin-scoped MCP adapter canaries | `0.141.0` required | Block that canary until upgraded. |
 | Hook/action-auth resume canaries | `0.141.0` required | Block that canary until upgraded. |
-| Usage-budget hygiene before long multi-runner windows | `0.140.0` minimum for `/usage` | Advisory only. |
+| Usage-budget hygiene before long swarms | `0.140.0` minimum for `/usage` | Advisory only. |
 
 ## Operator Check
 

package/docs/CONCEPTS.md

@@ -38,8 +38,10 @@ autonomous execution.
 ## Session
 
 A session is a bounded run inside one repo. Use one for a bug fix, feature
-slice, review, release canary, or short parallel review window; not for a
-product, quarter, or org.
+slice, review, release canary, or short swarm; not for a product, quarter, or
+org.
+
+Rebind reattaches a live session to the current ledger, task, branch, and worktree after interruption or runner/vendor change.
 
 ## Receipt
 
@@ -52,23 +54,6 @@ A ledger is the durable work record for a repo or workspace: decisions,
 receipts, state changes, and refs. Raw execution chatter belongs in session
 runbooks and scratch space.
 
-### Durable Record vs Query Index
-
-Two surfaces share the ledger name. They are different systems:
-
-| Surface | Path | When it populates |
-| --- | --- | --- |
-| Durable record | `docs/work/ledger/LEDGER.md` | Automatically, as the workflow appends event lines |
-| Query index | `.etiquette/state/ledger/index.db` | Only when you run `etiquette ledger index` |
-
-The durable record is canonical and append-only. The query index is a
-generated, regenerable SQLite cache read by `ledger search` and `ledger show`.
-It ingests typed `schema=ledger-entry.v0*` lines and scanned documents, not
-routine workflow event lines. `ledger_entries: 0` after a full workflow cycle
-means no typed entries exist yet; the durable record is intact. Deleting the
-index loses nothing. See
-`docs/contracts/ledger-entry/ledger-query-cli.v0.1.md`.
-
 ## Promotion Gate
 
 The promotion gate is where candidate work becomes accepted truth.
@@ -99,8 +84,7 @@ runner only through an explicit lease.
 
 A child lease must be a strict subset of the parent lease. The subset covers
 shorter or equal TTL, narrower or equal authority scope, subset write paths,
-subset tools, inherited prohibitions, reduced child-runner budget, and reduced
-depth.
+subset tools, inherited prohibitions, reduced spawn budget, and reduced depth.
 
 Children return to their immediate parent. The parent synthesizes one upstream
 receipt and remains accountable for child cleanup. A child or headless node is
@@ -109,7 +93,7 @@ not a durable seat unless it is separately enrolled and passes readiness.
 ## Exec
 
 Exec is any runtime that does work: a local shell, Codex, Claude Code, Gemini,
-Ollama, a script, a container, or a managed execution container.
+Ollama, a script, a container, or a remote runtime cell.
 
 Exec may run, observe, retry safe work, and return evidence. Exec must not
 grant, merge, close, promote, or mutate canonical truth.
@@ -131,7 +115,7 @@ External tools keep their native jobs: chat is conversation, planning tools are
 planning, code hosts are review, observability is incident evidence, and
 identity systems are identity.
 
-Etiquette is the accountability journal. External "Done" is not acceptance.
+Etiquette is the accountability spine. External "Done" is not acceptance.
 Authentication is not authorization.
 
 ## Short Rules

package/docs/CONCEPT_STATUS.md

@@ -0,0 +1,66 @@
+# Concept Status Matrix
+
+Etiquette uses a few strong workflow concepts. Some are core behavior today,
+some belong to the optional secure plane, and some are still operating patterns
+that need a concrete consumer before they become default workflow.
+
+Use this page when writing portal copy, onboarding material, release notes, or
+manager runbooks. Do not promote a concept beyond the status shown here.
+
+## Edition Boundary
+
+| Surface | Purpose | Authority Posture |
+| --- | --- | --- |
+| Etiquette Core | Repo-local coordination, task envelopes, receipts, allowed writes, read models, manuals, and canaries. | Transparent by default; authority comes from tracked task/grant records and receipts. |
+| Etiquette Secure | Restricted-seat admission, external assurance claims, revocation, policy state, and optional tightening reactor. | Tightens standing and eligibility; it must not grant workflow authority by itself. |
+| Hosted/portal plane | Setup passes, workspace visibility, onboarding, board/read-model display, and operational observability. | Portal RBAC authorizes portal operations only. Workflow authority stays local and grant-backed. |
+
+## Concept Matrix
+
+| Concept | Core Status | Secure Status | Portal Surface | Caveat |
+| --- | --- | --- | --- | --- |
+| Ledger | Shipped. Repo-local task records, events, and receipts carry durable workflow truth. | May receive signed or protected replication later. | Board and console render ledger-derived read models. | Git-backed truth is durable and auditable; call it cryptographic only when signing/protected append-only is actually configured. |
+| Receipts | Shipped. Work returns must cite changed files, validation, blockers, and next owner. | May include action authorization stamps and external verifier receipts. | Evidence drawers and manager views point to receipts. | A receipt proves evidence; it does not grant, merge, close, or promote by itself. |
+| Seats and agents | Shipped. A seat is a stable responsibility; an occupant/runtime can change. Owner cards derive accountability, diet, boundaries, review cadence, and failure modes from source contracts plus live readiness. | Secure posture is parked; seats use local readiness and explicit task routing. | Roster and owner cards show lifecycle, readiness, ownership, and posture. | Model cards, owner cards, and roster posture help routing but do not authorize work or transfer ownership. |
+| Task envelopes | Shipped. Tasks declare owner, mode, allowed writes, forbidden writes, validation, stop conditions, and receipt expectations. | Secure admission is parked; task routing remains explicit. | Manager manuals and pickup surfaces show the envelope. | Allowed writes are a cooperative boundary unless paired with OS/container enforcement or audit gates. |
+| Rubrics and validation | Shipped as acceptance criteria and conformance gates. | Can be bound to restricted workflows and verifier receipts. | Manager/operator docs list required validation and stop conditions. | Do not claim every runtime is hard-blocked from returning unless the specific flow enforces that gate. |
+| Authorization | Shipped as grant-backed workflow discipline: authentication seats an actor; authorization gates consequential action. | Secure posture is parked; grant leases, kill-switch state, and action stamps remain the admission-time authority model. | Hosted pass docs and workspace authority contracts describe the boundary. | A verified occupant has standing, not blanket authority. Grants are effective only while standing is current. |
+| Portal / management console | Core read model, docs site, screenshots, and read-only `console serve` are shipped. | Secure portal may manage policy state and revocation signals. | Console and board are read-only by default. | Portal RBAC is not workflow authority. Browser actions remain out of scope in Core. |
+| Distribution and plugins | Core CLI, docs, templates, MCP resources/prompts, and outbox-backed proposal staging are portable. | Secure can ship as an optional add-on. | Codex and Claude Code plugins may launch workflows and portal views. | Plugins are convenience packaging, not authority. MCP proposal tools must not mutate the ledger directly. |
+| Remote execution | Supported as evidence-first design. | Secure runtimes may require admission, revocation, and verifier identity before execution. Org-remote workspaces use session outboxes, sharded drains, candidate imports, and authority promotion gates. | Manager docs should treat remote receipts as evidence. | Start remote as witness, not worker. Remote receipts and drain imports do not authorize promotion. |
+| Managed-agent parity | Parity map exists for agents, environments, sessions, events, tools, MCP, memory, outcomes, and scheduling. | Secure runtime admission is parked. | Docs site and portal docs may expose the map. | Compatibility is not dependency. The runner executes; Etiquette governs and records. |
+| Architecture boundary | Core, runtime, harness, adapter, and reactor roles are documented and import-boundary tested. | Secure adds admission policy without forking doctrine. | Hosted consumes projected views without becoming authority. | New reverse imports are architectural changes, not convenience edits. |
+| Memory | Shipped as cited context, filesystem-shaped candidate stores, SQLite FTS recall, and `memory status` capability reporting. Evidence consolidation/rollup is the memory compaction lifecycle; it is not doctrine marination. | Secure deployments may restrict what crosses org/workspace boundaries. | Docs may surface references, summaries, archive pointers, and shipped/reserved memory status. | Memory proposes; ledger authorizes. Do not claim full semantic/vector memory parity until the adapter ships. Do not rewrite shared truth through background consolidation. |
+| Marination | Operating pattern. Use for doctrine sabbaticals: scheduled fresh-attention review of rules, errata, and proposed revisions. | Can be run under Secure as an advisory process with cited evidence. | Not yet a default portal workflow. | Deltas only. It produces proposals, not silent lane mutations. |
+| Sabbaticals / parking | Partially reflected as `park`, `held`, and deferred dispositions. | Secure deployments may freeze standing or grants while work is parked. | Manager cadence can show parked/held work. | Do not promise automatic stash/cleanup unless the workspace implements that runbook. |
+| Tightening reactor | Not part of default Core. | Optional off-by-default listener that writes only fail-closed signals such as revocation or kill-switch state. | Secure operations may show reactor health. | It may tighten, never loosen. If it stops, local admission still fails or proceeds from last known policy according to the configured gate. |
+
+## Primitive Loop
+
+Core records, validates, gates, and dispatches. Full remembers, consolidates,
+marinates, and projects. Execution is not the gate: Core execution is the local
+shell/worktree, Full execution is a runtime cell or managed runner, and both
+remain authority-false until the promotion gate accepts evidence.
+
+| Layer | Core | Full |
+| --- | --- | --- |
+| Record | identity, seats, task envelopes, session runbooks, ledger, receipts | memory stores, recall capsules, org/workspace projections |
+| Reflect | rubrics, local validation, reconciliation by review | consolidation rollups, marination, drift and failure trend review |
+| Gate | human/Git promotion gate over receipts and grants | same gate, enriched by secure admission and policy checks |
+| Execute | local shell, local worktree, local runner | runtime cells, EKS/kind sandboxes, managed runners |
+| Act | dispatch, receipt return, next-owner routing | hosted portal views, observability, adapter projections |
+
+## Writing Rule
+
+Use shipped language for shipped behavior, design language for parked behavior,
+and edition language for Secure behavior:
+
+```text
+Core records, validates, gates, and dispatches.
+Full remembers, consolidates, marinates, and projects.
+Secure admits and revokes restricted standing.
+Portals display and coordinate.
+Grants authorize consequential actions.
+Receipts prove what happened.
+Execution returns evidence; it never mints authority.
+```

package/docs/CORE_PROFILE.md

@@ -16,7 +16,7 @@ Core excludes by default:
 
 - hosted runtime and EKS provisioning;
 - MCP server;
-- Linear adapter;
+- external planning adapter;
 - memory-store lifecycle and drains;
 - agent-plane profiles;
 - console/site;
@@ -37,8 +37,7 @@ Core records, validates, gates, and dispatches:
 
 Full remembers, consolidates, marinates, and projects. Memory stores,
 consolidation rollups, marination modules, hosted portals, secure screening,
-managed execution containers, and sharded drains belong there unless explicitly
-enabled.
+remote runtime cells, and sharded drains belong there unless explicitly enabled.
 
 Use:
 
@@ -64,8 +63,7 @@ The Core promotion path is:
 5. The ledger records the promoted result.
 
 At Core scale, Git is the promotion mechanism. Drains, sharded import, hosted
-planes, and managed execution containers belong to the Full profile unless
-explicitly enabled.
+planes, and runtime cells belong to the Full profile unless explicitly enabled.
 
 Core commands may advise, check, and record evidence. They do not authorize
 work, attach grants, merge, close lanes, or promote candidates without the

package/docs/LANE_PROVISIONING.md

@@ -16,8 +16,8 @@ lane: APP-001-domain-foundation
 task_id: APP-001
 repo: github.com/org/app
 project_ref: .
-current_owner: codex-seat
-review_owner: cc-seat
+current_owner: impl-seat
+review_owner: review-seat
 mode: product-implementation | read-only-audit | docs-only
 startup_docs:
   - AGENTS.md
@@ -90,6 +90,11 @@ etiquette pickup --project . --seat <seat> --task <task> --text
 Then read only the startup docs named by the bulletin. Do not scrape old chat
 or a global bus to infer project state.
 
+If the seat is resuming, changing role, changing runner/model/vendor, or moving
+between worktrees, perform seat rebind before `join`/`pickup`: verify the live
+project, task, branch, worktree, routing surface, and evidence surface from the
+ledger. Rebind is context proof only; it is not readiness or authority.
+
 Inside a session, the agent should confirm:
 
 - seat id and operator principal;

package/docs/README.md

@@ -9,17 +9,17 @@ For private manager-to-developer rollout, use
 
 References:
 
+- [CONCEPT_STATUS.md](CONCEPT_STATUS.md)
 - [CODEX_CLIENT_COMPATIBILITY.md](CODEX_CLIENT_COMPATIBILITY.md)
 - [RELEASE_SURFACE_AUDIT.md](RELEASE_SURFACE_AUDIT.md)
-- [INTEGRATION_UI.md](INTEGRATION_UI.md) — building a UI/consumer over the event log and packets
 
 Source checkouts also keep hosted parity, portal, managed-runtime parity, and root kernel notes for
 maintainers. They are not part of the local devkit tarball.
 
 Integration profile:
-Slack/Teams are conversation, Jira/Linear are planning, GitHub/GitLab are code
-review, Sentry/Datadog/OpenTelemetry are incident evidence, and SSO/SCIM/OIDC
-are identity. Etiquette is the accountability journal: chat is not source of
+Conversation systems carry discussion, planning systems track backlog, code review
+systems review changes, incident systems carry evidence, and identity systems
+authenticate users. Etiquette is the accountability spine: chat is not source of
 truth, external Done is not acceptance, and authentication is not authorization.
 
 Current release posture: Core is the default local-first product, Exec is