chain-insights 0.3.9 → 0.3.18

package/dist/viz-DB5XFG1z.mjs

@@ -1,35 +0,0 @@
-import { t as __exportAll } from "./rolldown-runtime-D7D4PA-g.mjs";
-import { r as truncateGraph } from "./data-extractor-B4nHw1wZ.mjs";
-import { r as writeVizHtml, t as generateHtml } from "./html-generator-AowOmzyi.mjs";
-import { readFile } from "node:fs/promises";
-//#region src/viz/index.ts
-var viz_exports = /* @__PURE__ */ __exportAll({ generateVisualization: () => generateVisualization });
-async function generateVisualization(opts) {
-	let rawData;
-	if (opts.dataFile) {
-		const content = await readFile(opts.dataFile, "utf-8");
-		let parsed;
-		try {
-			parsed = JSON.parse(content);
-		} catch {
-			throw new Error("Invalid transaction data. The input file must contain a JSON array of transaction objects with `from`, `to`, and `value` fields.");
-		}
-		const { extractGraphFromJson } = await import("./data-extractor-B4nHw1wZ.mjs").then((n) => n.t);
-		rawData = extractGraphFromJson(parsed);
-	} else if (opts.caseId) {
-		const { extractGraphFromCase } = await import("./data-extractor-B4nHw1wZ.mjs").then((n) => n.t);
-		const extracted = await extractGraphFromCase(opts.caseId);
-		if (extracted.nodes.length === 0) throw new Error("No Transaction Data. This case has no evidence with transaction data. Add evidence using `chain-insights evidence add` or provide a JSON file with `chain-insights viz --data <file.json>`.");
-		rawData = extracted;
-	} else throw new Error("Provide either a case ID or --data <file.json>");
-	const data = truncateGraph(rawData);
-	const vizId = opts.caseId ? `${opts.caseId}_${Date.now()}` : `adhoc_${Date.now()}`;
-	return {
-		vizId,
-		htmlPath: await writeVizHtml(vizId, generateHtml(data, data.metadata.caseId ? `${data.metadata.caseId} - Money Flow` : "Ad-hoc Visualization"), opts.caseId)
-	};
-}
-//#endregion
-export { viz_exports as n, generateVisualization as t };
-
-//# sourceMappingURL=viz-DB5XFG1z.mjs.map

package/dist/viz-DB5XFG1z.mjs.map

@@ -1 +0,0 @@
-{"version":3,"file":"viz-DB5XFG1z.mjs","names":[],"sources":["../src/viz/index.ts"],"sourcesContent":["export { GraphData, GraphNode, GraphEdge, EntityType, RiskLevel, truncateGraph } from './graph-model.js'\nexport type { GraphData as GraphDataType, GraphNode as GraphNodeType, GraphEdge as GraphEdgeType } from './graph-model.js'\nexport { generateHtml, writeVizHtml, transformToGraphHtml } from './html-generator.js'\nexport { DataExtractor, extractGraphFromCase, extractGraphFromJson } from './data-extractor.js'\n\nimport { readFile } from 'node:fs/promises'\nimport { truncateGraph } from './graph-model.js'\nimport { generateHtml, writeVizHtml } from './html-generator.js'\n\nexport async function generateVisualization(opts: {\n  caseId?: string\n  dataFile?: string\n}): Promise<{ vizId: string; htmlPath: string }> {\n  let rawData: unknown\n\n  if (opts.dataFile) {\n    const content = await readFile(opts.dataFile, 'utf-8')\n    let parsed: unknown\n    try {\n      parsed = JSON.parse(content)\n    } catch {\n      throw new Error('Invalid transaction data. The input file must contain a JSON array of transaction objects with `from`, `to`, and `value` fields.')\n    }\n    const { extractGraphFromJson } = await import('./data-extractor.js')\n    rawData = extractGraphFromJson(parsed)\n  } else if (opts.caseId) {\n    const { extractGraphFromCase } = await import('./data-extractor.js')\n    const extracted = await extractGraphFromCase(opts.caseId)\n    if (extracted.nodes.length === 0) {\n      throw new Error('No Transaction Data. This case has no evidence with transaction data. Add evidence using `chain-insights evidence add` or provide a JSON file with `chain-insights viz --data <file.json>`.')\n    }\n    rawData = extracted\n  } else {\n    throw new Error('Provide either a case ID or --data <file.json>')\n  }\n\n  const data = truncateGraph(rawData as Parameters<typeof truncateGraph>[0])\n\n  const vizId = opts.caseId\n    ? `${opts.caseId}_${Date.now()}`\n    : `adhoc_${Date.now()}`\n\n  const title = data.metadata.caseId\n    ? `${data.metadata.caseId} - Money Flow`\n    : 'Ad-hoc Visualization'\n\n  const html = generateHtml(data, title)\n  const htmlPath = await writeVizHtml(vizId, html, opts.caseId)\n\n  return { vizId, htmlPath }\n}\n"],"mappings":";;;;;;AASA,eAAsB,sBAAsB,MAGK;CAC/C,IAAI;CAEJ,IAAI,KAAK,UAAU;EACjB,MAAM,UAAU,MAAM,SAAS,KAAK,UAAU,OAAO;EACrD,IAAI;EACJ,IAAI;GACF,SAAS,KAAK,MAAM,OAAO;EAC7B,QAAQ;GACN,MAAM,IAAI,MAAM,kIAAkI;EACpJ;EACA,MAAM,EAAE,yBAAyB,MAAM,OAAO,iCAAA,MAAA,MAAA,EAAA,CAAA;EAC9C,UAAU,qBAAqB,MAAM;CACvC,OAAO,IAAI,KAAK,QAAQ;EACtB,MAAM,EAAE,yBAAyB,MAAM,OAAO,iCAAA,MAAA,MAAA,EAAA,CAAA;EAC9C,MAAM,YAAY,MAAM,qBAAqB,KAAK,MAAM;EACxD,IAAI,UAAU,MAAM,WAAW,GAC7B,MAAM,IAAI,MAAM,6LAA6L;EAE/M,UAAU;CACZ,OACE,MAAM,IAAI,MAAM,gDAAgD;CAGlE,MAAM,OAAO,cAAc,OAA8C;CAEzE,MAAM,QAAQ,KAAK,SACf,GAAG,KAAK,OAAO,GAAG,KAAK,IAAI,MAC3B,SAAS,KAAK,IAAI;CAStB,OAAO;EAAE;EAAO,UAAA,MAFO,aAAa,OADvB,aAAa,MAJZ,KAAK,SAAS,SACxB,GAAG,KAAK,SAAS,OAAO,iBACxB,sBAG0C,GAAG,KAAK,MAAM;CAEnC;AAC3B"}

