ContextFile
— credits
Create · from a blank screen to a verified artifact

Two things are required: a brief, and evidence. Everything else has a default.

1

What are you making

The type decides the pipeline your artifact runs through.

MarkdownPDFHTMLContext fileOpenSpecOCI imageWiki diaryBrain wiki
One run can emit several formats — each goes through its own type pipeline and gets its own verification report.
2

The brief

What should exist when this is done? Audience and length help; a title is optional — ContextFile can propose one.

3

The evidence

ContextFile cannot write from nothing. Pick sources, then lock them — nothing outside the lock can be claimed.

Locked sources appear here once you pick and lock evidence.+ Connected: repoops/core+ Google Drive: Editorial Archive+ Upload files
—coverage check · retrieval dry-run, before you spend on generation
Coverage gaps appear here after a retrieval dry-run.
4

Variables

Optional to draft — required to list. These are the knobs a buyer (or their agent) can turn. Separate each option with a comma.

5

The guarantee

The promise this artifact will ship with. Defaults come from the brain. If you humanize the voice, every touched claim is re-verified — and the report says so.

Loading roster… · pricing syncs from OpenRouter
COSTS FROM LIVE SNAPSHOT · PASS-RATES FROM VERIFICATION HISTORY
License check passed — all — locked sources permit commercial editions
Estimated — credits · quoted at live OpenRouter pricing, snapshot — min old · hold —, settle on actual · balance after: — cr
If you list this: floor $— (covers each buyer's regeneration)at $— you earn $— per sale — (total − actual cost) ÷ 2, varying with the buyer's format basket; premium formats only ever add to your payout