Semantic Instruments · 0.0.39 reference slice
Knowledge that can be inspected
before it is trusted or run.
A Semantic Instrument is an inspectable, versioned semantic package: it declares its purpose, inputs, dependencies, limits, and the evidence behind a result. It is a tool, never a peer person or an authority by presentation alone.
Honest release boundary. The 0.0.39 reference slice has package, validation, registry, resolution, receipt, attestation, RPL, and Studio workflows with scripted conformance coverage. It is not a claim that every sector workflow has completed live human UAT or that a demo runner is a clinical, legal, or employment decision service.
The package
A collectable has context, not just a badge
The shipped collectable binds an HCF description, N3 definition graph, manifest, accessible 10d visual, and—on native builds—an optional compact Q42 graph. Larger Q42 volumes are declared dependencies rather than silently becoming the instrument.
- Purpose, prohibited interpretations, category, and version are explicit.
- Inputs, outputs, source graph, visual, and content digest can be inspected.
- Demo and reference packs remain labelled; a visual does not create trust.
The boundary
Keep people, claims, and tools separate
An author, reviewer, publisher, instrument, execution result, and capability credential are separate records. A signature or catalogue listing establishes provenance; it does not establish that a claim is true.
- Collection, installation, trust, and activation are distinct decisions.
- Required inputs or dependencies that are missing are held, not invented.
- Revocation prevents new reliance without erasing historic receipts.
The Studio authoring rail
Seven deliberate stages, reachable by keyboard
01
Flow
Choose the bounded lifecycle and entry-point intent.
02
Select
Choose a labelled demo or reference starting point.
03
Shapes Canvas
Inspect and edit the declared semantic shape.
04
Manufacture
Build the inspectable collectable and check publication readiness.
05
Receipts
Review the chain of executions and their commitments.
06
Inspect
See purpose, dependencies, provenance, limits, and held state before use.
07
Run
Execute only a closed, preflighted installation and retain a receipt.
Gate
Human UAT
Live accessibility, security, and human walkthrough evidence remains the SI-12 release gate.
Validate & resolve
Dependencies are visible
SHACL shapes and package inspection reject incomplete material. Resolution creates a dependency lock, distinguishes optional from required dependencies, detects revoked entries, and supports a closed offline install when its declared dependencies are available locally.
Execute & record
A receipt binds the run
Preflight requires a closed installation. Each outcome binds release, package digest, dependency-lock digest, entry point, input/output commitments, and optional parent receipt. Empty required input produces a held receipt rather than a fabricated result.
Recognise & attest
Credentials retain their context
Native, W3C VC, and Open Badges-compatible exports are supported as envelopes. Capability recognition can compare formal or prior-learning evidence against requirements and report satisfied, equivalent, unresolved, or unmet elements.
What is executable today
Reference runner, not a disguised sector decision engine
Current reference behaviour
- Only the labelled
assess and recognise demo entry points are dispatched.
- The reference transform is deliberately simple, making its input and output commitments inspectable.
- Cancellation, resource limits, unknown entries, and unclosed installs are refused.
Not claimed by this page
- No generic Host-ID dispatch and no production clinical, legal, or employment determination is implied.
- Native Q42 content may be held in WASM with an explicit degradation notice.
- SI-12’s live security, accessibility, and human-UAT matrix is not represented as complete.
Follow the 0.0.39 record
The release page gives the wider milestone; the source tree and conformance suite remain the technical authority.