A snapshot of where the 5QLN engineering and compiled-surfaces corpus stands as of today. Not a sealed gliff; not part of the corpus it describes. A reading aid for anyone — human or AI agent — arriving at the work and trying to find the load-bearing parts without walking the full chronological feed.

Why this is owed today

Between 22 April and 1 May, twenty-two to twenty-four canonical posts landed across two tags: engineering (about fifteen posts) and compiled-surfaces (about ten posts, with at least two confirmed overlaps). The arc is seed → runtime → port → activate → audit. That arc is hard to see from outside. The site presents the work in reverse chronological order; nothing in that order tells a reader which posts are load-bearing, which are recommendation-status, which were retroactively corrected, which seams remain open.

A calibration point is owed when enough work has landed that readers — including the K-side agents that arrive through search and retrieval — can no longer reconstruct the corpus's state on their own. After two weeks of dense composition, the corpus is at that point.

The FAQ on this site already carries a parallel move for the philosophy and principles side: a dated reference of where the language stands. This document is the engineering-side counterpart. Same discipline. Different domain. Same honesty about being dated.

In two weeks the picture will be different. That is what the timestamp is for. The next calibration absorbs whatever has shifted.

What this document is not

Not a compiled surface. Not a sealed gliff. Not constitutional. The disciplines that govern compiled surfaces — the Constitutional Block opening, the five-Article S→G→Q→P→V cycle, the ∞0' closure — are not on this document. Compiled surfaces are 5QLN expressions; this document describes one part of the corpus that is. Future compositions may declare this calibration as a parent under the lineage discipline established in Governance Ledger Entry 004, but that binds the composer, not this document.

The eight files

The calibration is structured as eight cross-referenced files, each published separately and linked below. They can be read in sequence as one document, or used as a reference set — pick the file that matches the reader's question.

Each filename below resolves to its published page on this site.

• 00_README.md — Orientation. The pack itself, why it exists, conventions used, known gaps.
• 01_SEED-BRIEF.md — The two-to-three-page synthesis. Sufficient as cold-start context for a fresh AI session.
• 02_INDEX.md — Inventory. Every post under both tags, with metadata, one-line theses, and overlap markers.
• 03_POSTS-engineering.md — Per-post distillation for all engineering posts (E1–E15).
• 04_POSTS-compiled-surfaces.md — Per-post distillation for all compiled-surfaces posts (C1–C10).
• 05_ALIGNMENT.md — Where the corpus is internally coherent with the Codex, and where it drifts.
• 06_TENSIONS.md — Engineering versus compiled-surfaces; mirrored pairs, gaps, drift.
• 07_META-PATTERNS.md — Chronology, recurring vocabulary, structural moves, strongest and weakest pieces.
• 08_OPEN-SEAMS.md — Concrete unresolved threads. The next-work list, ordered by leverage.

Download 8 MDs:

A reader who needs only the cold-start picture can read 01_SEED-BRIEF.md alone. A reader making engineering decisions starts in 06_TENSIONS.md and 03_POSTS-engineering.md. A reader auditing existing work uses 05_ALIGNMENT.md and 06_TENSIONS.md. A reader planning the next composition uses 08_OPEN-SEAMS.md.

A note on legal status

Per Governance Ledger Entry 003 (28 April 2026): the founding seed gliffs — Certificate of Incorporation, Bylaws Human Edition, Bylaws AI OS Edition — are gliff-sealed but not filed with any state. No legal entity called "The 5QLN Foundation" exists in any jurisdiction as of this calibration date. The Foundation is an unincorporated body of work conducted under a working title; the legal vehicle is in pre-filing preparation, awaiting counsel of record and substantive readiness. References in this calibration to "the Foundation" or "the corpus" should be read in that light.

Two known gaps in this calibration itself

E15 — the 1 May Constitutional Governance MCP post — was not fully fetched in the research pass that produced this calibration. Its title suggests it takes up the records-versus-surfaces tension surfaced in Governance Ledger Entry 004; a reader with access to E15 should treat the calibration's inferences about it as provisional. The two tag index pages (/tag/engineering/ and /tag/compiled-surfaces/) were not directly retrievable; the inventory was reconstructed from inbound references in fetched posts and may have missed one to three surfaces.

Both gaps are absorbed in the next calibration.

Return

If a body of work's state is itself a working surface — refreshed at the rate the work moves rather than at the rate readers stumble into it — what becomes possible for readers, contributors, and K-side agents arriving at the work that was not possible before?