@etiquekit/etq 1.0.1 → 1.0.5

package/docs/CONCEPTS.md

@@ -113,7 +113,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
@@ -126,3 +126,4 @@ Portals display and coordinate.
 Integrations project refs.
 Execution returns evidence; it never mints authority.
 ```
+

package/docs/README.md

@@ -19,7 +19,7 @@ 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 spine: chat is not source of
+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

package/docs/SEAT_DISCIPLINE.md

@@ -1,19 +1,79 @@
 # Seat Discipline
 
 Seat discipline keeps agent work useful, attributable, and portable across
-runtimes.
+runtimes. Mechanics say what to do; discipline says when to distrust yourself.
+It is organized by moment of need, not by topic.
+
+## On Wake
+
+- Orient before acting: `whereami`, then the task envelope, then the runbook.
+- Read tiered: status line first, then the exact entry, then the full
+  artifact. Never bulk-load directories for "context" — load the specific
+  receipt you were pointed to.
+
+## Before Claiming Anything
+
+- Verify at claim time: re-read the source at the moment you assert it,
+  never from memory of an earlier read. A cited manifest or spec is read in
+  the same act as the claim.
+- Check the live tip, not your notes: logs and board notes lag integrations.
+- When another seat or a human holds the ground truth, ask — do not
+  solo-reconstruct their state.
+
+## Before Writing
+
+- Read the machine fields, not the title: the envelope's mode and allowed
+  writes decide what a task may do; prose is not authority.
+- Search the exact target surface before classifying work as new — most
+  "add X" tasks are "finish the X that half-exists."
+- One writer per canonical mutation. Design in parallel; mutate single-file.
+
+## While Working
+
+- Technical register on the record: schemas, fields, commands, refs.
+  Metaphor and personality stay in chat; the record is for the next reader.
+- No person or vendor names in artifacts. Attribute external material at the
+  moment of incorporation, with license.
+- One meaningful update per note, reader-resolvable without tooling. Write
+  runbook notes, not raw transcript dumps.
+
+## Before Returning
+
+- Receipt first: outcome, changed files, validation command and result,
+  blockers, next owner. No raw logs — cite paths to them.
+- Run validation before returning the receipt. A red validation is reported
+  red; "done" without proof is a defect, not a return.
+- If your change altered a source shape, refresh its recorded evidence in
+  the same commit.
+- Run post-commit hygiene (`git diff --check HEAD~..HEAD`) — pre-commit
+  checks miss freshly added files.
+
+## On Review
+
+- Verify the shipped artifact, not the branch state you remember.
+- Reviews return evidence, never authority: confirm, counter, or advise.
+  A reviewer packet does not mutate the lane it reviews.
+- Accepted review is different from integrated work.
+- Proposals carry their own counter-arguments and open questions — invite
+  the pressure test.
+
+## At Authority Edges
+
+- Stop when authority is unclear, validation cannot run, writes would exceed
+  the envelope, a secret appears, or the session is unbounded.
+- Never claim work was authorized without decision language from the
+  authority holder. Enthusiasm is not routing.
+- Risk-tier your own gates: proceed on cheap-and-reversible; insist on a
+  real decision for irreversible, authority-changing, or spend actions.
+  Gating everything trains the rubber-stamp.
+- Promote only through the policy-resolved gate.
+- Memory proposes. Ledgers authorize. Receipts prove. Audit accounts.
 
-## Operating Rules
+## When Blocked
 
-- Read the repo state before forming a plan.
-- Use a task envelope before product edits.
-- Keep each session bounded.
-- Write useful runbook notes, not raw transcript dumps.
-- Run validation before returning a receipt.
-- Keep receipts compact and cited.
-- Treat accepted review as different from integrated work.
-- Promote only through the policy-resolved gate.
-- Stop when authority, secrets, scope, or validation are unclear.
+- Use the diagnostics verbs before hand-debugging; walk the recovery path
+  from the user's seat before declaring a state recoverable.
+- Escalate with a concrete blocker, not a vibe. Quiet is not a finding.
 
 ## Identity Split
 
@@ -27,42 +87,30 @@ repo_substrate: source, ledger, receipts, validation, commits
 
 ## Work Boundaries
 
-A seat should know:
-
-- allowed writes;
-- forbidden writes;
-- validation commands;
-- stop conditions;
-- expected receipt;
-- next owner.
-
-If any of those are missing, ask for a sharper task.
-
-## Session Hygiene
-
-Sessions are for bounded work. Restoring a session restores context, not
-authority.
-
-## Review Discipline
-
-Review seats should pressure-test hidden authority changes, missing validation,
-oversized write sets, stale assumptions, unbounded sessions, evidence that
-cannot be reproduced, and claims that should be receipts.
-
-Reviewers contribute evidence. The routed owner mutates truth.
+A seat should know: allowed writes; forbidden writes; validation commands;
+stop conditions; expected receipt; next owner. If any are missing, ask for a
+sharper task. Sessions are for bounded work; restoring a session restores
+context, not authority.
 
 ## Tool Discipline
 
-Use chat for conversation, planning tools for intent, code review tools for
-diffs and CI, incident tools for runtime evidence, and identity providers for
-authentication.
-
-Do not let any of them become acceptance.
+Chat is conversation, planning tools are intent, code review tools are diffs
+and CI, incident tools are runtime evidence, identity providers are
+authentication. None of them are acceptance.
 
 ## Failure Signals
 
 Open a follow-up or stop the run when a seat edits outside allowed writes,
-validation repeatedly fails, the runbook grows without a receipt, a task spans
-unrelated repos, a runtime claims success without evidence, a projection
-disagrees with git, a grant owner is unclear, or an integration tries to close
-or promote work.
+validation repeatedly fails, the runbook grows without a receipt, a task
+spans unrelated repos, a runtime claims success without evidence, a
+projection disagrees with git, a grant owner is unclear, or an integration
+tries to close or promote work.
+
+## Growing Local Discipline
+
+This document ships the judgment that is true everywhere. Your team's own
+calibration — which seats are strong where, which tools misbehave, which
+routes need a second look — is grown locally: when a correction lands, record
+it as one small note with why and how-to-apply, index it, and re-read it at
+the moment you would otherwise repeat the mistake. Corrections that are never
+recorded are corrections you will pay for twice.

package/docs/contracts/ledger-entry/README.md

@@ -1,7 +1,7 @@
 # Ledger Entry Contracts
 
-This contract keeps the ledger-query-mode work narrow. It hardens the spine first:
-typed ledger entries that later reflex queries can read without guessing.
+This contract keeps the ledger-query-mode work narrow. It hardens the journal first:
+typed ledger entries that later working-loop queries can read without guessing.
 
 It does not ship a ledger query engine, sabbatical dossier engine, capsule
 promotion loop, or remote ledger authority.
@@ -10,7 +10,7 @@ promotion loop, or remote ledger authority.
 
 ```text
 raw local ledger entry
