@etiquekit/etq 1.0.13 → 1.0.15

package/AGENTS.md

@@ -1,30 +1,37 @@
 # Etiquette Agent Guide
 
-This repo is the Etiquette source repo. Keep the all-developer onboarding path small.
+## If you installed this package
 
-## Default Rule
+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:
 
-New engineers should start with:
+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.
 
-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.
+Commands record evidence; they never grant, merge, close, publish, or
+promote.
 
-## Ownership
+## If you are working on the Etiquette source repo
 
-This repo owns:
+Keep the all-developer onboarding path small. New engineers start with:
 
-- 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.
+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)
 
-This repo does not own product repos, product lane state, secrets, hosted services, or runtime vendor setup.
+Do not send new seats through internal history, old coordination lanes, or
+maintainer-only notes.
 
-## Editing Rule
+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.
 
-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,3 +1,4 @@
+
                                  Apache License
                            Version 2.0, January 2004
                         http://www.apache.org/licenses/
@@ -137,8 +138,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,7 +1,5 @@
-Etiquette
-Copyright (c) 2026 Leepick Inc, US.
+Etiquette (etq)
+Copyright 2026 The Etiquekit Authors
 
-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.
+Local-first, git-backed agent-workflow governance toolkit.
+Distributed under the Apache License, Version 2.0.

package/QuickStart.md

@@ -1,51 +1,53 @@
 # Quick Start
 
-Get from zero to a governed working project in about two minutes.
+For a clean repo, a team canary, or a new Etiquette developer.
 
-Prereqs: Git, Node 18+ (for npm install) or Bun `>=1.3.0`.
+Prereqs: `git >= 2.40` and `bun >= 1.3` on `PATH`. macOS and Linux.
 
 ## 1. Get The CLI
 
-The published package:
-
 ```sh
-npm install -g @etiquekit/etq
-# or project-local: npm install @etiquekit/etq && alias etq=./node_modules/.bin/etq
-etq --help
+npm install -g @etiquekit/etq                      # local exec plane over @etiquekit/core
+curl -fsSL https://etiquekit.com/install.sh | sh   # or: native installer
 ```
 
-Bootstrap a project and run your first cycle:
+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 using the docs at
+`https://etiquekit.com/docs/`, then:
 
 ```sh
-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
+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"
 ```
 