package/docs/knowledge-exports.md

@@ -1,204 +0,0 @@
-# Knowledge Exports
-
-Chain Insights workspaces are Obsidian-compatible vaults. Normal local
-investigation work happens in the workspace; exports are portable, redacted,
-and shareable bundles for partner handoff, LLM Wiki ingestion, and archive.
-
-Chain Insights can export a verified case as a local knowledge bundle for LLM
-Wiki, Codex, Claude Code, ChatGPT, Obsidian, and any agent that can read a
-folder of Markdown and JSON files.
-
-The export is local-first. Chain Insights writes files under your initialized
-workspace and does not upload the case anywhere by itself.
-
-## Install Viewers And Agent Tools
-
-Install Chain Insights:
-
-```bash
-npm install -g chain-insights
-cia --version
-```
-
-Install Obsidian when you want a human vault UI:
-
-- Windows and macOS: download the installer from
-  <https://obsidian.md/download> and open it.
-- Linux AppImage: download the AppImage from <https://obsidian.md/download>,
-  then run:
-
-```bash
-chmod u+x Obsidian-<version>.AppImage
-./Obsidian-<version>.AppImage --no-sandbox
-```
-
-- Linux Flatpak:
-
-```bash
-flatpak install flathub md.obsidian.Obsidian
-flatpak run md.obsidian.Obsidian
-```
-
-Install LLM Wiki when you want an agent-native research wiki on top of the
-exported case:
-
-```bash
-# Claude Code
-claude plugin install wiki@llm-wiki
-
-# OpenAI Codex
-codex plugin marketplace add nvk/llm-wiki
-# Then open /plugins, enable "LLM Wiki", and use @wiki.
-```
-
-For any other LLM agent, install the portable LLM Wiki instructions in the
-project where the agent runs:
-
-```bash
-curl -sL https://raw.githubusercontent.com/nvk/llm-wiki/master/AGENTS.md \
-  > AGENTS.md
-```
-
-You do not need Obsidian or LLM Wiki to read an export. The bundle is plain
-Markdown plus JSON, so editors and agents can consume it directly.
-
-## Create A Case Export
-
-Start from a Chain Insights workspace:
-
-```bash
-mkdir -p ~/work/chain-insights-investigations
-cd ~/work/chain-insights-investigations
-cia init .
-```
-
-Open a case and run investigation tools with `--case` so evidence, reports, and
-graph artifacts stay attached to the case:
-
-```bash
-cia case open "Exchange deposit clustering" \
-  --tags aml,bittensor \
-  --description "Trace source funds into exchange entities"
-```
-
-After evidence exists, verify and export:
-
-```bash
-cia case evidence verify <case-id>
-cia case export <case-id> --target obsidian-llmwiki --mode private
-```
-
-The default output path is:
-
-```text
-published/<case-slug>/
-```
-
-Inspect the bundle:
-
-```bash
-find published/<case-slug> -maxdepth 3 -type f | sort
-```
-
-## Output Files
-
-The export writes:
-
-```text
-README.md
-Case.md
-Agent Console.md
-LLMWIKI.md
-llms.txt
-manifest.chain-insights.json
-graph.chain-insights.json
-Graph.canvas
-Entities/
-Evidence/
-Prompts/Codex.md
-Prompts/Claude-Code.md
-Prompts/ChatGPT.md
-Sources/evidence-manifest.md
-Sources/reports-index.md
-```
-
-Use `manifest.chain-insights.json` as the machine-readable source of truth for
-case ID, export mode, verification status, file hashes, and redaction warnings.
-Use `graph.chain-insights.json` for node/edge import, and `Graph.canvas` for an
-Obsidian Canvas view of the same graph.
-
-## Open In Obsidian
-
-1. Open Obsidian.
-2. Open the vault switcher.
-3. Select **Open folder as vault**.
-4. Choose `published/<case-slug>/`.
-5. Start with `Case.md`, `Agent Console.md`, and `Graph.canvas`.
-
-Obsidian treats the export directory as a normal vault. It may create a local
-`.obsidian/` settings folder inside the export; that file is viewer state, not
-Chain Insights evidence.
-
-## Load Into LLM Wiki
-
-LLM Wiki stores topic wikis under `~/wiki/` by default and can ingest local
-files. A simple Chain Insights flow is:
-
-```text
-/wiki init chain-insights-cases
-/wiki:ingest /absolute/path/to/published/<case-slug>/LLMWIKI.md --wiki chain-insights-cases
-/wiki:ingest /absolute/path/to/published/<case-slug>/Case.md --wiki chain-insights-cases
-/wiki:ingest /absolute/path/to/published/<case-slug>/Agent\ Console.md --wiki chain-insights-cases
-/wiki:ingest /absolute/path/to/published/<case-slug>/manifest.chain-insights.json --wiki chain-insights-cases
-/wiki:ingest /absolute/path/to/published/<case-slug>/graph.chain-insights.json --wiki chain-insights-cases
-/wiki:compile --wiki chain-insights-cases
-```
-
-For larger cases, drop selected exported files into the topic wiki inbox and run
-LLM Wiki ingestion from there. Keep the original `published/<case-slug>/`
-directory unchanged so the Chain Insights manifest hashes remain auditable.
-
-## Use With Codex, Claude Code, Or ChatGPT
-
-For coding-agent sessions, open or attach `published/<case-slug>/` and start
-with this instruction:
-
-```text
-Read Case.md, Agent Console.md, LLMWIKI.md, manifest.chain-insights.json, and
-graph.chain-insights.json first. Treat manifest.chain-insights.json and
-Sources/evidence-manifest.md as canonical. Preserve full blockchain addresses
-exactly unless this is a public redacted export. Use Chain Insights MCP tools
-for fresh graph facts when available.
-```
-
-For ChatGPT, upload the smallest useful subset first:
-
-- `Case.md`
-- `Agent Console.md`
-- `manifest.chain-insights.json`
-- `graph.chain-insights.json`
-- selected files from `Evidence/` and `Entities/`
-
-## Export Modes
-
-Use the least-shareable mode that fits the audience:
-
-| Mode | Use it for |
-| --- | --- |
-| `private` | Local analyst work. May include full addresses and sensitive notes. |
-| `partner` | Controlled partner handoff. Review the bundle before sharing. |
-| `public` | Demos and public writeups. Addresses are aliased and redaction metadata is written to the manifest. |
-
-Do not share `private` exports outside the investigation team.
-
-## MCP Tool Flow
-
-Agents connected through the Chain Insights MCP proxy can create the same
-bundle without shelling out:
-
-1. Call `case_verify_evidence` for the case.
-2. Call `case_export` with `case_id`, `target=obsidian-llmwiki`, and
-   `mode=private`.
-3. Open the returned `outputDir`, then read `Agent Console.md` first.
-
-The MCP tool and CLI command write the same file format.

