WORLD LOOM

World Loom is a machine action assurance kernel. Its fundamental object is not a diff or a ticket but a decision record: what a machine was permitted to do, under which policy, on what evidence — and a verdict another party can replay and independently verify. Verification fails closed: a change with no test commands and no invariants returns insufficient evidence, never approval.

The system ships as a Python package and the wloom command line — wloom verify for repository and change verification, wloom diff for base-to-candidate comparison, wloom replay for auditing a stored report — and World Loom Edge, a local gateway for machine tool calls. It is open-core verification software: it claims no zero regressions, no certifications, and no autonomy it has not evidenced. The project is in active development.

Risky software changes are approved on argument, not evidence. Reviewers read diffs, CI prints green, and the record of why a machine was allowed to act on real systems scatters across threads, tickets, and logs nobody can replay.

The gap is assurance. When a machine — a migration script, an agent, a pipeline — is permitted to act, there should be a durable answer to what it was allowed to do, why, and under which policy. Ordinary tooling records what happened; it cannot produce a fail-closed verdict or a verifiable receipt.

Fail closed, always. A verification with no test commands and no invariants returns insufficient evidence — never approval. The verdict is a machine-readable decision carrying an audit digest, invariant results, and command receipts.

Deny by default at the edge. World Loom Edge proxies the tool lifecycle with explicit tool and argument policy, approval hooks, bounded messages, and sandboxed execution that keeps sensitive work in the customer's environment.

Receipt everything. Every decision lands in an append-only, hash-chained ledger with redacted audit metadata, inclusion proofs, and exportable audit packs a third party can verify independently.

A stdlib-only Python runtime exposing two surfaces: the wloom CLI and the world_loom.product_api embedding interface, whose verify_change and verify_repository functions return plain JSON-safe reports. Repository verification snapshots base and candidate trees, rejects forbidden files, symlinks, and oversize inputs, computes changed-file manifests, and runs only allowlisted commands in the candidate tree. Policy packs are declarative TOML and gate message bounds, timeouts, environment inheritance, and sandbox behavior. Execution is local, temporary, network-denied, and credential-free by default.