Docs

What the Contract means, and what counts as Rig. Start with why, then the rules, then the mappings.

Why Rig

The argument in three altitudes: the tablet, the anti-library case, and the consequence when models author work.

Design philosophy

Rig is a future-proof, host-independent, human-readable vocabulary for creative work.

Why no code

A no-code creative application framework. Because no code is the best code.

AI co-coding

AI co-coding is here to stay. Not as a prediction to argue about - as a design constraint we address.

Contract

The portable rules, the vocabulary for talking about them, and the test for whether something is Rig.

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

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.

SUDE loop

SUDE = Setup / Update / Draw / Exit.

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

Versioning

RigWorks uses Semantic Versioning (MAJOR.MINOR.PATCH). One source of truth: VERSION. Document envelopes carry the same value as the root "rig" field.

History

Release notes for the Contract. One row per version, newest first. The rules that govern these rows (SemVer, maturity tiers, the 1.0 freeze) live in versioning.md; the number itself lives on

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

Data and exchange

The JSON wire shape, .rig / .rigz packages, and portable property datatypes.

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.

Format mappings

How established file formats map onto Rig schemas at the boundary. Native files and encodings stay fulfillment.

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

KiCad

Rig names electronics meaning as rig.circuit. (parts, terminals, nets - shared by schematic, board, and live hardware) and board fabrication as rig.pcb.. KiCad files stay host mappings at th

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.

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).

Domain mappings

How established domains and runtimes are expressed with Rig schemas. Solvers, services, and runtimes stay fulfillment.