Skip to main content

External Frameworks as an Input Class

Purpose​

This page records the public boundary for external-framework outputs inside the governed ecosystem transition framing.

External frameworks are not the center of the architecture. They are one input class that may enter StegVerse through governed transition handling.

Transition path​

external framework artifact
  -> governed ingestion
  -> CGE fingerprinting
  -> GCAT / BCAT evaluation
  -> Transition Table standing
  -> ALLOW / DENY / FAIL-CLOSED
  -> receipt_chain / STRP record
  -> governed output

What this changes​

The external-framework surface should not be presented as:

StegVerse compares itself to external frameworks.

The preferred framing is:

StegVerse can ingest external-framework outputs as governed transition candidates.

Compatibility evidence boundary​

Generated external-framework reports and page-status blocks are compatibility evidence only.

They are not:

certification
endorsement
formalism adoption
admissibility proof
execution authority
canonical STRP admission

Relationship to governed ecosystem transitions​

This page is subordinate to:

docs/governance/governed-ecosystem-transitions.md

External-framework outputs follow the same high-level transition boundary as human requests, LLM outputs, repo tasks, SDK requests, runtime observations, and receipt-chain continuations.

Current status​

EXTERNAL_FRAMEWORK_INPUT_CLASS_FRAMING_PRESENT