Docs
What the Contract means, and what counts as Rig.
Design philosophy
Rig is a future-proof, host-independent, human-readable vocabulary for creative work. The framework ships no code - why no code - because agreement outlives every fulfillment that honors it.
Why no code
A no-code creative application framework. Because no code is the best code.
Terms
Rig prose leans on a few words in a precise way. This page is the reference.
Is it Rig?
Rig is a shared vocabulary - Readable Independent Grammar: the schema catalog (prose + JSON Schema) and portable entity + POD component documents (rig.document). It is not a library to link
SUDE loop
SUDE = Setup / Update / Draw / Exit.
ECS conventions
Entity-component composition is how Rig portable meaning is shaped. No particular registry library. No GPU or UI toolkit types inside Contract-facing components.
UI (optional companion)
Rig + UI sits on top of Rig (entity/component POD + schemas). It is still zero code, and it stays in this Contract - not a separate named spec. Layout chrome and UI packs are fulfillment; po
Interchange
Rig portable documents are JSON using the rig.document envelope. Component object keys are full schema ids (rig.spatial.transform).
Properties and Datatypes
Portable property descriptors let any properties surface show any opt-in component field.
Versioning
RigWorks uses Semantic Versioning (MAJOR.MINOR.PATCH). One source of truth: VERSION. Document envelopes carry the same value as the root "rig" field.
Known gaps
Places the Contract is silent, ambiguous, or wrong. Found by implementing a fulfillment from the prose, not imagined - the honest price of a data framework (why-no-code.md) is that nothing f
AI co-coding
AI co-coding is here to stay. Not as a prediction to argue about - as a design constraint we address.
Dev environments
A development-environment host is Rig when it emits entities with POD components keyed by schema ids it supports (honors). Provider SDKs, interactive login UX, cache stores, and CLI chrome a
IDML
Rig names InDesign layout meaning as rig.layout. plus rig.story.. InDesign Markup Language files stay host mappings at the boundary - same rule as IFC in openbim.md and SVG (design philosoph
OpenBIM
Rig names OpenBIM meaning as rig.bim.. IFC, BCF, and IDS files stay host mappings at the boundary - same rule as SVG (design philosophy).
Print (FGF)
Rig names pellet / FGF machine meaning as rig.print.. G-code files and slicer processes stay host mappings at the boundary - same rule as IDML in idml.md.
ROS 2
A ROS 2 host is Rig when it emits entities with POD components keyed by schema ids it supports (honors). rmw, DDS, launch files, and bags are fulfillment - not this catalog.
UFO
Rig names editable-font meaning as rig.font.. Unified Font Object files stay host mappings at the boundary - same rule as IFC in openbim.md and SVG (design philosophy).