Prove TeX plugin independence
This commit is contained in:
parent
1830f21b05
commit
12b4d45ab8
8 changed files with 120 additions and 5 deletions
|
|
@ -194,6 +194,10 @@ Work:
|
|||
conformance fixtures are stable.
|
||||
- Move `tex.math` to EvePlugins when TeX source, macro, baseline, cached render,
|
||||
and fallback fixtures are stable.
|
||||
- Treat nested plugin placement as composition, not custody. A Sai surface may
|
||||
deploy with nested Norn or TeX surfaces when those plugin sidecars are
|
||||
available, but Norn and TeX remain independent plugin owners with their own
|
||||
ABI manifests, capability claims, and conformance packs.
|
||||
|
||||
Exit criteria:
|
||||
|
||||
|
|
@ -201,6 +205,8 @@ Exit criteria:
|
|||
- Providers invoke plugins through the ABI object model.
|
||||
- Runtimes declare plugin support through capability manifests.
|
||||
- Unsupported required plugin capabilities appear as visible gaps.
|
||||
- Optional nested plugin gaps degrade the nested surface; they do not transfer
|
||||
graph, math, or renderer semantics into the parent plugin.
|
||||
|
||||
## Phase 4: Graduate Runtime Bodies
|
||||
|
||||
|
|
@ -666,6 +672,10 @@ Recently cut:
|
|||
smoke asserts the provider pack, `aetheria-world` fixture, `aetheria`
|
||||
provider entry, and `aetheria-world-command-replay` scenario without reading
|
||||
Eve's parity manifest or dirtying the Aetheria worktree.
|
||||
- The Aetheria consumer smoke now also asserts frontend extraction boundaries:
|
||||
web and Unity UI Toolkit are covered generic lowerings, Unity scene remains a
|
||||
typed EveUnity gap, and the observed Aetheria Electron shell/client paths are
|
||||
split-handoff evidence to replace with a provider-agnostic EveElectron body.
|
||||
- The parity harness now runs a conformance consumer smoke against a copied
|
||||
`artifacts/conformance/latest` layout, proving the export can be consumed
|
||||
through `index.json` and `packs/*.json` without reading Eve's parity manifest.
|
||||
|
|
|
|||
|
|
@ -445,7 +445,9 @@ Sai does not own:
|
|||
## Norn And TeX As First-Class Plugins
|
||||
|
||||
Norn and TeX are not Sai subfeatures. Sai can place them inside a visual-novel
|
||||
scene, but ownership stays with their plugins.
|
||||
scene, but ownership stays with their plugins. Each plugin publishes a
|
||||
renderer-independent sidecar ABI; runtimes only declare whether they can project
|
||||
that plugin's advertised capabilities.
|
||||
|
||||
Norn plugin responsibilities:
|
||||
|
||||
|
|
@ -497,6 +499,10 @@ briefing without Sai becoming a graph engine or a TeX engine. Sai owns the
|
|||
stage. Norn owns the graph. TeX owns the math. Eve owns the plugin ABI and
|
||||
renderer conformance. The app provider owns live state and receipts.
|
||||
|
||||
Fixture co-location is not semantic custody. A TeX ABI fixture may currently
|
||||
use the Sai VN surface to prove nested placement, but the TeX handoff, manifest,
|
||||
advertisement, and conformance pack still graduate through EvePlugins.
|
||||
|
||||
## Building An App With Eve And Sai
|
||||
|
||||
An app that wants VN functionality composes four layers.
|
||||
|
|
|
|||
|
|
@ -33,7 +33,8 @@ Anything else is guilty until it can explain why it protects a core invariant.
|
|||
|
||||
- `Eve`: kernel contracts, specs, browser reference, and conformance incubation.
|
||||
- `EvePlugins`: first-party reusable plugins while young, such as fields,
|
||||
world 2D/3D, and TeX.
|
||||
world 2D/3D, and TeX. These plugins are independent sidecar capabilities, not
|
||||
hidden features of Sai or any other provider.
|
||||
- `Sai`: owner for the VN/Ink plugin once `sai.vn` graduates.
|
||||
- `Norn`: owner for graph plugin semantics once `norn.graph` graduates.
|
||||
- `EveUnity`, `EveGodot`, `EveFlutter`, `EveElectron`, and similar runtime
|
||||
|
|
|
|||
Loading…
Reference in a new issue