Evidence before copy
Workflow claims begin with a source fixture and an output produced by the current application. Guides link to those artifacts when publishing them is safe and useful.
Publishing evidence
How we test Markdown publishing claims
Lemmafour guidance is tied to reproducible source files, generated output, explicit limitations, and a dated editorial review. This page explains that process and its boundaries.
Visible limitations
Unsupported execution, package, rendering, or repository behavior is stated alongside the workflow. A successful example is not presented as universal compatibility.
Dated review
Publishing guides have an accountable review owner and a review-by date. Material product changes trigger an earlier review rather than waiting for the normal quarterly cycle.
Private measurement
Discovery is measured with aggregate page, query, referral, device class, and commercial outcome data. Document content, filenames, local paths, account identifiers, and email addresses are excluded.
Review sequence
From fixture to published guidance
- 1Define the exact workflow
Specify the input format, relevant settings, expected output, and meaningful failure conditions.
- 2Run the current product path
Use the public workspace and the same compilation or export path described to readers.
- 3Inspect source and output
Check structure, page layout, equations, diagrams, citations, images, and export behavior relevant to that guide.
- 4Publish evidence and boundaries
Attach reproducible artifacts where appropriate, state limitations, and date the review.
Corrections
Found a result that does not match?
Include the guide URL, browser, operating system, input type, and the expected and observed behavior. Do not email a sensitive document unless it has been safely redacted.
Report a publishing issue