@titan-design/hitl 0.3.1 → 0.6.0

package/NOTICE

@@ -0,0 +1,216 @@
+@titan-design/hitl
+Copyright 2026 Henry Jewkes. Licensed under the MIT License.
+
+This package includes code adapted from openrig
+(https://github.com/mvschwarz/openrig), licensed under the Apache License 2.0.
+
+  Upstream file: packages/daemon/src/domain/human-questions.ts (parseHumanQuestions)
+  Adapted in:    src/gate-brief.ts (the question bounds and questionsIssue)
+  Copyright 2026 Mike Schwarz
+
+Changes: the checks report through GateBriefInvalid instead of a result union,
+and `recommended` keeps only `true`.
+
+The full text of the Apache License 2.0 follows.
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   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.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -29,12 +29,15 @@ point. The waiter polls, because the resolver may be a different process writing
 the same SQLite file.
 
 ```ts
+import os from "node:os";
+import path from "node:path";
 import { openDatabase } from "@titan-design/store-sqlite";
 import { SqliteGateStore } from "@titan-design/hitl/sqlite";
 import { openGate } from "@titan-design/hitl";
 import { z } from "zod";
 
-const store = new SqliteGateStore(openDatabase("~/.local/state/thing/gates.sqlite3"));
+const dbPath = path.join(os.homedir(), ".local/state/thing/gates.sqlite3");
+const store = new SqliteGateStore(openDatabase(dbPath));
 
 const gate = openGate(store, {
   id: "deploy-approval",
@@ -51,7 +54,11 @@ Somewhere else entirely, in a CLI, an MCP tool, or a dashboard route:
 ```ts
 import { resolveGate, cancelGate } from "@titan-design/hitl";
 
-resolveGate(store, "deploy-approval", { approved: true });
+resolveGate(store, "deploy-approval", { approved: true }, {
+  class: "owner-terminal",
+  id: "owner",
+  channel: "cli",
+});
 ```
 
 After a restart, re-attach by id instead of re-opening:
@@ -89,7 +96,7 @@ both pass the same behaviour suite.
 
 `SqliteGateStore` installs a `hitl_gate` table through store-sqlite's
 `runMigrations` on construction. Pass `migrate: false` and put `gateMigration(n)`
-in the product's own migration list when hitl shares a database with domain
+and `gateResolverMigration(m)` in the product's own migration list when hitl shares a database with domain
 tables. `table` renames the table so one database can host several gate spaces.
 Timestamps are ISO-8601 strings, the shape store-sqlite writes and any surface
 can send on as-is.
@@ -99,7 +106,7 @@ tell its waiter why.
 
 ## Who resolved it
 
-`resolve` and `resolveGate` take an optional third argument, a `GateResolver`:
+`resolve` and `resolveGate` require a third argument, a `GateResolver`:
 `{ class, id, channel, confirmEvent? }`. `class` is an actor class from
 `@titan-design/authority`. The store records it as `resolvedBy`.
 
@@ -116,23 +123,145 @@ agent or automation never answers a gate. It throws `GateResolverRefused` and th
 pending. The store reads each declared resolver field once into a frozen copy, and checks and stores
 only that copy. A store's `authorize` option runs after the class check and can refuse more,
 never fewer. It must return `{ allowed }` synchronously, or the store throws
-`GateAuthorizeInvalid`. With `authorize` installed, a resolve that names no resolver is refused.
+`GateAuthorizeInvalid`.
 Refusals name the gate id and the actor class, never the resolver's other fields.
 
+### Allowances
+
+A product may admit a non-owner class for specific answers by passing `allowances` to the store:
+a list of `{ resolverClass, stepId, payload }`. An allowance admits exactly that class, a gate whose
+step is `stepId` (the text after the last `/` of its id, with any `:<n>` repeat suffix removed) and a
+payload deep-equal to `payload`, and only when the resolver's `id` is not blank. Anything else gets the
+default refusal unchanged. The list is copied when the store is built, so a caller cannot widen it
+later, and the gate's rule and `authorize` still run after it.
+
+```ts
+new MemoryGateStore({ allowances: [{ resolverClass: "coordinator", stepId: "stuck-behind", payload: { decision: "retry" } }] });
+```
+
 hitl records a claim about the resolver; it cannot prove one. Any process that can write
 the database can claim any class.
 
 On SQLite the resolver lives in a `resolved_by` column that `gateResolverMigration(n)` adds,
-along with a trigger that refuses any resolve naming no resolver. Add it to your own
-migration list after `gateMigration`. It is idempotent and does not backfill: gates resolved
-before it read back with `resolvedBy` undefined. Until the migration runs, a store resolves
-without a resolver as before and throws `GateStoreSchemaOutdated` when given one, rather
-than dropping it. `migrate: true` does not run it yet.
+along with a trigger that refuses any resolve naming no resolver. `migrate: true` runs it as
+version 2; with `migrate: false`, add it to your own migration list after `gateMigration`. It
+is idempotent and does not backfill: gates resolved before it read back with `resolvedBy`
+undefined. `SqliteGateStore` checks for the column when it is constructed and throws
+`GateStoreSchemaOutdated` naming `gateResolverMigration` when it is missing, or naming
+`gateMigration` when the table does not exist. That error carries an empty `gateId`,
+because no gate is involved yet.
 
 After the migration, a writer built on hitl 0.2.x fails when it resolves: SQLite aborts the
 statement with a raw error whose message is `hitl: resolvedBy required`. The same trigger
 refuses a direct insert of a resolved row with no resolver. Cancels from an old writer still
-work. The fix is to upgrade that writer so it passes a resolver.
+work. The fix is to upgrade that writer so it passes a resolver. A caller on this release
+never reaches the trigger: every store refuses a resolve with no resolver first.
+
+## Upgrading to 0.4
+
+0.4 makes the resolver required. It is a breaking release; a `^0.3` range does not pick it up.
+
+1. Pass a `GateResolver` to every `store.resolve`, `resolveGate` and workflow
+   `runtime.signal` call. The compiler finds each one. Name the class honestly: a human at
+   a terminal is `owner-terminal`, a human on a phone is `owner-remote`. An agent or an
+   automation cannot resolve a gate, by design.
+2. Add `gateResolverMigration(n)` to your migration list, after `gateMigration`, with the
+   next free version in your own list. `migrate: true` stores run it for you as version 2.
+3. Expect `GateStoreSchemaOutdated` naming `gateResolverMigration` from the
+   `SqliteGateStore` constructor if step 2 is missing. The store no longer opens over such a
+   table.
+4. Upgrade every process that writes the gate table at once. A writer still on 0.2 fails
+   each resolve with SQLite's `hitl: resolvedBy required` once the migration has run.
+
+A caller that bypasses the type and resolves with no resolver gets `GateResolverRefused`
+with the reason `a resolver is required` from every store, memory or SQLite, and the gate
+stays pending.
+
+## Rule-bound gates
+
+A gate can carry the authority rule that opened it. Pass `rule` to `create`:
+`{ table, version, ruleId, resolvers }`, where `resolvers` lists the resolver classes the
+rule admits, as `evaluate` from `@titan-design/authority` returns them.
+
+```ts
+store.create({
+  id: "release-approval",
+  prompt: "Publish the release?",
+  rule: { table: "F5", version: "1.0.0", ruleId: "REL-CO", resolvers: ["owner-terminal"] },
+});
+```
+
+The store reads the rule once into a frozen copy, so the caller cannot widen it after
+`create`. A rule that is not a non-empty list of resolver classes throws `GateRuleInvalid`
+and creates nothing. A rule-bound gate refuses a resolver whose class the rule does not
+name, and refuses a resolve that names no resolver. Both throw `GateResolverRefused` and
+leave the gate pending. The check runs after the default class check and before
+`authorize`, so it only narrows. A gate without a rule behaves as before.
+
+On SQLite the rule lives in a `rule` column that `gateRuleMigration(n)` adds, along with a
+trigger that aborts any update resolving a rule-bound row by a class outside its rule, or
+changing the rule, with `hitl: resolver outside the gate rule`. That stops a writer built on
+hitl 0.3.x, which knows nothing of rules, from widening who may answer. The migration is
+idempotent and does not backfill. `migrate: true` runs it as version 3. A store whose table
+lacks the column throws `GateStoreSchemaOutdated` naming `gateRuleMigration` when handed a
+rule, rather than dropping it.
+
+The trigger needs `resolved_by` to know who answered. On a table that has run
+`gateRuleMigration` but not `gateResolverMigration`, the trigger aborts every raw resolve of
+a rule-bound row, and no store opens over the table. Run both migrations in either order;
+the second one installs the class-aware trigger.
+
+The insert guard fires before SQLite's conflict handling. A raw insert with no rule onto a
+pending rule-bound id therefore aborts with `hitl: a pending rule-bound gate cannot be
+replaced`, whether it is a plain duplicate, `ON CONFLICT DO UPDATE`, `ON CONFLICT DO NOTHING`
+or `INSERT OR IGNORE`; a duplicate plain insert reports that message, not `UNIQUE`. The guard
+covers only pending rows. A raw `REPLACE` of a cancelled or resolved rule-bound row succeeds
+and can leave a pending rule-less row. That is outside the store API: `create` is a plain
+insert and throws on an existing id, and no store method replaces a row.
+
+## Gate briefs
+
+A gate's `prompt` is written for the machine. A brief is what the owner reads: pass
+`summary`, `evidenceRef` and optionally `questions` to `create` or `openGate`.
+
+```ts
+openGate(store, {
+  id: "release-approval",
+  prompt: "release-1.4.0",
+  schema: z.object({ decision: z.enum(["release", "hold"]) }),
+  summary: "Release 1.4.0? CI green on main. Recommend release.",
+  evidenceRef: "https://github.com/acme/thing/actions/runs/1",
+  questions: [{
+    id: "decision",
+    question: "Release 1.4.0?",
+    options: [{ id: "release", label: "Release", recommended: true }, { id: "hold", label: "Hold" }],
+  }],
+});
+```
+
+| Field | Bound |
+| --- | --- |
+| `summary` | 1-280 characters on one line: the decision and the recommendation |
+| `evidenceRef` | 1-500 characters on one line: an https URL, an absolute path, or `$ <command>` |
+| `questions` | 1-4 questions with unique ids; each has 1-500 characters of text and 2-4 options |
+| option | unique id (1-40 letters, digits, `-`, `_`), a label of at most 75 characters (the Slack button limit), at most one `recommended: true` per question |
+
+A store built with `requireBrief: true` refuses `create` without a `summary` and an
+`evidenceRef`. Without it both stay optional, but a brief field that is present is still
+checked. A refused brief throws `GateBriefInvalid`, whose `issues` names each problem, and
+writes no row. `questions` is the presentation contract only: `schema` still validates the
+answer, and hitl does not cross-check the two. `snapshotBrief` is the same check, exported for
+a surface that wants to validate before it opens a gate.
+
+On SQLite the brief lives in `summary`, `evidence_ref` and `questions` columns that
+`gateBriefMigration(n)` adds. It is idempotent and does not backfill: gates opened before it
+read back with all three undefined, and still resolve. `migrate: true` runs it as version 4.
+A store whose table lacks the columns throws `GateStoreSchemaOutdated` naming
+`gateBriefMigration` when handed a brief, rather than dropping it, and refuses to construct
+at all when `requireBrief` is set.
+
+The question bounds are adapted from openrig (Apache-2.0); `src/gate-brief.ts` carries the
+attribution.
 
 ## Settling
 

package/dist/{base-store-BvwOJL6M.d.ts → base-store-B-IPO0UN.d.ts}

@@ -1,4 +1,4 @@
-import { ActorClass } from '@titan-design/authority';
+import { ResolverClass, ActorClass } from '@titan-design/authority';
 
 /** A gate is a row, never a promise: pending work survives the process that opened it. */
 type GateStatus = "pending" | "resolved" | "cancelled" | "expired";
@@ -18,6 +18,46 @@ interface GateRecord {
     expiresAt: string | undefined;
     /** Who resolved the gate, as claimed by the caller; unset for gates resolved before stores recorded it. */
     resolvedBy: GateResolver | undefined;
+    /** The authority rule that opened the gate; unset for a gate no rule governs. */
+    rule: GateRule | undefined;
+    /** One line for the owner: the decision and the recommendation. Unset for a gate opened without a brief. */
+    summary: string | undefined;
+    /** Where the owner checks the facts: an https URL, an absolute path, or `$ <command>`. */
+    evidenceRef: string | undefined;
+    /** A fixed menu a surface can render as buttons; the gate's `schema` still validates the answer. */
+    questions: GateQuestion[] | undefined;
+}
+interface GateQuestionOption {
+    /** 1-40 letters, digits, `-` or `_`; unique within its question. */
+    id: string;
+    /** 1-75 characters, the Slack button limit. */
+    label: string;
+    /** At most one option per question; omitted means false. */
+    recommended?: true;
+}
+interface GateQuestion {
+    /** 1-40 letters, digits, `-` or `_`; unique within the gate. */
+    id: string;
+    /** 1-500 characters. */
+    question: string;
+    /** 2-4 options. */
+    options: GateQuestionOption[];
+}
+/** What the owner reads instead of the machine-facing prompt. A store with `requireBrief` refuses a gate without one. */
+interface GateBrief {
+    /** 1-280 characters on one line. */
+    summary: string;
+    /** 1-500 characters on one line. */
+    evidenceRef: string;
+    /** 1-4 questions; absent means the gate's schema alone defines the answer. */
+    questions?: GateQuestion[];
+}
+/** Binds a gate to the authority rule that opened it, so only that rule's resolver classes may answer. */
+interface GateRule {
+    table: string;
+    version: string;
+    ruleId: string;
+    resolvers: ResolverClass[];
 }
 /** A claim about who answered a gate. hitl records it and checks its class; it cannot prove it. */
 interface GateResolver {
@@ -38,12 +78,28 @@ type GateAuthorization = {
  * never admit one the default refused. Must return synchronously.
  */
 type GateAuthorize = (gate: Readonly<GateRecord>, resolver: Readonly<GateResolver>) => GateAuthorization;
+/**
+ * One answer a non-owner class may give, declared by the product when it builds the store.
+ * It admits exactly: `resolverClass`, a gate whose step is `stepId` (a bare id or `<id>:<n>` after
+ * the last `/`), and a payload deep-equal to `payload`. Evaluated in place of the default refusal for
+ * those gates only; the gate's rule and `authorize` still run after it. The resolver's id must be non-blank.
+ */
+interface GateAnswerAllowance {
+    resolverClass: ActorClass;
+    stepId: string;
+    payload: Readonly<Record<string, unknown>>;
+}
 interface GateInput {
     /** Defaults to a random UUID. Supply one to make the gate addressable by a name you already own. */
     id?: string;
     prompt: string;
     schema?: JsonSchema;
     expiresAt?: Date | string;
+    rule?: GateRule;
+    /** Required, with `evidenceRef`, when the store has `requireBrief`. */
+    summary?: string;
+    evidenceRef?: string;
+    questions?: GateQuestion[];
 }
 /**
  * Synchronous on purpose: both implementations are local (a Map, and
@@ -52,7 +108,7 @@ interface GateInput {
 interface GateStore {
     create(input: GateInput): GateRecord;
     get(id: string): GateRecord | undefined;
-    resolve(id: string, payload: unknown, resolvedBy?: GateResolver): GateRecord;
+    resolve(id: string, payload: unknown, resolvedBy: GateResolver): GateRecord;
     cancel(id: string, reason: string): GateRecord;
     listPending(): GateRecord[];
 }
@@ -89,12 +145,23 @@ declare class GateResolverRefused extends GateError {
     readonly reason: string;
     constructor(gateId: string, actorClass: string | undefined, reason: string);
 }
-/** The store cannot record a resolver because its table predates the resolver migration. */
+/**
+ * The store cannot record a resolver or a rule because its table predates the migration that adds the column.
+ * `gateId` is empty when the store refuses at construction, before any gate is named.
+ */
 declare class GateStoreSchemaOutdated extends GateError {
     readonly table: string;
     readonly migration: string;
     constructor(gateId: string, table: string, migration: string);
 }
+declare class GateRuleInvalid extends GateError {
+    readonly reason: string;
+    constructor(gateId: string, reason: string);
+}
+declare class GateBriefInvalid extends GateError {
+    readonly issues: string[];
+    constructor(gateId: string, issues: string[]);
+}
 declare class GateAuthorizeInvalid extends GateError {
     constructor(gateId: string);
 }
@@ -106,22 +173,24 @@ declare class GateAuthorizeInvalid extends GateError {
 declare abstract class BaseGateStore implements GateStore {
     protected readonly clock: () => number;
     private readonly authorize?;
-    protected constructor(clock: () => number, authorize?: GateAuthorize | undefined);
+    private readonly requireBrief;
+    protected constructor(clock: () => number, authorize?: GateAuthorize | undefined, requireBrief?: boolean, allowances?: readonly GateAnswerAllowance[]);
+    private readonly allowances;
     protected abstract insert(record: GateRecord): void;
     protected abstract read(id: string): GateRecord | undefined;
     protected abstract update(record: GateRecord): void;
     protected abstract readByStatus(status: GateRecord["status"]): GateRecord[];
     create(input: GateInput): GateRecord;
     get(id: string): GateRecord | undefined;
-    resolve(id: string, payload: unknown, resolvedBy?: GateResolver): GateRecord;
+    resolve(id: string, payload: unknown, resolvedBy: GateResolver): GateRecord;
     cancel(id: string, reason: string): GateRecord;
     listPending(): GateRecord[];
     private requirePending;
-    /** The default check runs first and `authorize` second, so `authorize` can only narrow who may resolve. */
+    /** The default check (or a listed allowance) runs first, the gate's rule second and `authorize` last, so each can only narrow who may resolve. */
     private requireAuthorized;
     /** Expiry is lazy: nothing sweeps the table, so a read is what notices the deadline passed. */
     private lapseIfExpired;
     protected nowIso(): string;
 }
 
-export { BaseGateStore as B, type GateRecord as G, type JsonSchema as J, type GateStore as a, type GateResolver as b, type GateAuthorize as c, GateAborted as d, GateAlreadyExists as e, GateAlreadySettled as f, type GateAuthorization as g, GateAuthorizeInvalid as h, GateCancelled as i, GateError as j, GateExpired as k, type GateInput as l, GateNotFound as m, GatePayloadInvalid as n, GateResolverRefused as o, type GateStatus as p, GateStoreSchemaOutdated as q };
+export { BaseGateStore as B, type GateRecord as G, type JsonSchema as J, type GateQuestion as a, type GateStore as b, type GateResolver as c, type GateAuthorize as d, type GateAnswerAllowance as e, GateAborted as f, GateAlreadyExists as g, GateAlreadySettled as h, type GateAuthorization as i, GateAuthorizeInvalid as j, type GateBrief as k, GateBriefInvalid as l, GateCancelled as m, GateError as n, GateExpired as o, type GateInput as p, GateNotFound as q, GatePayloadInvalid as r, type GateQuestionOption as s, GateResolverRefused as t, type GateRule as u, GateRuleInvalid as v, type GateStatus as w, GateStoreSchemaOutdated as x };