Agent operating contract

Use Folio as document intent, not a pagination engine.

Agents preserve semantic source HTML, choose the smallest Folio primitive that expresses layout intent, and keep renderer limitations explicit.

Required sequence

  1. Start with the document's semantic HTML and reading order.
  2. Use ordinary headings, paragraphs, lists, tables, figures, and links directly.
  3. Add a Folio custom element only when it expresses reusable print/layout intent.
  4. Check the component page and capability tier before promising output behavior.
  5. Keep printable content useful before custom-element upgrade or when JavaScript is unavailable.
  6. Use CSS/native fragmentation before considering any browser code.
  7. Put preview/configurator application state in Limen/Ordo, not inside printable components.
  8. Run the print experiments and site checks before claiming a change is complete.

Mobile and screen preview behavior

Folio's public CSS is responsive on screens without changing the physical print contract. No JavaScript is required for responsive behavior.

Adaptive component

ef-print-columns

At screen widths of 48rem or less, multicolumn content collapses to one readable column. Print media preserves the authored column count.

Adaptive component

ef-print-sidebar

At screen widths of 48rem or less, the main/rail layout stacks into one column. Print media preserves the side-rail grid.

Natural flow

Structural primitives

Structural and content primitives such as document, title-page, section, back-page, callout, figure, code, toc, note, break, and keep follow normal flow. Header/footer regions stack for screen inspection, and wide tables scroll inside their wrapper rather than overflowing the page.

Contract boundary

Screen is inspection. Print is output.

Never change pagination rules merely to make a phone preview fit. Screen-only adaptations must disappear under @media print.

Boundary ownership

ConcernOwner
Document data and semantic meaningConsuming application
Reusable print layout intent and visual defaultsFolio
Pagination, fragmentation, physical page constructionBrowser or selected renderer
Renderer capability and deterministic export policyCapability profile / adapter
Interactive preview/configuration stateLimen + Ordo/application

Do not

Repository verification

npm install
npm test
npm run site:check
npm run site:test:browser
./ros registry check
./ros validate

The repository source of truth for this guidance is docs/AGENT-USAGE.md.