Folio

Read the request and any existing artifact before writing HTML. Every external dependency and publish URL belongs in the manifest ledger. Artifacts are static documents — they do not call APIs.

When to use folio — and when not to

Folio is for durable, openable, shareable web deliverables — things the user will keep, reopen, or hand to someone else.

Use folio when:

• The user asks for a doc, dashboard, sheet, deck, or page they'll save or send
• The output is a deliverable, not a quick look ("make me a report", "build a dashboard for the team", "put this online", "I want a page that…")
• The user invokes a verb explicitly (folio publish, folio audit, folio remix, folio describe)

Do not use folio when:

• The user wants a quick look, not a deliverable ("show me", "what does this look like", "just check", "can you display")
• The output won't be opened again after this conversation — answer inline or write a scratch file, don't stamp it, ledger it, or gate it
• The request is for a code snippet, a config file, a single function — those aren't browser artifacts