SZL Holdings

Team

company

https://a-11-oy.com/

stephenlutar2-hash

stephen-l-279315240

Activity Feed Request to join this org

AI & ML interests

a11oy.net

Recent Activity

betterwithage updated a Space about 6 hours ago

SZLHOLDINGS/yarqa

betterwithage updated a model about 8 hours ago

SZLHOLDINGS/szl-kernels

betterwithage updated a Space about 9 hours ago

SZLHOLDINGS/README

View all activity

Organization Card

Community About org cards

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.

Weights + software

Models

Lineage

Trained weights, adapters, recipes, surrogates, and source-bound kernels stay explicitly classified.

View every model ->

Records + evidence

Datasets

Provenance

Corpora, admitted evidence, evaluations, receipts, and proofs expose source and privacy boundaries.

View every dataset ->

Interfaces + demos

Spaces

Runtime

Command, verification, research, and visualization interfaces expose source and demonstration limits.

View every Space ->

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.

IntentDeclare the requested outcome and scope.
PolicyEvaluate authority before execution.
DecisionAllow, deny, warn, or escalate.
ReceiptBind inputs, policy, action, and outcome.
VerifyReplay evidence outside the product UI.
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.