Public viewers
3 reviewed PDFs
Actual PDFs · Audited Basis outputs
Basis examples
Basis examples from reviewed runs.
Public-safe viewer pages built from reviewed Basis outputs. Each example centers the document, the run brief, and the artifact shape that carried through to a handoff-ready result.
Each example is derived from a real Basis workflow. Sensitive details can be redacted while preserving the structure of the decision package, artifact trail, and review process.
Output shapes
brief · note · manuscript
Artifact trail
PDF · TeX · review notes
What these pages show
Visible output
Viewer pages rendered from reviewed Basis artifacts.
Curation
Public-safe editions with cleaned front matter and internal-only references removed.
Use
A fast way to judge whether Basis matches your workflow.
Public proof surface
Three different output shapes from the same product surface.
These pages show how a Basis run carries through into a document someone can inspect, export, and hand off.
Technical brief
Technical Brief Example: Evaluating Coding Agents on Real Repository Tasks
A real 38-page Basis brief on repository-scale coding-agent evaluation, presented as a curated public proof page with the actual manuscript output front and center.
Document
Technical brief
Length
38 pages
Front matter
Cover · contents · main sections
Formal note
Formal Note Example: Unbiasedness of the Sample Mean Under Integrability
A compact Basis manuscript showing that the system can produce a tight proof note with clear assumptions, a clean theorem statement, and an explicit failure case.
Document
Formal note
Length
3 pages
Front matter
Cover · abstract · proof
Structured manuscript
Structured Manuscript Example: Proof Note With Setup, Counterexample, and Remedy
A paper-style Basis manuscript that expands a simple theorem into a more structured note with setup, main result, counterexample, and a practical bounded-transform remedy.
Document
Structured manuscript
Length
4 pages
Sections
Setup · theorem · remedy
Next step
Need the same output shape on your own technical question?
Start with a concrete objective, constraints, and the kind of artifact you expect to review at the end. These examples show the level of clarity and structure we expect a new run to reach.