Skip to content
View velvetmonkey's full-sized avatar

Highlights

  • Pro

Block or report velvetmonkey

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
velvetmonkey/README.md
Ben Cassie: Rules decide, models explain. Nothing silently overwrites a conflict.

Rules decide, models explain. Nothing silently overwrites a conflict.

A home for my personal projects and research: deterministic systems, approval gates and Lean 4 proofs.

Entity Desk · Seal · Research foundation · What checked means

Entity Desk

Entity Desk is a current project, built around one rule: deterministic software finds conflicts, and a model only explains them.

  • Stack and sources: C#/.NET over public open data (GLEIF, SEC EDGAR and Wikidata).
  • Method: A deterministic reconciliation pass compares records and highlights disagreements between sources. A language model explains each disagreement in plain terms. Nothing silently overwrites a conflict.
  • First feature: Deal Watch.
  • Status: Private repository, not yet public. Repository link, architecture notes and a Deal Watch walkthrough will occupy this slot once the project is published.

Seal

Seal is the first shipped instance of the same thesis: deterministic rules enforce the boundary, with signed decision receipts when the receipt directory is writable.

It is a local MCP approval gate for Claude Code. Protected tool calls pause for exact-call inspection, run at most once after approval, refuse calls that drift from what was approved and write signed decision receipts when the receipt directory is writable. Seal is a gate, not a sandbox. Checking a receipt does not establish that the recorded tool effect happened.

Research foundation

Lean 4 proofs state their model, axiom footprint and non-claims. SafeMesh connects Rust CRDTs to Lean convergence proofs through differential tests; bindings and wire encoding remain tested engineering. I co-authored Observers Are All You Need and contributed Lean proofs of stated propositions, not OPH's wider claims. My related paper is Barrier asymmetry in self-modelling gradient flow: a witness-corrected free energy. Witness Lab and Reasoning compiler test claims with explicit failure cases.

Lean 4 proof corpus index

What checked means

Claims need receipts. Lean proofs apply only to their stated models and axiom footprints. Differential tests, finite conformance checks, numerical demos and deployed software each carry a different scope. Non-guarantees stay visible alongside the claims.

For the shipped tools, start with Seal's guarantees and non-guarantees and SafeMesh's proof boundary.

Website · ORCID · Zenodo

Pinned Loading

  1. seal seal Public

    Local MCP approval gate for Claude Code: exact-call prompts, at-most-once approval, drift refusal and signed decision receipts. A gate, not a sandbox.

    JavaScript

  2. safemesh safemesh Public

    Five CRDTs (G-Set, G-Counter, PN-Counter, OR-Set, RGA/Text) in no_std Rust with C ABI, WASM/TypeScript and Python bindings, tied to Lean 4 convergence proofs by differential tests. Apache-2.0.

    Rust

  3. attention-lean attention-lean Public

    Lean 4 / Mathlib formalisation of hard and soft attention expressivity over finite Boolean cubes: exact head-count bounds carried from argmax to softmax at the Boolean-output level.

    Lean