StegVerse SDK Developer Wiki

Developer-facing documentation for the canonical StegVerse-org/StegVerse-SDK programmatic intake, testing, integration, evidence, replay, and reconstruction boundary.

Published from SDK source revision 58b6fde87e19851cf255836f7a79312f7300bafb. This site is a documentation projection, not an authority surface.

Core flow

source-native manifested data
-> stegverse.ingress-manifest.v1
-> caller-selected processing capability
-> declared installed runtime route
-> processor-specific evaluation
-> organization-ledger transition receipt (the Organization keeps custody)
-> caller-selected return projection
-> returned artifact + manifest_receipt_id
-> replay / reconstruction where applicable
(downstream, non-gating: Master Records records the released batch receipt)

Developer paths

Manifest ingress

Submit source-native manifested data through the generic ingress envelope.

Processing contract
Ingress schema

Examples and demos

Start from a framework-neutral external manifest and the SDK builder/CLI guidance.

External-framework example
SDK README / CLI examples

Receipts, Replay / reconstruction

Navigate manifest_receipt_id, governed result lineage, replay, and reconstruction.

Receipt navigation

Current implementation state

Distinguish merged source, semantic validation, authentic governed runtime evidence, and release status.

SDK mirror handoff

Selection is not authority

payload class != processing capability
processing capability != runtime route
processing selection != authority
route selection != authority
caller projection != canonical organization record

Authority boundaries

The SDK validates/manifests intake and returns evidence. Interlock/InTr owns governed ingress/egress transition seams where required. The Organization owns custody of its runtime history in its organization ledger, and each transition closes on the organization-ledger receipt. Master Records records released organization batch receipts downstream for cross-organization reconstruction; it is not custody, not a gate and grants no transition authority, and nothing waits on it. Publisher may materialize an approved presentation/publication projection but does not become governance authority. TV/TVC remains credential authority where credentials are required. This wiki grants none of those authorities.

Machine-readable provenance

Wiki source manifest records the exact published source revision and SHA-256 digest for each copied canonical source file.