-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=${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
+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
 ```
 
 `bootstrap local` creates repo-local state, seats, task envelopes, pickup docs,
 events, and runbooks. It does not grant, publish, merge, close, or promote.
-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.
+`handoff` is a read-only guide: it prints install, bootstrap, and pickup
+commands without changing anything.
 
 ## 3. Orient The Live Seat
 
@@ -53,21 +55,24 @@ Run `whereami` whenever a developer or agent resumes, changes directories, or
 inherits a worktree:
 
 ```sh
-"$ETQ" whereami --project "$PWD" --seat impl-seat --task APP-001
-"$ETQ" pickup --project "$PWD" --seat impl-seat --task APP-001 --allow-current-project --text
+etq whereami --project "$PWD" --seat codex-seat --task APP-001
+etq pickup --project "$PWD" --seat codex-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
 
-Create checkable dispatch examples, then run the generated command:
+Completion gate: write the receipt at the path `pickup` names, 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:
 
 ```sh
-"$ETQ" dispatch scaffold --project "$PWD" --task-id APP-001 --seat impl-seat
-"$ETQ" dispatch check --project "$PWD" \
+etq dispatch scaffold --project "$PWD" --task-id APP-001 --seat codex-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 \
@@ -77,7 +82,13 @@ Create checkable dispatch examples, then run the generated command:
 `dispatch record` writes local metadata and receipt refs; it does not merge,
 close, publish, or grant.
 
-## 5. Stop Conditions
+## 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.
 
-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.
+Docs: https://etiquekit.com/docs/ · Agents start at: https://etiquekit.com/llms.txt

package/README.md

@@ -1,78 +1,80 @@
 # Etiquette
 
-Etiquette is a governance and evidence CLI for agent-assisted engineering work.
+**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.
 
-It answers the questions that matter when agents help write code: who acted,
-under which seat, inside what scope, with what evidence, and who accepted the
-result.
+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.
 
-Default loop: `setup -> handoff -> bootstrap local -> whereami -> doctor -> join -> pickup -> receipt -> promotion gate`.
+Docs: https://etiquekit.com/docs/ · Agents start at: https://etiquekit.com/llms.txt
 
-Execution runtimes are optional; they return evidence and do not mint authority.
+## Package split
 
-## Start
+Etiquette is now shipped as a small open core plus execution planes:
 
-Prereqs: Git and Bun `>=1.3.0`; the CLI shims require `bun` on `PATH`.
-For a clean repo or a new seat, read [QuickStart.md](QuickStart.md). For private team rollout, use [docs/TEAM_HANDOFF.md](docs/TEAM_HANDOFF.md), then:
+| Package / repo | Role |
+| --- | --- |
+| [`@etiquekit/core`](https://www.npmjs.com/package/@etiquekit/core) | Public open governance contract: schemas, pure state machines, authority/refusal rules, plane profiles, and conformance. |
+| [`@etiquekit/etq`](https://www.npmjs.com/package/@etiquekit/etq) | Thin local execution plane: CLI, git journal, worktree/session ergonomics, local evidence return, and developer-facing docs. It consumes `@etiquekit/core`. |
+| `remote-etq` | Private managed execution plane: API, sequencer, workers, tenancy, and hard-stop enforcement. |
 
-```sh
-./bin/etiquette setup --target codex --project /tmp/etiquette-start
-./bin/etiquette handoff --project /tmp/etiquette-start --task-prefix APP
-./bin/etiquette bootstrap local --project /tmp/etiquette-start --task-prefix APP
-./bin/etiquette whereami --project /tmp/etiquette-start --seat impl-seat --task APP-001
-./bin/etiquette doctor --project /tmp/etiquette-start
-./bin/etiquette status --project /tmp/etiquette-start
-./bin/etiquette join --project /tmp/etiquette-start --seat impl-seat
-./bin/etiquette pickup --project /tmp/etiquette-start --seat impl-seat --task APP-001 --allow-current-project --text
-./bin/etiquette console board --project /tmp/etiquette-start --text
-```
-
-`handoff` is a read-only guide: it prints install, bootstrap, and pickup commands without installing, bootstrapping, pushing, closing, or granting.
-
-`bootstrap local` creates repo-local seats, task envelopes, bounded runbooks,
-local packet events, and pickup docs without global bus writes or authority.
-`whereami` is the context readback: runner resume restores conversation
-history; `whereami` tells the seat which project, worktree, task, and runbook it
-is actually operating in.
-
-Use repo-local commands for now. The hosted public installer is parked.
+The public source homes are linked from npm package metadata and
+https://etiquekit.com/docs/. The open reference is the core contract plus
+sample/conformance surfaces. `etq` is the production local plane that dogfoods
+that contract.
 
-## Core Concepts
+## Install
 
-- Seat: durable work identity; the occupant or model can change.
-- Task envelope: scope, allowed writes, validation, and stop conditions.
-- Receipt: evidence of what happened; it proves but does not authorize.
-- Promotion gate: the human/Git gate where candidate work becomes truth.
-- Ledger: durable local record of sessions, receipts, and decisions.
+```sh
+npm install -g @etiquekit/etq        # local exec plane; installs @etiquekit/core
+curl -fsSL https://etiquekit.com/install.sh | sh   # or: native installer
+```
 
-Read next: [docs/README.md](docs/README.md), [docs/CONCEPTS.md](docs/CONCEPTS.md), [docs/CORE_PROFILE.md](docs/CORE_PROFILE.md), [docs/SEAT_PROVISIONING.md](docs/SEAT_PROVISIONING.md), and [docs/WORKTREE_QOL.md](docs/WORKTREE_QOL.md).
+Requires `bun >= 1.3` and `git >= 2.40`. macOS and Linux. The installer
+verifies signatures against a pinned key before executing.
 
-Provision runtime seats only after assignment:
+## Sixty seconds to a governed workspace
 
 ```sh
-sh templates/seat-packs-v0/bin/provision-seat codex /tmp/dev-codex-seat
-sh templates/seat-packs-v0/bin/provision-seat claude-code /tmp/dev-claude-code-seat
-sh templates/seat-packs-v0/bin/provision-seat gemini /tmp/dev-gemini-seat
-sh templates/seat-packs-v0/bin/provision-seat ollama /tmp/dev-ollama-seat
-sh templates/seat-packs-v0/bin/provision-seat openrouter /tmp/dev-openrouter-seat
+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
 ```
 
-## Validate
+Per-runtime seat packs: `provision-seat claude-code` · `provision-seat codex`
+· `provision-seat gemini` · `provision-seat ollama` · `provision-seat openrouter`.
+
+The daily loop:
 
 ```sh
-npm run release:scan
-bun test
-npm run typecheck
+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
 ```
 
-## Release Status
+(`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.
 
-```yaml
-default_surface: templates/etiquette-vanilla-v0
-optional_runtime_surface: templates/seat-packs-v0
-public_installer: held
-```
+## Concepts in one breath
 
-## License
+| 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? |
 
-Apache-2.0 — see [LICENSE](./LICENSE) and [NOTICE](./NOTICE).
+Commands initialize, check, record evidence, and project read models. They
+**never** grant, merge, close, publish, or promote — evidence, not authority.

package/bin/etiquette

@@ -14,8 +14,12 @@ done
 ROOT=$(CDPATH= cd -- "$(dirname -- "$SELF")/.." && pwd)
 
 if ! command -v bun >/dev/null 2>&1; then
-  echo "etiquette requires bun on PATH" >&2
+  echo "etiquette requires bun >= 1.3 on PATH (https://bun.sh)." >&2
+  echo "install: curl -fsSL https://bun.sh/install | bash" >&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,8 +14,12 @@ done
 ROOT=$(CDPATH= cd -- "$(dirname -- "$SELF")/.." && pwd)
 
 if ! command -v bun >/dev/null 2>&1; then
-  echo "etiquette-core requires bun on PATH" >&2
+  echo "etiquette-core requires bun >= 1.3 on PATH (https://bun.sh)." >&2
+  echo "install: curl -fsSL https://bun.sh/install | bash" >&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

@@ -8,16 +8,16 @@ vendor wrapper. Those can all consume Etiquette, but they do not own its truth.
 ## Layers
 
 ```text
-Core          contracts, schemas, validators, ledgers, receipts, audit
-Local runtime repo-local CLI, event log, task packets, memory search
-Harness       teammate UX, context presets, skills, dashboards, canvases
-Adapters      Codex, Claude Code, Gemini, managed runners, GitHub, MCP
-Reactors      optional tighten-only listeners for revocation and sync
+@etiquekit/core   public contracts, schemas, validators, refusal rules
+@etiquekit/etq    thin local exec plane: CLI, git journal, worktrees, receipts
+remote-etq        private managed exec plane: API, sequencer, workers, tenancy
+adapters          Codex, Claude Code, Gemini, GitHub, MCP, managed runners
+reactors          optional tighten-only listeners for revocation and sync
 ```
 
 ```text
-Core records, validates, gates, and dispatches.
-Full remembers, consolidates, marinates, and projects.
+Core defines the contract.
+Local and remote planes execute against it.
 Execution returns evidence; it never mints authority.
 ```
 
@@ -61,24 +61,21 @@ context workbenches, dashboards, and MCP readers. Start remote as witness-only.
 ## Package Boundary
 
 ```text
-packages/protocol  kernel contracts; no runtime or adapter imports
-packages/control   local runtime and public CLI; may use protocol only
-legacy bridges     dbt-core and adapter-* stay source-only until a consumer
-apps/*             UX surfaces; consume core through public commands or APIs
+@etiquekit/core  open package and public repo: pure governance contract
+@etiquekit/etq   npm package and public home: thin local execution plane
+remote-etq       private repo/service: managed execution plane
 ```
 
-Known bridge exceptions must stay named in conformance tests until removed.
-Adding a reverse import is an architectural change. The public 0.2.x package ships only
-`control`, `protocol`, docs, templates, and scripts; legacy DBT and old slice
-adapters stay source-only until a consumer exists.
+The local plane may depend on core. Core must never depend on the local or
+remote planes. Adding a reverse import is an architectural change.
 
-For 0.2.x, only two product boundaries are hard enforcement surfaces:
+The hard enforcement surfaces are:
 
-- Core excludes Full command families and optional runtime, hosted, memory,
-  console, sync, adapter, MCP, release, and remote provisioning surfaces.
-- Exec remains authority-false: it may run, observe, verify, and return
+- Core excludes local CLI, hosted, managed, runtime, integration, MCP, and
+  deployment surfaces.
+- Every exec plane remains authority-false: it may run, observe, verify, and return
   evidence, but it cannot grant, close, merge, promote, mutate canonical truth,
-  or mint access outside Core grants and envelopes.
+  or mint access outside grants and envelopes.
 
 Exec evidence is boundary evidence, not process surveillance. Runners return scope, write
 boundaries, candidates, validation, failures, refusals, and stop conditions; internal retries need

package/docs/CONCEPTS.md

@@ -10,8 +10,10 @@ runtime.
 seat -> task envelope -> session -> execution -> receipt -> promotion gate
 ```
 
-Core records, validates, gates, and dispatches. Exec runs and returns evidence.
-Full remembers, consolidates, marinates, and projects.
+`@etiquekit/core` defines the public contract: schemas, state machines,
+authority/refusal rules, plane profiles, and conformance. `@etiquekit/etq` is
+the thin local execution plane that consumes that contract, runs local workflow
+commands, and returns evidence. Managed or hosted planes are separate consumers.
 
 ## Seat
 
@@ -41,8 +43,6 @@ A session is a bounded run inside one repo. Use one for a bug fix, feature
 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
 
 A receipt proves what happened: changed files, validation, runbook refs,
@@ -115,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 spine. External "Done" is not acceptance.
+Etiquette is the accountability journal. External "Done" is not acceptance.
 Authentication is not authorization.
 
 ## Short Rules

package/docs/CORE_PROFILE.md

@@ -1,7 +1,15 @@
 # Etiquette Core Profile
 
-Etiquette Core is the bare-bones governance flavor for senior engineers who
-want the original promise without the managed runtime surface.
+This file describes the `etiquette-core` CLI profile inside `@etiquekit/etq`.
+It is not the same thing as the public npm package `@etiquekit/core`.
+
+`@etiquekit/core` is the open governance contract: schemas, pure state machines,
+authority/refusal rules, plane profiles, and conformance. `@etiquekit/etq` is
+the thin local execution plane that consumes it.
+
+The `etiquette-core` CLI profile is the bare-bones local governance flavor for
+senior engineers who want the original promise without the managed runtime
+surface.
 
 Core includes:
 
@@ -16,7 +24,7 @@ Core excludes by default:
 
 - hosted runtime and EKS provisioning;
 - MCP server;
-- external planning adapter;
+- Linear adapter;
 - memory-store lifecycle and drains;
 - agent-plane profiles;
 - console/site;
@@ -25,7 +33,7 @@ Core excludes by default:
 
 ## Primitive Map
 
-Core records, validates, gates, and dispatches:
+The local core profile records, validates, gates, and dispatches:
 
 | Layer | Core primitive |
 | --- | --- |
@@ -35,9 +43,9 @@ Core records, validates, gates, and dispatches:
 | Execute | local shell, local worktree, local runner; authority-false |
 | Act | dispatch advice, receipt return, next-owner routing |
 
-Full remembers, consolidates, marinates, and projects. Memory stores,
-consolidation rollups, marination modules, hosted portals, secure screening,
-remote runtime cells, and sharded drains belong there unless explicitly enabled.
+Higher-level planes may consolidate and project. Memory stores, consolidation
+rollups, hosted portals, secure screening, remote runtime cells, and sharded
+drains belong outside this profile unless explicitly enabled.
 
 Use:
 

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: impl-seat
-review_owner: review-seat
+current_owner: codex-seat
+review_owner: cc-seat
 mode: product-implementation | read-only-audit | docs-only
 startup_docs:
   - AGENTS.md
@@ -90,11 +90,6 @@ 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

@@ -1,5 +1,14 @@
 # Etiquette Docs
 
+Package map:
+
+- [`@etiquekit/core`](https://www.npmjs.com/package/@etiquekit/core) is the
+  public open contract; source is linked from npm metadata and the website.
+- [`@etiquekit/etq`](https://www.npmjs.com/package/@etiquekit/etq) is the thin
+  local exec plane. It consumes `@etiquekit/core` and supplies CLI, local
+  journal, worktree/session ergonomics, and evidence return.
+- `remote-etq` is the private managed execution plane.
+
 Start with [CONCEPTS.md](CONCEPTS.md), [CORE_PROFILE.md](CORE_PROFILE.md),
 [SEAT_PROVISIONING.md](SEAT_PROVISIONING.md), [SEAT_DISCIPLINE.md](SEAT_DISCIPLINE.md),
 [LANE_PROVISIONING.md](LANE_PROVISIONING.md), [WORKTREE_QOL.md](WORKTREE_QOL.md),
@@ -9,21 +18,13 @@ 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)
 
-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:
-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
+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
 truth, external Done is not acceptance, and authentication is not authorization.
-
-Current release posture: Core is the default local-first product, Exec is
-authority-false and swappable, Full/hosted surfaces are optional scale layers,
-and public hosted distribution is parked until organizational approval.
-
-Maintainer history and prior workflow notes are not part of new-seat onboarding.
+Current posture: `@etiquekit/core` is open, `@etiquekit/etq` is the local exec
+plane that dogfoods it, and remote/hosted execution stays private.