package/docs/obsidian-vault.md

@@ -1,130 +0,0 @@
-# Obsidian Vault Workflow
-
-Chain Insights workspaces are Obsidian-compatible investigation vaults.
-Obsidian is the first-class human review UI, while Chain Insights case files,
-evidence manifests, reports, graph JSON, and exports remain plain local files.
-Obsidian plugin is not required.
-
-## Install
-
-Install Chain Insights:
-
-```bash
-npm install -g chain-insights
-cia --version
-```
-
-Install Obsidian when you want the vault UI:
-
-- Windows and macOS: download the installer from
-  <https://obsidian.md/download> and open it.
-- Linux AppImage: download the AppImage from <https://obsidian.md/download>,
-  then run:
-
-```bash
-chmod u+x Obsidian-<version>.AppImage
-./Obsidian-<version>.AppImage --no-sandbox
-```
-
-- Linux Flatpak:
-
-```bash
-flatpak install flathub md.obsidian.Obsidian
-flatpak run md.obsidian.Obsidian
-```
-
-## Create An Investigation Vault
-
-Create a normal local folder and initialize it:
-
-```bash
-mkdir -p ~/work/chain-insights-investigations
-cd ~/work/chain-insights-investigations
-cia init .
-cia obsidian open .
-```
-
-If the app association is not available, open Obsidian manually, choose
-**Open folder as vault**, and select the initialized workspace folder.
-
-The workspace includes Chain Insights runtime metadata, case state, generated
-vault notes, Obsidian settings, evidence, entities, canvases, reports, and
-published handoff bundles. The files remain readable in any editor.
-
-## Work A Case
-
-Open a case:
-
-```bash
-cia case open "Exchange deposit clustering" \
-  --tags aml,bittensor \
-  --description "Trace source funds into exchange entities"
-```
-
-Run investigation tools with `--case` so evidence and report pointers attach to
-the case:
-
-```bash
-cia mcp trace-victim-funds \
-  --network bittensor \
-  --victim-addresses 5GTjfJaLpBNrgybhY24NqhDnKW9r94z72RSYLxeodxJfSkj5 \
-  --case 1
-```
-
-Refresh live vault notes whenever case evidence, dossiers, or sessions change:
-
-```bash
-cia case vault refresh 1 --force
-```
-
-Use Obsidian for review of `Home.md`, case notes, entity notes, evidence notes,
-and canvases. Use the CLI or MCP tools for live GraphRAG MCP reads and evidence
-capture.
-
-## VS Code And Agent Operator Setup
-
-Open the same folder in VS Code, Codex, Claude Code, or another local agent.
-The agent and Obsidian should operate over the same workspace path:
-
-```bash
-code .
-codex
-claude
-```
-
-Agents should read the workspace notes, case files, evidence manifests, graph
-JSON, and report pointers before running new tools. When a result changes the
-case, refresh the vault notes again:
-
-```bash
-cia case vault refresh 1 --force
-```
-
-## LLM Wiki Overlay
-
-LLM Wiki is an optional overlay for agent-native retrieval and compiled case
-knowledge. Use the live workspace for normal local work, then export a selected
-case when you need an ingestion bundle:
-
-```bash
-cia case evidence verify 1
-cia case export 1 --target obsidian-llmwiki --mode private
-```
-
-The exported `published/<case-slug>/LLMWIKI.md`,
-`manifest.chain-insights.json`, `graph.chain-insights.json`, and Markdown notes
-can be ingested into an LLM Wiki topic while the original workspace remains the
-auditable source.
-
-## Sharing
-
-Normal local investigation work stays in the initialized vault. Export only
-when you need sharing, partner handoff, LLM Wiki ingestion, or archive.
-
-Use `private` only inside the investigation team. Use `partner` for controlled
-handoff after review. Use `public` for demos and public writeups where address
-aliasing and redaction metadata are required.
-
-Do not share `.chain-insights/` runtime state, local credentials, wallet
-material, debug tokens, or unreviewed private notes. Review generated bundles
-before sending them outside the team.

