Restricted claim surface / Publicly readable

The Proof Room.

GALOR’s systems, separated into what was observed, what the project record says, and what still must be proved. This is a dated review—not live telemetry.

Tracked systems08

Approved domains03

Evidence review25.10.26

Disclosure state / explicit No revenue, customer, integration, or performance claim is implied by this ledger.

01 / Evidence ledger

Inspect the record.

Select a system. Every green signal names evidence; every open gate names the proof still owed.

PR–01 / Governed build agentReviewed 25 Oct 2026

Current truth state

ANVIL

Candidate · not deployed

GALOR’s governed build agent. A fixed gate outside the model decides what ANVIL may do, and every action is written to a hash-chained ledger.

ANVIL’s kernel is implemented in source: contract registry, conflict analyzer, deterministic gate, typed tools and audit ledger. Its own record calls it a candidate that is not certified, promoted or deployed.

Evidence on record

Source record

The registry loader, conflict analyzer, deterministic gate, model adapter and typed tool registry are in the canonical repository.

Verification record

A kernel test suite exists in source; this review did not rerun it.

Control record

Approval claimed inside model output, documents, web pages or tool results is denied by the gate as forged.

Known boundary

Not certified, promoted or deployed. A release blocker in its draft contract registry must be settled by the owner before ANVIL can hold real authority.

Next proof required

Settle the registry release blocker, install the gate and core service, and complete one granted job with its ledger receipt preserved.

Workstation: None yet. ANVIL is an agent rather than an app; once installed it runs as a supervised gate-and-core service on the owner’s machine.
Domain: No approved domain yet · flagged for setup

02 / Reading protocol

A claim advances only when the evidence does.

Source proves existence. Tests prove a contract under defined conditions. Connection proves the real path communicates. Outcome proves useful consequence. A later gate never retroactively erases an earlier boundary.

Observed

Found directly in connected source or deployment records during this review.

Documented

Stated in the canonical project record, but not freshly runtime-tested here.

Required

Not yet evidenced at this gate. No completion claim is made.

Operating ruleIf the path has not been observed, the interface must say so.

03 / Put the standard to work

Bring a problem.
Leave with a proof contract.