+
+
+ {{ output.eyebrow | escape }}
+{{ output.title | escape }}
+
+ 
+
+ {{ output.caption | escape }}
+ {% if output.source and output.source_label %} + + {{ output.source_label | escape }} + + {% endif %} +{{ evidence.eyebrow | escape }}
+{{ evidence.introduction | escape }}
+ {% endif %} + +{{ output.eyebrow | escape }}
+{{ output.caption | escape }}
+ {% if output.source and output.source_label %} + + {{ output.source_label | escape }} + + {% endif %} +{{ pipeline.eyebrow | escape }}
+{{ pipeline.introduction | escape }}
+ {% endif %} + +{{ status.eyebrow | escape }}
+{{ status.introduction | escape }}
+ {% endif %} + +Finite tilings / algorithm laboratory
- # Tiling Foundry ++ Tiling Foundry turns the Yang–Zhang reduction into an inspectable software + pipeline. Construction, solving, verification, witness correspondence, and + measurement remain separate so that each result can be audited rather than + merely observed. +
- [Explore the documentation](#documentation){: .text-link } + Explore the documentationReading path
+ Start with the architecture reference and reduction note to understand the + pipeline. Use implementation contracts and the data contract when inspecting + code or integrations. Use methodology pages before interpreting dated + benchmark, profile, coverage, or fuzzing reports. +
+ ++ Each catalog entry shows both its document type and status. Current + specifications, contracts, references, notes, and designs describe maintained + behavior within their stated scope. Methodology pages define how evidence is + collected. Dated reports preserve results for a named source state and date. + Historical pages preserve earlier decisions and are not current API + documentation. +
+ +
+ Completed implementation plans remain versioned under docs/plans/
+ for operational history, but are excluded from this public catalog.
+
Start here
+ These current references define the software boundaries that keep the + reduction, solver, independent verification, solution transport, and + Boolean–Wang witness correspondence auditable. +
{% include document-list.html documents=architecture %}Construction
+ The technical note distinguishes paper conventions from project conventions. + The builder page is the implementation contract for region geometry, + ownership, and black-box obligations. The bibliography records primary + sources. +
{% include document-list.html documents=reduction %}Measured mechanisms
+ Read the methodology first. The remaining pages are dated profile or + benchmark reports that preserve their corpus, environment, work counters, + timing method, and limitations. +
{% include document-list.html documents=optimization %}Native C / Z3
+ The current protocol distinguishes solving the same prepared Wang region + from end-to-end decisions that begin with the same formula file. Dated + reports retain the measured source identity and interpretation limits. +
{% include document-list.html documents=comparisons %}Design history
+ Earlier proposals are retained to explain the project’s design trajectory. + They are not current API contracts. +
{% include document-list.html documents=historical %}# Tiling Foundry
`. The public page + therefore begins its heading outline at H2. This is a correctness and + accessibility defect, not a stylistic preference. +2. **The homepage title is duplicated.** The output is + `