Specification
The specification is the contract every runtime, tool, and host implements. The manifest is the center of gravity; everything else derives from it.
Documents
Section titled “Documents”- Manifest — the app manifest: bindings, capabilities, types, slots, events, libraries
- Manifest Inheritance —
extends: add-new, fill, refine, and the collision rules - Mod Manifest — what a mod declares: capabilities, entry, and
fillskeyed by host slot id - Fragments — the inert-template protocol:
data-bind,data-if, handlers, and the command buffer - Fragment Formats — the format catalog a slot’s
acceptsnames - Capabilities — default-deny grants, prefix subsumption, and the read/write mode lattice
- Bindings — host functions and namespaces, error vocabulary, naming grammars
- Hooks — event-typed slots and the dispatch contract
- Module-Format Mods — ES module entries, the import deny, and approved libraries
- Host Harness — synthetic hosts: stub bindings, journals, and replayable step scenarios
- Debugging — the DAP-shaped debug protocol
- Security — the sandbox guarantees and threat model
- Annotations —
@xriptsource annotations scanned into manifests
Schemas
Section titled “Schemas”Every schema is served at its $id URL, with prior version ids resolving as aliases:
/schema/manifest/v0.7.json— the app manifest schema/schema/mod-manifest/v0.7.json— the mod manifest schema/schema/harness/v0.7.jsonand/schema/harness-steps/v0.7.json— the harness descriptor and scenario shapes/schema/capability-prompt/v0.5.json,/schema/install-descriptor/v0.5.json,/schema/discovery-result/v0.5.json,/schema/debug-messages/v0.5.json— the host-side data shapes
Point a manifest’s $schema at the matching URL and editors pick up validation and autocomplete.