HeliosDatabase

Configure a running plugin's behaviour without restarting via `PUT/GET/DELETE /admin/kv/<plugin>/<key>`. Per-plugin namespaced state. Use when the user says "set the budget", "configure the residency map", "/admin/kv", "plugin runtime config", or wants to push a new mask rule live.

Bring up any of the 22 v0.4.0 demos under `demos/v0.4.0/<n>/`. Each ships a `demo.sh up\|run\|down` and a self-contained `docker-compose.yml`. Use when the user says "run a demo", "demo.sh", "show me X working", "anomaly detection demo", or asks for a runnable example.

Deploy HeliosProxy via Kubernetes operator (CRD), Terraform provider, or Pulumi. Quick-start per surface and which to pick when. Use when the user says "operator", "Kubernetes", "CRD", "HeliosProxy resource", "Terraform", "TF provider", "Pulumi", "IaC".

Install HeliosProxy from crates.io or build from source. Pick feature flags. Verify with `--version`. Use when the user says "install heliosproxy", "set up the proxy", "cargo install heliosdb-proxy", or hits a "command not found" on `heliosdb-proxy`.

Start the HeliosProxy daemon — `heliosdb-proxy --config proxy.toml` or all-CLI-args mode. Use when the user says "start the proxy", "run heliosproxy", "set up the daemon", "systemd unit", or hits "connection refused" against the admin port.

Top-level navigation for HeliosProxy. Auto-loads when the user mentions "heliosproxy", "helios proxy", or pastes its admin REST output / config / log lines. Routes to one of 21 domain skills (install, start, config, shutdown, connect, topology, health, chaos, switchover, time-travel, shadow-execute, anomaly, plugin-{pack,load,kv,catalog}, edge, demo-{up,down}, release, iac). Use this skill to find the right skill before going deep.

Cut a HeliosProxy release. Bump version → CHANGELOG → commit → tag → push. The `crates-io.yml` workflow runs `cargo publish` on tag push. Use when the user says "release", "cut a version", "publish to crates.io", "tag a release", "bump version".

Catalog of the eight first-party plugins (cost-governor, ai-classifier, token-budget, llm-guardrail, pgvector-router, column-mask, audit-chain, residency-router). What each fires on, what it gates, what KV keys it reads. Use when the user says "which plugin does X", "I need to mask PII", "I need to gate AI traffic", "guardrails", "how does residency-router decide".

Install HeliosDB-Nano via crates.io or build from source. Lists every cargo feature flag (code-graph, code-embed, mcp-endpoint, fips, ha-full, etc.), shows feature-matrix recipes, initializes a data directory, and verifies the install. Use this when the user has not yet run heliosdb-nano on this machine, or when adding a feature that requires a custom build.

Database branching in HeliosDB-Nano — ephemeral fork-test-discard sandboxes. Create a branch from main (or any other branch, with an optional `AS OF` historical anchor), make isolated changes, validate, then discard. The primary pattern for agent sandboxes, migration rehearsals, A/B experiments, and short-lived "what if" workspaces. MERGE back exists but its conflict detection is currently unreliable — prefer discarding and re-applying validated SQL to main. Use this when the user says "branch", "fork the database", or wants to try a destructive change without affecting production data.

Run HeliosDB-Nano as an MCP (Model Context Protocol) server so AI agents (Claude Code, Codex CLI, MCP-aware tools) can query, write, branch, time-travel, and search via JSON-RPC 2.0. Covers stdio, HTTP, and WebSocket transports; the 16-tool catalog (10 DB-backed + 6 in-process RAG); and wiring into Claude Code via `claude mcp add`. Use this when the user wants an LLM agent to operate the database directly through tool calls instead of writing SQL.

Top-level navigation for HeliosDB-Nano. Auto-loads when user mentions "heliosdb", "heliosdb-nano", or pastes its CLI/REPL output. Routes to one of 16 domain skills (install, connect, schema, query, transactions, branches, time-travel, backup, vector, code-graph, graph-rag, mcp, server, deploy, observability, migrate). Use this skill to find the right skill before going deep.

Query historical state in HeliosDB-Nano. Every read can be anchored to a past timestamp via `AS OF TIMESTAMP '…'`; the engine returns the snapshot as it was at that moment. Useful for audit/forensics, "what changed", reverting after a bad UPDATE, and comparing aggregates across time. Use this when the user says "what did this look like yesterday", "before that bug", "show me the state at 10am", or "diff against last week".

The pre-merge validation methodology used in this repo. Required before merging any non-trivial change — bug fixes, optimizer passes, storage tweaks, parser changes, anything user-visible. Eight phases: branch + implement, targeted unit tests, integration regression, targeted feature bench, cross-feature regression, head-to-head OLTP comparison vs main, validation report, release. Use this when the user says "merge this", "this is ready to ship", "before merging", or asks for a perf gate before a release.

Index a repository's source code as an AST symbol graph in HeliosDB-Nano. Covers grammar registration (Rust / Python / TypeScript / Go / Markdown / SQL), full-project indexing (`code_index`), LSP-shaped queries (`lsp_definition`, `lsp_references`, `lsp_call_hierarchy`, `lsp_hover`), the git-hook helper (`heliosdb-nano code-graph hook`), and the `_hdb_code_symbols` / `_hdb_code_symbol_refs` tables. Use this when the user wants AI-grade "where is this defined / used / called" queries across a codebase, or wants to wire a code-graph into a Claude Code / MCP workflow.

Migrate an existing app to HeliosDB-Nano with minimal source changes. Covers SQLite (Python `sqlite3` drop-in via the `heliosdb_sqlite` SDK), PostgreSQL (any PG-wire client works unchanged), and MySQL (`--mysql` listener for PHP/WordPress). Documents the dialect-autodetect parser, accepted SQLite-isms (`?` placeholders, `INSERT OR REPLACE/IGNORE`, `INTEGER PRIMARY KEY AUTOINCREMENT`, `sqlite_master`, `PRAGMA *`), and the gotchas that still require code changes. Use this when the user says "port this from sqlite", "switch from sqlite3 to Helios", or "drop-in replace Postgres / MySQL".