Deterministic document CI
if.typeset
A pipeline that turns Markdown into reviewable outputs with measured quality signals — so you can ship docs that survive scrutiny.
Pipeline
validate → lint → render-html → render-pdf → QA incidents → trust contract
Black / white
What it gives you
- Deterministic builds (same input → same output).
- QA incidents as machine-readable JSON.
- Profiles (web_pdf, print_pdf) for different publication targets.
What it does not claim
- It does not prove factual correctness.
- It does not guarantee compliance scope or policy effectiveness.
- It does not replace human review for high-stakes decisions.
Profiles (examples)
Same engine, different publication constraints.
web_pdf Web-first HTML plus a reviewable PDF output, tuned for headings, links, and diagrams under typical browser constraints.
print_pdf Print-friendly PDF output with stricter layout and overflow checks, tuned for clean exports and “no surprises” pagination.
Verification binding
Receipts make published outputs checkable later.
When outputs are published, bind source and output bytes to a public receipt so reviewers can verify integrity without logins.
How verification works Code (HTML-first fallback)
For review environments that can’t use Forgejo UI/auth.
Hosted-static codepack snapshot:
Open codepack
https://infrafabric.io/static/hosted/review/codepacks/iftypeset/2026-01-06/index.html