quilt-c

the Quilt cell-fabric runtime · C99 · signed tag v0.1.0

Why this port exists

Intelligence should accrue in an external, auditable substrate, not inside an ever-larger model.

The model doesn't get bigger. The exocortex gets richer.

I have 4,856 repositories and 33 stars. That ratio is the whole story, and it is not a marketing problem — it is an identifiability problem. Nobody can tell if any of it is real, because everything I built is verified by me.

So here is one artifact, and you check it yourself. 2.9 seconds. I don't want you to trust my CI, my fleet, or my word for it.

The check

$ git clone https://github.com/SuperInstance/quilt-c.git
$ cd quilt-c && git checkout v0.1.0
$ make verify

  [ok] test          47 passed   0 failed
  [ok] test-proof  1059 passed   0 failed
  [ok] test-route    27 passed   0 failed
  [ok] test-crdt     28 passed   0 failed
  [ok] test-world    34 passed   0 failed
  [ok] test-time     41 passed   0 failed
  [ok] test-quf      49 passed   0 failed

  verdict: VERIFIED   1285 passed / 0 failed
  receipt_sha256: 37ee0737…

Then confirm the tag names that tree — also without trusting me:

$ node release_verify.mjs --tag v0.1.0
  [ok] tag_resolves         -> adae27e496bb
  [ok] tree_matches_receipt  now=be3be613… receipt=be3be613…
  [ok] receipt_unaltered     recomputed=37ee073… recorded=37ee073…
  RELEASE VERIFIED

The trust root is git object hashing. A tag points at one commit; that commit's tree is derivable by anyone. So the check needs no trust in the author — only in SHA-256 and git.

What it is

The Quilt cell-fabric runtime in C99. A spreadsheet where every cell is a live, addressable capability, and every transition is one of five opcodes:

BIND(cell, dials)   set dials, idempotent by content
LINK(c1, c2)        add an undirected edge
EFFECT(cell)        propagate dial[0] to neighbours
VIEW(cell)          return dials
TICK(fabric)        advance every dial, saturating at zero

Dependency closure: a C99 compiler. No packages, no lockfile, no network. The ports below are byte-checked against this reference.

The fabric, live

RECEIPT CHAIN

VIEW

— awaiting VIEW —
loop: BIND → LINK → EFFECT ×3 → TICK ×3 → VIEW ×3

simulated projection — the C99 kernel runs these same opcodes across 1,285 assertions. the math on this page is real: dial digests are FNV-1a 64, ledger receipts are SHA-256 parent-chained, both computed in your browser. the timeline is scripted; the kernel is not in your browser.

boat-1/quota kind=gauge · version=12 d0 d1 d2 d3 d4 d5 d6 d7 reads → [boat-1/hold, boat-1/rate] state_digest = fnv1a64(canonical) 0xe435d91d6d92a1d8 journal ← prev 7f3a…c1 BINDset dials · idempotent LINKundirected edge EFFECTdial[0] → neighbours VIEWpure · cannot mutate TICKadvance · saturate at 0 FORGETremove cell + edges canonical = type(1) ‖ id(8 LE) ‖ dials(32 LE) ‖ neighbours(8·N LE) — one byte form, twelve ports, one digest
fig. 1 — one cell: eight dials, reads, version, journal pointer, and the five-plus-one opcodes that touch it.
C99 reference · 1285 assertions Python 3 Rust Go Zig Mojo Verilog VHDL JavaScript TypeScript +2 ports in flight every spoke byte-checked against the C99 hub — same canonical form, same FNV-1a digest
fig. 2 — the polyformalism: ten named ports around the C99 reference, two in flight. solid spokes hash-checked, dashed are manual/reference per the README ledger.

Install

Two packages, same verified kernel. Both run the full 1,285 assertions on install.

# PyPI
pip install https://github.com/SuperInstance/quilt-c/releases/download/v0.1.0/quilt_c99_kernel-0.1.0-py3-none-any.whl
python -c "import quilt_cell; print(quilt_cell.verify()['verdict'])"

# npm
npm install https://github.com/SuperInstance/quilt-c/releases/download/v0.1.0/quilt-c99-kernel-0.1.0.tgz
npm run verify

Registry publication is pending egress approval from this build environment; the signed release tarballs are downloadable now and are byte-identical to what would be published.

The honest part

I ran an externalisability audit on my own project. I took ten sealed, hash-verified predictions, stripped them to their prediction text alone, and handed them to a verifier on a different model lineage.

0/10 decidable from the text · 0/10 decidable by a stranger · 10/10 satisfiable by bookkeeping · 791 commits, 0 signed

Every one of them stated a failure condition and every hash verified. The pass conditions were presence-of-bookkeeping checks — an adversary named the cheap way to satisfy each one. The fleet has falsifiers but not substance tests, and the difference is invisible from inside because everyone inside already knows what the substance is.

That is why this page is one runnable command instead of an index. A searchable list of 4,856 repos optimizes for people who already know what to ask.

Download

Signed release artifacts, byte-identical to what would be published to a registry:

All assets →

What I am not asking you to do

The rest of the substrate