Use Forma as a presentation boundary, not an application runtime.
Agents reuse canonical patterns, preserve native semantics, and leave behavioral and domain authority in the systems that own it.
Required sequence
- Identify the user task and domain state.
- Find the closest canonical pattern under
patterns/. - Preserve its semantic elements, class structure, labels, IDs, and ARIA relationships.
- Supply application content and rendered state.
- Put non-native behavior in the consuming application/Limen.
- Keep legal transitions, permissions, obligations, and scoring in Ordo/application state.
- Run repository and site verification before claiming completion.
Boundary ownership
| Concern | Owner |
|---|---|
| Typography, color, spacing, layout, responsive presentation | Forma |
| Checked/open/required/disabled and native state | Native HTML rendered by the application |
| Async search, ranking movement, rule editing | Application / Limen |
| Legal transitions, capabilities, obligations, permissions | Ordo/application domain state |
| Scores and assessment interpretation | Application domain logic |
Do not
- Add runtime JavaScript or WebAssembly to Forma.
- Replace native HTML only to obtain a custom appearance.
- Create duplicate components for presets an existing semantic pattern represents.
- Infer domain meaning from color, order, or CSS state.
- Make drag, hover, pointer input, or color the only usable path.
- Fork a pattern in an application merely to change visual styling.
Build and verify
npm install
npm run build
npm run check
npm run site:check
./ros registry check
./ros validate
The repository source of truth for this contract is docs/AGENT-USAGE.md.