-  -> typed spine-eligible metadata
+  -> typed `spine_eligible` metadata
     -> optional compact projection
       -> later sabbatical capsule only after operator promotion
 ```
@@ -18,12 +18,12 @@ raw local ledger entry
 ## Core Rule
 
 ```text
-Reflex routes the present.
+The working loop routes the present.
 Sabbatical understands the arc.
-Capsules compress the arc back into reflex context.
+Capsules compress the arc back into working-loop context.
 ```
 
-The brain may recommend. The spine may route. Grants authorize. Execution
+The planner may recommend. The journal may route. Grants authorize. Execution
 mutates. Receipts prove. Audit accounts.
 
 ## Contracts
@@ -65,18 +65,18 @@ These names are reserved vocabulary, not V0 machinery:
   search adapters; SQLite FTS5 is the only V0.1 retrieval accelerator.
 - `ledger-topic-dossier.v0` — unlock only when an operator asks for a durable
   long-horizon dossier over a real topic.
-- `sabbatical-ledger-query` — reserved as the deliberate brain posture; it
-  cannot write the reflex spine directly.
-- `capsule-to-spine-feedback` — unlock only when reviewed capsules have a human
+- `sabbatical-ledger-query` — reserved as the deliberate planner posture; it
+  cannot write the working journal directly.
+- `capsule-to-journal-feedback` — unlock only when reviewed capsules have a human
   promotion surface.
 
 Deferred surfaces must name an operational consumer before implementation.
 
 ## Boundary
 
-- The brain cannot write the spine directly. It may produce a capsule or
+- The planner cannot write the journal directly. It may produce a capsule or
   dossier that an operator later promotes.
-- `spine_eligible: true` is explicit; reflex indexes do not infer eligibility
+- `spine_eligible: true` is explicit; working-loop indexes do not infer eligibility
   from entry type.
 - Existing ledger lines remain readable as `pre_v0: true` legacy entries.
 - Ledger entries do not authorize work unless a valid grant path says so.

package/docs/contracts/ledger-entry/ledger-entry.v0.2.md

@@ -9,7 +9,7 @@ does not authorize work, attach grants, close tasks, or replace receipts.
 
 ```text
 The leading timestamp (created_at) is the RECORDING time. It is never
