Publish
Send the candidate artifact through the authenticated publish path.
Kraton Registry / discovery plane
Search intent, browse declared authority, then inspect one immutable record by digest. This is a registry surface — not a gallery of claims.
SEMANTIC SEARCH · HARD AUTHORITY FILTERS · SIGNED + VERIFIED RECORDS ONLY
Allowed authority / hard filter
A filter is an allowlist: a result's declared capabilities must be a subset of the chosen boundary. These are not decorative tags or relevance hints.
Registry records
DISCOVERY STATUS / OFFLINE
Discovery API unavailable
The read-only discovery service is offline. Artifact bytes, review state, and registry entries remain intentionally absent here until the service can answer again.
A record has a lifecycle
GraphQL is intentionally read-only. Publishing follows a separate authenticated path: the component is inspected, its boundary is analysed, its bundle is signed, and only then can a record become discoverable.
Send the candidate artifact through the authenticated publish path.
Read WIT, schemas, and imports from the component bytes.
Derive capabilities and reject boundaries that do not hold.
Bind component and policy layers in one artifact bundle.
Expose a signed, verified record addressed by digest.
Discovery returns a SHA-256 address; OCI serves those exact bytes; the Engine runs that exact address. A name may advance. A digest never silently does.
Admission is not a badge
The authenticated publisher path is deliberately separate from browsing. A newly accepted artifact stays pending until its component, declared authority, signature, and analysis result agree.