foldsig.

A fold-signature format — describe a thing as a recipe, not a snapshot.

A fold-signature is an ordered fold-DAG on a prime spine, from a common seed: a program that generates the object, not a picture of it. An STL is a surface; this is the construction. The format precedes any hardware that would read it — and its worth is checkable now, in software, by three gates.

The three gates

1 · Round-trip

serialize → parse → serialize is byte-identical, so the recipe is unambiguous — a quine, it can't drift.

2 · Witness

the recipe closes — it resolves at least κ (= φ⁻¹ ≈ 0.618) of what it generates. Generation outrunning resolution runs away, never settling into a definite thing.

3 · Compose — non-masking

two signatures fold into a valid larger one only if every part independently closes — a stable half can never carry a runaway half, even when the aggregate would look fine. A build is only as sound as its weakest part.

Use

import { validate, compose, hash } from 'foldsig';

validate(sig)   // { shape, roundtrip, witness:{stable,forge,resolve,ratio}, hash, valid }
compose(a, b)   // { ok:true, signature, hash }  — or  { ok:false, part, aggregateStable }
hash(sig)       // 32 hex chars — the recipe's true name (content-addressed)

What it is: real, tested, composable software with genuine guarantees — round-trip determinism, non-masking composition, content-addressing. What it isn't: a machine that folds anything into matter. It describes a fold; it condenses nothing. "Valid" means internally consistent, closes, composes — not "has been built."