sigild 0.0.1

package/CONTRIBUTING.md

@@ -0,0 +1,39 @@
+# Contributing to sigil
+
+## Workflow
+
+- Work happens on feature branches: `feat/<layer>`, `fix/<short>`, or `chore/<short>`.
+- Push the branch and open a PR against `main`.
+- PR description links the issue with a `Refs #N` or `Closes #N` trailer.
+- CI must pass before merge. The required check is `Test (Node 22)`.
+- Squash-merge only (linear history on `main`).
+- Delete the branch after merge.
+
+Direct pushes to `main` are blocked by branch protection. Repo admins can bypass in an emergency, but should still prefer the PR path.
+
+## Local development
+
+```sh
+npm install   # respects .npmrc (ignore-scripts=true)
+npm test      # tsc + node --test 'dist/test/**/*.test.js'
+```
+
+Tests must pass locally before pushing.
+
+## Commit messages
+
+- Subject line under 70 characters, imperative mood ("Add X", not "Added X").
+- Body explains the **why**. The diff already shows the **what**.
+- No `Co-Authored-By` trailers.
+- Reference issues with `Refs #N` (partial work) or `Closes #N` (completes the issue).
+
+## Security
+
+Never commit:
+- `.env`, `.env.*`
+- `*.pem`, `*.key`, `*.keystore`
+- Anything inside `~/.sigil/` or a project-local `.sigil/`
+
+The repo `.gitignore` covers these patterns. Double-check `git status` before committing.
+
+For security issues in sigil itself, open a private GitHub Security Advisory rather than a public issue.

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 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

