StegVerse is a research and engineering effort focused on governed AI execution, admissibility testing, receipt-bound runtime paths, and reconstructable human-AI / agent-system collaboration.
Submission is not execution. Execution is not authority. Authority is not admissibility.
Traditional software systems often assume that authenticated actors may execute operations freely.
StegVerse separates the path:
submission
→ manifest binding
→ receipt binding
→ admissibility check
→ bounded execution / demonstration
→ result receipt
→ reconstruction packet
In this model:
- actions are evaluated before consequence attaches;
- receipts preserve transition history;
- reconstruction answers what happened;
- admissibility answers whether standing existed for consequence;
- public review does not create endorsement, compatibility, provenance, collaboration, or validation.
| Component | Repo | Purpose |
|---|---|---|
| SDK intake | StegVerse-SDK | Public SDK boundary for manifest-bound and receipt-bound submissions. |
| LLM adapter | LLM-adapter | Converts LLM output into route-ready governance artifacts. |
| Demo suite | stegverse-demo-suite | Reproducible public governance demonstrations. |
| Demo suite runner | demo-suite-runner | Formal runner for GCAT/BCAT and related fixture probes. |
| Demo ingestion engine | demo_ingest_engine | Org-side orchestration and result-return boundary. |
| Demo sandbox | demo-sandbox | Public sandbox fixtures and controlled experiments. |
| Core-node runtime demo | core-node-runtime-demo | Runtime comparison across ingestion, core-node, and micro-node paths. |
| GSL | stegverse-gsl | Governance Specification Language for structure and manifest validation. |
| Discovery | discovery | Component discovery and repository indexing. |
| Manifests | manifests | Canonical pricing, package, tier, and configuration manifests. |
The following repositories are expected to remain private unless separate public-safe scaffolds are created:
| Component | Purpose |
|---|---|
| trust-kernel | Authority-bearing governance kernel. |
| StegVerse-admission | Admission / threshold layer. |
| telemetry | Cross-org signal monitoring and operational records. |
| TV / TVC | TrustVault and TrustVaultController workflow material. |
StegVerse is in an early prototype and demonstration phase. Public repositories are intended to expose interfaces, demos, schemas, receipts, path reports, and reconstruction-oriented artifacts. Private repositories retain authority-bearing or operationally sensitive logic.
Private review, artifact inspection, repository review, or technical comments do not become public attribution, endorsement, compatibility recognition, provenance recognition, collaboration, validation, semantic attribution, conceptual attribution, or publication authorization.
Public repositories define their own licenses. Most public demonstration and SDK repositories currently use MIT.