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

AI & ML interests

a11oy.net

Recent Activity
betterwithage  updated a Space 23 minutes ago
SZLHOLDINGS/a11oy
betterwithage  updated a model about 2 hours ago
SZLHOLDINGS/SZL-Khipu-1.5B
betterwithage  updated a model about 2 hours ago
SZLHOLDINGS/SZL-Forge-1.5B-ReceiptAgent
View all activity

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

Control before action. Evidence after.

Models, data, kernels, and demonstrations for decisions that must stay inside declared authority and survive independent scrutiny.

Enter the command center Browse the portfolio Verify evidence

Artifact type, evidence class, and runtime state remain separate.

Choose a path

One estate. Four clear journeys.

Start with the outcome you need. Operator, builder, researcher, and verifier routes converge on the same source, release, and evidence boundaries.

01 / Operate

Govern an action

Inspect policy, authority, decision state, and the receipt emitted by a bounded workflow.

Open a11oy Space -> 02 / Build

Use exact artifacts

Pin models, datasets, and governed software by immutable revision and disclosed lineage.

Browse models -> 03 / Research

Follow a release family

Trace primary artifacts, derived forms, evaluations, datasets, and demonstrations as one bounded collection.

Open collections -> 04 / Verify

Replay the evidence

Follow receipts and provenance outside the product UI without treating reachability as proof.

Open proof registry ->
Portfolio

Find the artifact, then inspect its contract.

Hugging Face repository type does not redefine the artifact. Every card must say what it is, where it came from, how to reproduce it, and what it does not prove.

Governed kernels are software, not trained models.

The Models surface groups source-bound executable kernels for discovery. Their cards must not imply neural training, benchmark coverage, or production authorization that their receipts do not establish.

Operating loop

Decision and evidence travel together.

A six-stage contract makes the control boundary legible on a phone without a horizontal carousel or clipped final steps.

  1. IntentDeclare the requested outcome and scope.
  2. PolicyEvaluate authority before execution.
  3. DecisionAllow, deny, warn, or escalate.
  4. ReceiptBind inputs, policy, action, and outcome.
  5. VerifyReplay evidence outside the product UI.
  6. RespondRollback, investigate, or improve policy.
Truth contract

Read the label before the claim.

Evidence class says how a claim was established. Runtime state says what is available now. Neither grants authorization.

Evidence classes

Every consequential statement carries one of these explicit scopes. Demonstrations may be SIMULATED. SZLHOLDINGS/SZLHOLDINGS is a HISTORICAL profile mirror only; do not infer current inventory, runtime status, proof counts, or canonical links from it.

  • PROVED
  • MEASURED
  • REPORTED
  • MODELED
  • CONJECTURE
  • ROADMAP

A signature establishes scoped integrity and origin, not accuracy, safety, or fitness.

Build or verify

Start with the product. Finish with the evidence.

Use exact revisions, keep runtime and evidence state separate, and report security issues through the protected channel.

Developer documentation Security policy Support

Collections 12

View 12 collections