-backdated. If work was done off the spine, it is reconciled with a late
+backdated. If work was done off the journal, it is reconciled with a late
 entry recorded at its true time, pointing at contemporaneous evidence.
 Synthesizing entries with past recording times is corruption, not repair:
 one plausible fake timestamp devalues every real one.
@@ -51,7 +51,7 @@ valid_time_end:
 ## Added Entry Type
 
 `entry_type: retroactive_import` — a late reconciliation entry covering work
-that was executed without contemporaneous spine entries. Rules, enforced by
+that was executed without contemporaneous journal entries. Rules, enforced by
 the validator:
 
 - requires schema `ledger-entry.v0.2` (rejected on v0/v0.1);

package/docs/contracts/ledger-entry/ledger-entry.v0.md

@@ -1,6 +1,6 @@
 # ledger-entry.v0
 
-`ledger-entry.v0` is the typed local ledger record used by the reflex spine.
+`ledger-entry.v0` is the typed local ledger record used by the working journal.
 It makes compact ledger lines structurally queryable without promoting the
 ledger into an authority source.
 
@@ -58,7 +58,7 @@ legacy:
 `authority.class: grant` may set it to `true`, and only when the entry carries
 the durable grant reference required by the local workflow.
 
-`spine_eligible` is explicit. A reflex index must not infer it from
+`spine_eligible` is explicit. A working-loop index must not infer it from
 `entry_type`. Entries that are useful for current-state routing should set it to
 `true`; archival, noisy, or unreviewed entries should set it to `false`.
 
@@ -92,17 +92,17 @@ legacy:
 spine_eligible: false
 ```
 
-## Spine And Brain Boundary
+## Journal And Planner Boundary
 
 ```text
-Reflex routes the present.
+The working loop routes the present.
 Sabbatical understands the arc.
-Capsules compress the arc back into reflex context.
+Capsules compress the arc back into working-loop context.
 ```
 
-The reflex spine reads typed ledger entries. The sabbatical brain may produce a
-capsule or dossier, but it cannot write back into the spine directly. Promotion
-from capsule to spine requires an explicit operator gate.
+The working journal reads typed ledger entries. The sabbatical planner may produce a
+capsule or dossier, but it cannot write back into the journal directly. Promotion
+from capsule to journal requires an explicit operator gate.
 
 ## Authority Boundary
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@etiquekit/etq",
-  "version": "1.0.1",
+  "version": "1.0.5",
   "description": "Governance and evidence CLI for AI-assisted engineering seats.",
   "private": false,
   "type": "module",