A11oy proof registry.
Inspect runtime truth, receipt verification, assurance evidence, benchmarks, source, and public-estate metadata without relying on the product interface. A link proves location and a probe proves reachability only; neither proves capability.
Six independent ways to inspect the estate.
These links expose public evidence directly. Dynamic state remains labeled at the source; an HTTP response alone is never promoted to proof of quality or readiness.
Read the deployed revision and honesty posture from the product runtime.
/api/a11oy/v1/honest VerifierReceipt verificationOpen the public verifier before relying on a receipt or subject digest.
a-11-oy.com/verify AssuranceControls and evidenceInspect the assurance surface and its linked evidence rather than a marketing summary.
a-11-oy.com/assurance Public sourceGoverned-agent benchmarkReview the benchmark schema, cases, and implementation in versioned source.
benchmarks/governed-agent-bench Public sourceSource and CIInspect implementation history, checks, releases, and open review state.
github.com/szl-holdings/a11oy Public registryModels, datasets, and SpacesInspect the current public Hub inventory; runtime stage is transport evidence only.
huggingface.co/SZLHOLDINGSOne backbone. Every claim accountable.
Alloy conducts agents across providers the way a signals officer runs a net — nothing transmits without a callsign, a label, and a log.
Doctrine-gated inference
Agent outputs pass doctrine gates before they ship: honest labels enforced, overclaims blocked, exceptions fail closed without leaking internals.
Receipts, not vibes
Work products can carry DSSE-signed receipts with provenance you can verify offline — the claim chain is the product.
Estate control plane
Models, kernels, datasets, and live consoles across the SZL estate are orchestrated as one governed surface with a single honesty canon.
Brain, body, proof, and control — one navigable surface.
The estate stays modular at the source and unified at the interface. Each card opens a public Hub listing. REPORTED identifies listing metadata only; runtime state, capability, and availability are not checked in this section.
SZL-Khipu-1.5B
The flagship governed retrieval navigator, with public weights, adapter, schema, receipts, and GGUF path.
Open model line →Sovereign router
The public Hub listing for the routing interface and its stated provider-status and bounded-inference scope.
Open router →Living anatomy
The body map for organs, contracts, trust boundaries, and the controller outside model weights.
Open anatomy →Holographic estate
A spatial front door into the wider public estate, built as a distinct interface over shared evidence.
Open holographic →Governed kernels
Reusable verifier and policy components with explicit source, license, and provenance boundaries.
Open kernel suite →A11oy command surface
The public Hub listing for the control-plane interface and its stated formulas, inventory, governance, and route scope.
Open control plane →How a claim earns its label
The pipeline is deliberately boring — and deliberately auditable.
An agent produces a claim, artifact, or action proposal.
Doctrine guards check labels, banned tokens, and overclaim patterns.
Qualifying artifacts get DSSE receipts with subject digests.
Surfaces ship with the label visible — UNKNOWN stays UNKNOWN.
Anyone can re-check the receipt chain — trust ceiling 0.97, never blind.
The public artifact registry, consolidated.
Search reported model, dataset, collection, and bucket listings without leaving the flagship. Executable Spaces and Killinchu-named resources are outside this evidence inventory.
REPORTED means point-in-time public Hub listing metadata only. It does not prove capability, quality, safety, data rights, or deployed equivalence.
The governed estate
Alloy is the conductor; these are the sections of the orchestra.