Workflow gallery¶
Three recorded jobs. Each one is a prompt you can type, a captured result you can inspect, and a named host build — not a global quality score.
Start with the connection test
(example.com). Then run Understand an instruction. Host-specific
where-to-type notes: Host onboarding.
| Job | What you ask | What the capture shows | Named build |
|---|---|---|---|
| Understand an instruction | MDN Functions: scope, closures, syntax, conditions, citations, omissions | ok:true, focus:hit, 18 omitted sections |
ff-occam/1.1.1 GitHub Release v1.1.1, recaptured 2026-09-07 — ledger |
| Compare known sources | Two official nginx pages; do not invent proxy_read_timeout |
Both URLs ok; module focusMatched true/weak; beginner false | same Release host; public-build id is still 1.0.0 |
| Inspect changes | Same MDN URL + stored contentHash as if_none_match |
unchanged:true, empty body |
same Release host; public-build id is still 1.0.0 |
The same three jobs as folders (manifest.json, excerpts, omissions, wrapper
budget): Context packs. Operator CLIs for a docs delta and
a claim inspect: Docs change brief ·
Citation inspector. Bounded site research:
Site research.
The published GitHub Release identity (ff-occam/1.0.0) is recorded on the
current proof smoke and controlled refusal — see the
release evidence ledger. Do not treat a workspace
capture as byte-identical to every installed Release binary.
First useful prompt¶
After example.com works, paste this in a new conversation:
Use Occam to read https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Functions
Show how function scope and closures work. Include the syntax I need, any
conditions, and source links. Tell me if relevant content was omitted.
Settings used in the capture: fit_markdown:true,
focus_query:"function scope closures", max_tokens:800,
backend_policy:http. Reproduce from
settings.json
or:
occam read https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Functions --focus "function scope closures" --fit --max-tokens 800
If the result is incomplete, raise the budget or follow suggestedMinTokens.
Do not invent omitted steps.
Feedback¶
If a recorded job missed a command, condition, or citation you needed, send this template — task, expected content, redacted diagnostics. Do not send cookies or full HTML.