Organizing Private and Public Artifacts in One Registry

Define access policy without duplicating the same artifact across stores. The useful result is a method that preserves evidence, exposes constraints, and makes the next decision reviewable. This note describes an engineering workflow rather than a claim about a particular organization or production event.

Establish the boundary

Separate artifact visibility from file format and model type. Keep the relevant source version, configuration, and stable identifier together while this work is performed. That gives a reviewer a direct path from an observed outcome to the input and rule that produced it. Treat automatic checks and human judgment as separate controls, then record both in the release or incident note.

Public, workspace, and restricted states

Define public, workspace, and restricted states. Keep the relevant source version, configuration, and stable identifier together while this work is performed. That gives a reviewer a direct path from an observed outcome to the input and rule that produced it. Treat automatic checks and human judgment as separate controls, then record both in the release or incident note.

Metadata exposure appropriate to each state

Keep metadata exposure appropriate to each state. Keep the relevant source version, configuration, and stable identifier together while this work is performed. That gives a reviewer a direct path from an observed outcome to the input and rule that produced it. Treat automatic checks and human judgment as separate controls, then record both in the release or incident note.

Promote a private artifact to public through an explicit review

Promote a private artifact to public through an explicit review. Keep the relevant source version, configuration, and stable identifier together while this work is performed. That gives a reviewer a direct path from an observed outcome to the input and rule that produced it. Treat automatic checks and human judgment as separate controls, then record both in the release or incident note.

Revoke access without mutating immutable released files

Revoke access without mutating immutable released files. Keep the relevant source version, configuration, and stable identifier together while this work is performed. That gives a reviewer a direct path from an observed outcome to the input and rule that produced it. Treat automatic checks and human judgment as separate controls, then record both in the release or incident note.

Downloads and token scopes with minimal retained data

Audit downloads and token scopes with minimal retained data. Keep the relevant source version, configuration, and stable identifier together while this work is performed. That gives a reviewer a direct path from an observed outcome to the input and rule that produced it. Treat automatic checks and human judgment as separate controls, then record both in the release or incident note.

Practical check

Access-state table and example token-scope policy. The example below is intentionally small enough to run as a preflight check before a longer release, migration, or build workflow.

curl -fsSLO https://your-instance.example/download/qwen7b-ticket-triage
shasum -a 256 qwen7b-ticket-triage

Evidence for the next decision

Keep the input digest, outcome, and reviewer note with the resulting artifact or postmortem. Claiming a UI flag alone is an access-control system. When the current evidence is incomplete, preserve the failing example, define the missing validation, and defer promotion until the result can be compared fairly.

Make the process idempotent. Repeating the same step on unchanged input should not append metadata, discard extra detail, or silently change ownership. Idempotence makes retries safe and exposes hidden state when outputs differ.

Review results by failure category rather than a single blended number. A small number of high-risk failures can outweigh an improvement on common cases, particularly when the output feeds a release or escalation workflow.

Keep accepted and rejected examples together. A concise rejected sample with its expected outcome is a durable regression test and prevents the same edge condition from returning as an unexplained surprise.

Use a separate holdout set for release decisions. Training records can guide implementation, but they cannot demonstrate that the process behaves correctly on new wording, new sources, or a changed input order.