package/skills/ci-case/SKILL.md

@@ -1,43 +0,0 @@
----
-name: ci-case
-description: "Manage Chain Insights investigation cases (open, activate, suspend, close)"
-allowed-tools:
-  - Read
-  - Write
-  - Bash
----
-
-# /ci-case
-
-Manage investigation cases. Open new cases, switch active cases, suspend work-in-progress, or close completed investigations.
-
-Run case commands from an initialized Chain Insights workspace. If
-`.chain-insights/workspace.json` is missing, initialize the current project
-folder first:
-
-```bash
-cia init .
-```
-
-Cases live under the workspace `cases/` directory. Global `~/.chain-insights`
-is reserved for config, cache, wallet, and installed skills; it is not the
-investigation root.
-
-## Usage
-
-- `/ci-case open <name>`: open a new workspace-local investigation case.
-- `/ci-case status`: show active and open cases in the current workspace.
-- `/ci-case suspend`: suspend the active workspace case.
-- `/ci-case close <name>`: close a workspace case.
-
-## CLI Equivalents
-
-```bash
-cia case open "<name>" --tags "<network-or-topic>"
-cia case list
-cia case show <case-number>
-cia case session start <case-number> "session title"
-cia case session end <case-number> --findings "..." --next-steps "..."
-```
-
-Use numbered selectors from `cia case list` when a command accepts a case.