@etiquekit/etq 1.0.5 → 1.0.7

package/docs/README.md

@@ -9,7 +9,6 @@ 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)
 

package/docs/RELEASE_SURFACE_AUDIT.md

@@ -34,7 +34,6 @@ docs_default:
   - docs/ARCHITECTURE.md
   - docs/CODEX_CLIENT_COMPATIBILITY.md
   - docs/CONCEPTS.md
-  - docs/CONCEPT_STATUS.md
   - docs/CORE_PROFILE.md
   - docs/LANE_PROVISIONING.md
   - docs/SEAT_DISCIPLINE.md

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@etiquekit/etq",
-  "version": "1.0.5",
+  "version": "1.0.7",
   "description": "Governance and evidence CLI for AI-assisted engineering seats.",
   "private": false,
   "type": "module",
@@ -44,5 +44,12 @@
     "yaml": "2.8.3",
     "zod": "4.3.6"
   },
-  "homepage": "https://etiquekit.com"
+  "homepage": "https://etiquekit.com",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/leepickdev/etq.git"
+  },
+  "bugs": {
+    "url": "https://github.com/leepickdev/etq/issues"
+  }
 }

package/templates/seat-packs-v0/README.md

@@ -62,7 +62,7 @@ project head-start surfaces before pickup:
 - `docs/work/manuals/SEAT_OPERATING_MANUAL.md`
 - `docs/work/cookbooks/ADD_A_LANE.md` when routing work
 
-Use `$etiquette-seat-lifecycle` before pickup after stale context, resume,
+Re-orient with `etiquette whereami` before pickup after stale context, resume,
 runner/model/profile swaps, or workflow migration.
 
 ## Validate Catalog

package/templates/seat-packs-v0/source/claude-code-seat/README.md

@@ -14,6 +14,6 @@ Before pickup in the target project, read:
 4. `docs/work/manuals/SEAT_OPERATING_MANUAL.md`
 5. `docs/work/cookbooks/ADD_A_LANE.md` when routing new work
 
-Use `$etiquette-seat-lifecycle` before pickup after stale context, resume,
+Re-orient with `etiquette whereami` before pickup after stale context, resume,
 runner/model/profile swaps, or workflow migration. Hooks and readiness are
 evidence only; the task envelope is the work authority.

package/templates/seat-packs-v0/source/codex-seat/README.md

@@ -14,7 +14,7 @@ Before pickup in the target project, read:
 4. `docs/work/manuals/SEAT_OPERATING_MANUAL.md`
 5. `docs/work/cookbooks/ADD_A_LANE.md` when routing new work
 
-Use `$etiquette-seat-lifecycle` before pickup after stale context, resume,
+Re-orient with `etiquette whereami` before pickup after stale context, resume,
 runner/model/profile swaps, or workflow migration. Hooks and readiness are
 evidence only; the task envelope is the work authority.
 

package/templates/seat-packs-v0/source/gemini-seat/README.md

@@ -14,6 +14,6 @@ Before pickup in the target project, read:
 4. `docs/work/manuals/SEAT_OPERATING_MANUAL.md`
 5. `docs/work/cookbooks/ADD_A_LANE.md` when routing new work
 
-Use `$etiquette-seat-lifecycle` before pickup after stale context, resume,
+Re-orient with `etiquette whereami` before pickup after stale context, resume,
 runner/model/profile swaps, or workflow migration. Hooks and readiness are
 evidence only; the task envelope is the work authority.

package/templates/seat-packs-v0/source/ollama-seat/README.md

@@ -14,6 +14,6 @@ Before pickup in the target project, read:
 4. `docs/work/manuals/SEAT_OPERATING_MANUAL.md`
 5. `docs/work/cookbooks/ADD_A_LANE.md` when routing new work
 
-Use `$etiquette-seat-lifecycle` before pickup after stale context, resume,
+Re-orient with `etiquette whereami` before pickup after stale context, resume,
 runner/model/profile swaps, or workflow migration. Hooks and readiness are
 evidence only; the task envelope is the work authority.

package/templates/seat-packs-v0/source/openrouter-seat/README.md

@@ -14,6 +14,6 @@ Before pickup in the target project, read:
 4. `docs/work/manuals/SEAT_OPERATING_MANUAL.md`
 5. `docs/work/cookbooks/ADD_A_LANE.md` when routing new work
 
-Use `$etiquette-seat-lifecycle` before pickup after stale context, resume,
+Re-orient with `etiquette whereami` before pickup after stale context, resume,
 runner/model/profile swaps, or workflow migration. Hooks and readiness are
 evidence only; the task envelope is the work authority.

package/docs/CONCEPT_STATUS.md

@@ -1,67 +0,0 @@
-# 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. | Restricted seats may require assurance claims before admission. | 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 can refuse restricted seats before task execution. | 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. | Access assurance, grant leases, kill-switch state, and action stamps compose at admission time. | 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. |
-| Access screening | Not required for open Core. | Optional Secure surface using derived claims from providers such as Persona, Scandit, and Supabase. | Restricted-seat policy docs and secure onboarding should expose pass/fail status, not raw identity data. | Raw documents, scans, full document numbers, ethnicity, and provider secrets do not belong in Git. |
-| 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 can add restricted runtime admission and revocation. | 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.
-```