Hugging Face's logo
Activity Feed Request to join this org

AI & ML interests

a11oy.net

Recent Activity
betterwithage  updated a Space about 6 hours ago
SZLHOLDINGS/README
betterwithage  updated a Space about 7 hours ago
SZLHOLDINGS/anatomy
betterwithage  updated a Space about 7 hours ago
SZLHOLDINGS/sda
View all activity

Organization Card
Community About org cards
Skip to main content
SZL HOLDINGS
Governed AI infrastructure

HISTORICAL

Autonomy, under authority.

Models, software, and evidence for systems that must explain, constrain, and verify action.

  • SOURCE-BOUND
  • EVIDENCE-SCOPED
  • NO IMPLIED AUTHORIZATION
Explore the portfolio Inspect evidence View source
Start with intent

One front door. Three useful routes.

Investors, builders, and evaluators need different depth. Every route ends at source and current evidence, not copied green status.

Investor Understand the company See the category, product boundaries, research lineage, and diligence evidence. Open company profile → Developer Build from contracts Choose an artifact type, inspect exact source, then reproduce the integration path. Read documentation → Evaluator Verify before inference Separate artifact type, evidence class, runtime state, and action authority. Open current sources →
Hugging Face portfolio

Artifacts named for what they are.

Repository type is a storage and discovery choice. It does not by itself prove trained weights, production readiness, or authorization.

Weights Models and adapters Exact base lineage, files, evaluation, runtime envelope, and autonomy boundary. Inspect Khipu → Software Substrates and kernels Source, manifests, meters, and governance packages. No trained weights implied. Inspect substrate → Evidence Datasets and receipts Corpora, evaluations, manifests, proofs, and snapshots with admission boundaries. Inspect szl-lake → Interfaces Spaces and demonstrations Consoles and verifiers. Reachability proves transport availability only. Browse Spaces →
Product surfaces

Operational links. Visible limits.

Product, source, runtime state, and evidence remain separate so a reachable page cannot silently become a capability claim.

Governed command

a11oy

Governed inference and agentic execution. Provider availability, signing, readiness, and action authorization remain separate states.

Open product Inspect evidence
Observation and fusion

Killinchu COP

Public-feed ingestion, fusion, provenance, and receipt paths when dependencies answer.

Boundary: public effectors and actuation are SIMULATED. This surface does not command a live weapon or establish production authorization.

Open COP View source
Current state

Status is linked, not hardcoded.

Use current source-binding and readiness endpoints. A cached card, screenshot, counter, or green badge is not current-state evidence.

Canonical sources

Evidence and runtime are separate axes.

A signature can establish integrity and origin within scope. It does not automatically establish quality, safety, compliance, adoption, profitability, or authority to operate.

  • PROVED
  • MEASURED
  • REPORTED
  • MODELED
  • CONJECTURE
  • ROADMAP
Build · evaluate · verify

Move from model output to accountable action.

Start with the artifact type, follow the evidence, check current state, then reproduce the exact path from source.

Enter a11oy Read documentation Review limitations

Collections 12

View 12 collections