keel

A local-first monitor for investments whose value comes from their terms, not from a market price. The first instrument it tracks is a market-linked note: a worst-of autocall with a call level, observation dates and a barrier.

keel shows your instruments, what each term says and where that term came from, the next date that matters, and how far the underlyings sit from the call level and the barrier. When there is no evidence of a value, it says so instead of inventing one.

Status: pre-alpha. This repository currently holds its rules, review process, slice specs, and the verify gate. @keel/core loads an mln-terms/0.1 or mln-terms/0.2 file and reports which payoff terms are verified.

Not advice. keel is information only. It is not investment, tax or legal advice, and your offering documents govern. See DISCLAIMER.md.

How it is built

Every change is one slice, one pull request:

• A planner (Claude) writes the spec in docs/specs/.
• A builder (Cursor) implements it.
• Reviewers from two other vendors (Claude Code, then Codex) review it cold and adjudicate each other's findings.
• A human merges.

The rules are in AGENTS.md; the review procedure is .claude/skills/keel-pr-review/.

Privacy

Your data lives in a folder on your machine, outside this repository. The default build makes no network requests. Every fixture in this repository is synthetic.

Quickstart

Install, then run the gate:

pnpm install --frozen-lockfile
pnpm verify

pnpm verify runs typecheck, package tests, tooling self-tests, the tripwire, the network check, the determinism check, copy lint, and the import boundary. It runs every step even after one fails, names each failed step, and exits nonzero if any step failed.

Run one step:

pnpm verify:typecheck
pnpm verify:tests
pnpm verify:tooling
pnpm verify:tripwire
pnpm verify:network
pnpm verify:determinism
pnpm verify:copy
pnpm verify:boundaries

Package tests, including a file-name filter:

pnpm --filter @keel/core test
pnpm --filter @keel/core test <pattern>

A filter that matches no test file fails the run. Tooling self-tests, with an optional filter matched against the test file's path (pnpm test:tooling -- tripwire runs tools/acceptance/test/tripwire.test.mjs alone):

pnpm test:tooling
pnpm test:tooling -- <filter>

Fixture registry:

pnpm fixtures:regen
pnpm -s fixtures:trees

On Linux CI, pnpm verify runs inside a network namespace with no route out, and a probe in that namespace checks that an outbound fetch and a raw connect both fail. On macOS, the in-process network guard is the check that runs.

The CI evidence check needs the gh command and is not part of pnpm verify:

pnpm test:ci-evidence -- --success-run <id> --failure-run <id>

License

Apache-2.0.