@@ -0,0 +1,70 @@
+# sigil
+
+> Claude can sign, but never see.
+
+`sigil` is a local signing daemon and Claude Code integration that lets agentic coding tools use private keys without ever putting key material in the model's context window.
+
+**Status:** pre-alpha. Threat model is committed before the code. Do not use this with real funds yet. Build plan and current progress live in the [tracking issue](https://github.com/cdrn/sigil/issues/9).
+
+## What it is
+
+Three components that work together:
+
+1. **`sigild`** — a long-running local daemon that holds unlocked keys in process memory (zeroized on shutdown; mlock against swap is planned, see [THREAT_MODEL.md](./THREAT_MODEL.md)) and exposes signing operations over a Unix socket. Keys at rest are encrypted with XChaCha20-Poly1305 and an Argon2id-derived key.
+2. **`sigil-mcp`** — an MCP server that Claude (or any agentic tool) talks to. It forwards signing requests to `sigild` and returns signatures. Claude never sees key material — only opaque handles like `eth:executor`.
+3. **Hooks (the wards)** — `sigil init` installs PreToolUse and PostToolUse hooks into `.claude/settings.json` that block `Read` and `Bash` from touching key paths, and redact key-shaped strings from tool output.
+
+## What it isn't
+
+- Not a hardware wallet replacement. If you can use a Ledger or YubiKey, do that.
+- Not a custody solution. It runs on your laptop or VPS and protects you from one specific class of failure: leaking key material through an LLM agent.
+- Not a substitute for policy. The library prevents *ingestion* of keys; the policy engine prevents *misuse* of signing authority. Both matter — see the threat model.
+
+## How it will work (sketch)
+
+```bash
+# one-time setup
+sigil init                          # installs hooks into ~/.claude/settings.json
+sigil up                            # starts the daemon, unlocks keys via OS keychain
+
+# register a key with policy
+sigil portal add executor \
+  --type eth \
+  --key-file ~/keys/bot.key \
+  --policy ./policies/executor.toml
+
+# Claude now sees `eth:executor` as a portal it can sign with,
+# but cannot read the key file or anything under ~/.sigil
+```
+
+A policy file looks like:
+
+```toml
+[portal.executor]
+chain_ids = [1, 42161, 8453]
+allow_to = ["0xRouter...", "0xExecutor..."]
+max_value_wei = "100000000000000000"   # 0.1 ETH per tx
+max_value_per_hour_wei = "500000000000000000"
+allowed_selectors = ["0xa9059cbb", "0x095ea7b3"]   # transfer, approve
+require_confirm_above_wei = "10000000000000000"    # push to phone for human ack
+```
+
+## Supply chain posture
+
+Key-management libraries die from supply chain compromise, not from clever attacks on the code. Given the npm ecosystem in 2026 (Mini Shai-Hulud, Axios, pgserve, TanStack), `sigil` commits to:
+
+- **Zero install scripts.** No `postinstall`, `preinstall`, `prepare`. CI-enforced.
+- **Minimal dependencies.** Core sign path uses [`@noble/secp256k1`](https://github.com/paulmillr/noble-secp256k1) and `@noble/hashes` (audited, zero-dep). No viem in the core daemon.
+- **No Bun.** Plain Node only. Bun is currently being weaponized by Mini Shai-Hulud as an evasion layer; we will not give that pattern any cover.
+- **Provenance attestations** on every npm release via GitHub Actions trusted publishing.
+- **Signed standalone binaries** from GitHub Releases for users who'd rather not touch npm.
+- **Reproducible builds + SBOM** published with each release.
+- **No long-lived publish tokens.** OIDC only.
+
+## Threat model
+
+See [THREAT_MODEL.md](./THREAT_MODEL.md). Read it before trusting this with anything.
+
+## License
+
+Apache License 2.0. See [LICENSE](./LICENSE).

package/THREAT_MODEL.md

@@ -0,0 +1,84 @@
+# Threat Model
+
+This document describes what `sigil` defends against, what it doesn't, and the assumptions it makes. Read it before deciding whether `sigil` is appropriate for your use case.
+
+## Actors
+
+- **The user.** Has root on the machine. Trusted.
+- **The agent (e.g. Claude).** Untrusted in the specific sense that its context window can be poisoned by adversarial inputs (prompt injection from web pages, file contents, tool output). The agent itself is not malicious, but anything it ingests can become an instruction.
+- **The attacker.** May control content the agent reads (web pages, repos, API responses, transaction calldata) and may have published malicious dependencies the user installs.
+- **The host OS.** Trusted. If the attacker has local code execution as your user, `sigil` does not help.
+
+## Assets
+
+In order of value:
+
+1. **Private key material.** Must never leave `sigild`'s address space.
+2. **Signing authority.** A signature `sigild` produces on behalf of a portal is a financial action. The set of authorized actions is bounded by per-portal policy.
+3. **The audit log.** Append-only record of every sign decision. Tampering with it defeats post-incident forensics.
+
+## In scope
+
+### 1. Preventing key ingestion by the agent
+
+The primary threat. Failure mode: a private key ends up in the agent's context window, then in transcripts, prompt caches, cloud logs, or attacker-controlled exfiltration paths.
+
+Defenses:
+- Keys live in `sigild`'s memory only, unlocked from encrypted at-rest storage. Plaintext is zeroized on shutdown. mlock against swap is planned (requires a native module distributed as bundled prebuilds, see Known limitations).
+- The MCP interface exposes only opaque handles (`eth:executor`), never key bytes.
+- PreToolUse hooks block `Read` and `Bash` access to `~/.sigil/**`, `*.pem`, `**/.env*`, `**/keystore*`, and a configurable extra list.
+- PostToolUse output filter redacts hex-encoded 32-byte blobs, PEM blocks, and bip39-shaped strings from tool output before it reaches the model.
+
+### 2. Bounding signing authority
+
+A defended key still loses you money if the agent can be tricked into signing the wrong payload. Prompt injection through transaction calldata, web content, or repo files can redirect signing intent.
+
+Defenses (policy engine, per portal):
+- Destination allowlists (`allow_to`)
+- Per-tx and rolling-window value caps
+- Allowed function selectors (only `transfer`, `approve`, etc.)
+- Chain ID allowlists
+- Out-of-band human confirmation above a configurable value threshold (push to Pushover / Telegram / Apple Push)
+- Append-only audit log with monotonic counter
+
+### 3. Supply chain compromise of `sigil` itself
+
+Given the 2026 npm threat landscape, a compromised release of `sigil` would be catastrophic. Defenses:
+
+- Zero install scripts (`postinstall`, `preinstall`, `prepare`). CI-enforced.
+- Minimal, audited dependencies (`@noble/*` family, plain Node stdlib).
+- Provenance attestations via GitHub Actions trusted publishing (OIDC, no long-lived tokens).
+- Signed standalone binaries as an alternative distribution channel.
+- Reproducible builds, published SBOM, public release checksums.
+- No Bun in any distributed artifact.
+
+## Out of scope
+
+`sigil` does not defend against:
+
+- **Local code execution as your user.** If an attacker can run code as `$USER`, they can `ptrace` the daemon, read mlock'd memory, or simply ask `sigild` to sign things over the socket. `sigil` makes this harder (audit log will show it, policy still applies) but does not prevent it.
+- **Root or kernel compromise.** mlock prevents swap; it does not prevent a root user from reading process memory.
+- **Side channels on shared hardware.** Cache timing, Rowhammer, etc.
+- **Physical access to an unlocked machine.**
+- **Malicious user.** If you're trying to protect keys from yourself, you want a hardware wallet, not `sigil`.
+- **Compromise of upstream cryptographic primitives.** We rely on `@noble/*` being correct. If secp256k1 is broken, everyone has bigger problems.
+- **Confused-deputy at the policy boundary.** If your policy says "any tx to 0xRouter is fine" and the router happens to forward arbitrary calldata, `sigil` will sign whatever the agent asks. Policies must be written defensively.
+
+## Assumptions
+
+- The user installs `sigil` through a trusted channel (signed release, verified npm provenance, or built from source).
+- The host OS enforces standard process isolation.
+- The user's OS keychain (or chosen unlock mechanism) is not compromised.
+- Clock skew on the host is bounded (matters for rolling-window policy and audit timestamps).
+
+## Known limitations
+
+- The hook-based path blocker is best-effort: it covers `Read` and `Bash`, but a sufficiently creative agent could still ask another tool to do the read. The defense in depth is that even if a key file is read, its contents are redacted by the output filter before reaching the model.
+- The output redaction filter has false negatives (keys with non-standard encoding) and false positives (legitimate hex blobs). It is not a replacement for the path blocker; it's a second line.
+- The MCP socket is currently unauthenticated within the user's session. Any process running as `$USER` can connect to it. This is consistent with the threat model (we don't defend against local user compromise) but worth stating explicitly.
+- **mlock is not yet implemented.** Plaintext key material lives in a regular `Buffer` that is zeroized on daemon shutdown or unlock-failure. This means keys are vulnerable to being paged to swap on a memory-pressured system. mlock requires a native module, which we will ship as bundled prebuilds (no install scripts) rather than via a compile-on-install dependency. Tracked as a planned layer.
+- Out-of-band confirmation depends on a working push channel. If the push provider is down, high-value signs are denied, not approved.
+
+## Reporting issues
+
+Security issues: open a GitHub security advisory on the repo. Please do not file public issues for vulnerabilities.

package/dist/src/audit/index.d.ts

@@ -0,0 +1,2 @@
+export { type AuditDecision, type AuditEntry, type StoredAuditEntry, type ChainHead, ZERO_HASH, HASH_HEX_LEN, AuditChainError, AuditWriter, canonicalJSON, hashEntry, sealEntry, serializeEntry, parseLine, verifyChain, readHead, } from './log.js';
+//# sourceMappingURL=index.d.ts.map

package/dist/src/audit/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/audit/index.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,KAAK,aAAa,EAClB,KAAK,UAAU,EACf,KAAK,gBAAgB,EACrB,KAAK,SAAS,EACd,SAAS,EACT,YAAY,EACZ,eAAe,EACf,WAAW,EACX,aAAa,EACb,SAAS,EACT,SAAS,EACT,cAAc,EACd,SAAS,EACT,WAAW,EACX,QAAQ,GACT,MAAM,UAAU,CAAC"}

package/dist/src/audit/index.js

@@ -0,0 +1,2 @@
+export { ZERO_HASH, HASH_HEX_LEN, AuditChainError, AuditWriter, canonicalJSON, hashEntry, sealEntry, serializeEntry, parseLine, verifyChain, readHead, } from './log.js';
+//# sourceMappingURL=index.js.map

package/dist/src/audit/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../src/audit/index.ts"],"names":[],"mappings":"AAAA,OAAO,EAKL,SAAS,EACT,YAAY,EACZ,eAAe,EACf,WAAW,EACX,aAAa,EACb,SAAS,EACT,SAAS,EACT,cAAc,EACd,SAAS,EACT,WAAW,EACX,QAAQ,GACT,MAAM,UAAU,CAAC"}

package/dist/src/audit/log.d.ts

@@ -0,0 +1,96 @@
+export type AuditDecision = 'allow' | 'deny' | 'confirm_required';
+export interface AuditEntry {
+    seq: number;
+    ts: number;
+    prev_hash: string;
+    kind: string;
+    portal: string;
+    payload: unknown;
+    decision: AuditDecision;
+    reason?: string;
+    sig?: string;
+}
+export interface StoredAuditEntry extends AuditEntry {
+    hash: string;
+}
+export declare const ZERO_HASH: string;
+export declare const HASH_HEX_LEN = 64;
+export declare class AuditChainError extends Error {
+    readonly atSeq: number | undefined;
+    constructor(msg: string, atSeq?: number);
+}
+/**
+ * Canonical JSON serialization: keys sorted lexicographically, recursive.
+ * This is what we hash, so it must be deterministic across engine
+ * versions and across re-serializations.
+ */
+export declare function canonicalJSON(value: unknown): string;
+/**
+ * Compute the keccak256 hash of an entry (without the `hash` field).
+ * Returns lowercase hex.
+ */
+export declare function hashEntry(entry: AuditEntry): string;
+/**
+ * Stamp an entry with its hash.
+ */
+export declare function sealEntry(entry: AuditEntry): StoredAuditEntry;
+/**
+ * Serialize a stored entry to a single JSON line (newline-terminated).
+ */
+export declare function serializeEntry(entry: StoredAuditEntry): string;
+/**
+ * Parse a single line and verify its self-hash. Does NOT check chain linkage.
+ */
+export declare function parseLine(line: string): StoredAuditEntry;
+/**
+ * Verify a buffer's worth of JSONL audit entries.
+ * - Empty buffer → empty chain.
+ * - Each entry must self-hash correctly.
+ * - Each entry's seq must be expected (0, 1, 2, ...).
+ * - Each entry's prev_hash must match the previous entry's hash.
+ * - A trailing non-empty fragment (no terminating newline) is a torn write.
+ *
+ * Returns the entries in order. Throws AuditChainError on any failure.
+ */
+export declare function verifyChain(buf: Buffer | string): StoredAuditEntry[];
+/**
+ * The head state of an audit chain: enough to append the next entry.
+ */
+export interface ChainHead {
+    nextSeq: number;
+    prevHash: string;
+}
+/**
+ * Read the chain head from an existing audit file. Verifies the whole chain
+ * during read. If the file does not exist or is empty, returns the genesis head.
+ */
+export declare function readHead(path: string): ChainHead;
+/**
+ * Append-only audit writer with fsync after every write.
+ *
+ * Typical use:
+ *   const w = new AuditWriter('/path/to/audit.log');
+ *   w.append({ kind: 'eth_sign_message', portal: 'eth:bot', payload, decision: 'allow', sig });
+ *   w.close();
+ *
+ * The seq and prev_hash fields are managed by the writer; callers supply
+ * everything else.
+ */
+export declare class AuditWriter {
+    #private;
+    readonly path: string;
+    constructor(path: string, opts?: {
+        now?: () => number;
+    });
+    get head(): ChainHead;
+    append(input: {
+        kind: string;
+        portal: string;
+        payload: unknown;
+        decision: AuditDecision;
+        reason?: string;
+        sig?: string;
+    }): StoredAuditEntry;
+    close(): void;
+}
+//# sourceMappingURL=log.d.ts.map

package/dist/src/audit/log.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"log.d.ts","sourceRoot":"","sources":["../../../src/audit/log.ts"],"names":[],"mappings":"AAGA,MAAM,MAAM,aAAa,GAAG,OAAO,GAAG,MAAM,GAAG,kBAAkB,CAAC;AAElE,MAAM,WAAW,UAAU;IACzB,GAAG,EAAE,MAAM,CAAC;IACZ,EAAE,EAAE,MAAM,CAAC;IACX,SAAS,EAAE,MAAM,CAAC;IAClB,IAAI,EAAE,MAAM,CAAC;IACb,MAAM,EAAE,MAAM,CAAC;IACf,OAAO,EAAE,OAAO,CAAC;IACjB,QAAQ,EAAE,aAAa,CAAC;IACxB,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,GAAG,CAAC,EAAE,MAAM,CAAC;CACd;AAED,MAAM,WAAW,gBAAiB,SAAQ,UAAU;IAClD,IAAI,EAAE,MAAM,CAAC;CACd;AAED,eAAO,MAAM,SAAS,QAAiB,CAAC;AACxC,eAAO,MAAM,YAAY,KAAK,CAAC;AAE/B,qBAAa,eAAgB,SAAQ,KAAK;IACxC,QAAQ,CAAC,KAAK,EAAE,MAAM,GAAG,SAAS,CAAC;gBACvB,GAAG,EAAE,MAAM,EAAE,KAAK,CAAC,EAAE,MAAM;CAKxC;AAED;;;;GAIG;AACH,wBAAgB,aAAa,CAAC,KAAK,EAAE,OAAO,GAAG,MAAM,CAuBpD;AAED;;;GAGG;AACH,wBAAgB,SAAS,CAAC,KAAK,EAAE,UAAU,GAAG,MAAM,CAEnD;AAED;;GAEG;AACH,wBAAgB,SAAS,CAAC,KAAK,EAAE,UAAU,GAAG,gBAAgB,CAE7D;AAED;;GAEG;AACH,wBAAgB,cAAc,CAAC,KAAK,EAAE,gBAAgB,GAAG,MAAM,CAE9D;AAED;;GAEG;AACH,wBAAgB,SAAS,CAAC,IAAI,EAAE,MAAM,GAAG,gBAAgB,CA4CxD;AAED;;;;;;;;;GASG;AACH,wBAAgB,WAAW,CAAC,GAAG,EAAE,MAAM,GAAG,MAAM,GAAG,gBAAgB,EAAE,CA8BpE;AAED;;GAEG;AACH,MAAM,WAAW,SAAS;IACxB,OAAO,EAAE,MAAM,CAAC;IAChB,QAAQ,EAAE,MAAM,CAAC;CAClB;AAED;;;GAGG;AACH,wBAAgB,QAAQ,CAAC,IAAI,EAAE,MAAM,GAAG,SAAS,CAgBhD;AAED;;;;;;;;;;GAUG;AACH,qBAAa,WAAW;;IACtB,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;gBAMV,IAAI,EAAE,MAAM,EAAE,IAAI,GAAE;QAAE,GAAG,CAAC,EAAE,MAAM,MAAM,CAAA;KAAO;IAM3D,IAAI,IAAI,IAAI,SAAS,CAEpB;IAED,MAAM,CAAC,KAAK,EAAE;QACZ,IAAI,EAAE,MAAM,CAAC;QACb,MAAM,EAAE,MAAM,CAAC;QACf,OAAO,EAAE,OAAO,CAAC;QACjB,QAAQ,EAAE,aAAa,CAAC;QACxB,MAAM,CAAC,EAAE,MAAM,CAAC;QAChB,GAAG,CAAC,EAAE,MAAM,CAAC;KACd,GAAG,gBAAgB;IA4BpB,KAAK,IAAI,IAAI;CAGd"}