The VARIANT contract for a SECTION Page: one page per reader-ordered section unit of a paper or application, produced by a stage that runs once per unit. It loads haipipe-board-page for the base and haipipe-board-page-for-stage for the chain and gate, then adds only what a section page carries and a plain stage page does not: the section kind, the venue contract block whose blueprint line BINDS this unit alone, the template resolved per venue and kind, and the landing surface where citation, value, and display bindings reach prose. This is the type that CONNECTS to for-venue: the QBv catalog is read once by the venue stage, the blueprint allocates the desk's totals per section, and this page consumes its own allocation. Use when writing or fixing a section page, when its venue binding is wrong or missing, when a retarget must say what gets rewritten, or when a landed answer never reached the sentence that owed it. Trigger: section page, S-Main, S-Appendix, section kind, venue contract block, blueprint binds,
Instrucciones de origen · Vista previa de solo lectura
name
haipipe-board-page-for-section
description
The VARIANT contract for a SECTION Page: one page per reader-ordered section unit of a paper or application, produced by a stage that runs once per unit. It loads haipipe-board-page for the base and haipipe-board-page-for-stage for the chain and gate, then adds only what a section page carries and a plain stage page does not: the section kind, the venue contract block whose blueprint line BINDS this unit alone, the template resolved per venue and kind, and the landing surface where citation, value, and display bindings reach prose. This is the type that CONNECTS to for-venue: the QBv catalog is read once by the venue stage, the blueprint allocates the desk's totals per section, and this page consumes its own allocation. Use when writing or fixing a section page, when its venue binding is wrong or missing, when a retarget must say what gets rewritten, or when a landed answer never reached the sentence that owed it. Trigger: section page, S-Main, S-Appendix, section kind, venue contract block, blueprint binds, word budget, section edit page, retarget section, /haipipe-board-page-for-section.
metadata
{"version":"0.1.1","last_updated":"2026-08-05","summary":"First cut, on JL's 260805 admission. Rejected earlier as for-main; readmitted as for-section because section is cross-family and carries typed records for-stage does not."}
/haipipe-board-page-for-section · one reader-ordered unit, bound to one venue allocation
LOAD TWO CONTRACTS FIRST.haipipe-board-page owns the base frame; haipipe-board-page-for-stage owns everything a chained, gated page needs: requires / style-from / provides, the managed Stage Contract span, the venue transfer tiers, and the rule that ONE stage reads the venue catalog. This file restates none of that; it adds only the section overlay, the same way adds a route over the topic core.
for-literature
The kind this variant covers: one page per section UNIT, in any family that edits by section.
kind produced by closes when
──────────────────────────────────────────────────────────────────────
Section a stage declaring runs: per-unit, ITS OWN human gate passes,
unit one page per reader-ordered unit judged against its venue floor
The paper family files these as S-Main-<n>-<slug> and S-Appendix-<letter>-<slug>; the application family's section-edit produces its own. "Section" is cross-family, which is why this type exists while for-main was rejected: Main names one family's region, section names a shape both have.
The type key. A section page declares page-type: section in its frontmatter, and the line is REQUIRED: S-Main-3-theory is letter for letter a stage filename, and the key is what routes the page here instead of stopping at -for-stage. The page-type: key beats the filename (base, type resolution step ③).
🔗 The venue chain, which is the reason this type exists
The chain is drawn once, in -for-stage's "ONE stage reads the venue page, and it is the venue stage": the QBv catalog is read once by the venue stage, the blueprint turns the desk's totals into per-section allocations, and every later page reads the blueprint. This page does not redraw it. What it adds is the unit grain: this page consumes ITS OWN allocation through its ### Venue contract block, a POINTER and never a copy. The blueprint line is BINDING for this unit alone; the style line is reference only; the override line SAYS whether a per-section desk rule exists, because such a rule outranks the blueprint.
The block is the typed record that makes this a type. Other stage pages carry a venue contract block too, S-Open-Pitch among them; what no other stage page carries is one PER READER-ORDERED UNIT, allocating that unit's own budget and shape. Its three lines answer the three questions a retarget asks: what binds, what merely advises, and what the desk itself said.
🎚 The section kind is a JOIN KEY, and the template is one of three things it joins
A section declares its KIND from a closed set the family owns (introduction, methods, results, discussion, appendix, and the set grows). The kind is the one name that ties three things together: the venue division, the blueprint block, and the template. Three owners wrote them at different times, and the kind is what lines them up:
section_kind = "theory" joins
① the venue page's MATCHING DIVISION for-venue cuts QBv Content by the
(QBv1 · Sec-3-Theory) venue's own reading index, so venue
and section pages match division-to-division
② the blueprint's per-kind block the allocation, BINDING for this unit
③ the (venue × kind) template a MISQ introduction and a Nature
introduction differ in SHAPE, not length
This join is what for-stage cannot provide and why this type exists: a stage page chains page-to-page; only a section page joins division-to-division with the venue's own catalog. The join stays TWO-HOP: ① is read by the venue stage alone, and this page consumes ② and ③. A section page never copies structure from a sibling section; it takes it from its own resolved template.
📥 The landing surface: where the three record types reach prose
A section page is where the other types' records become sentences:
citation binding (for-literature) → the \citep on the claiming sentence
value binding (for-value) → the number, with its provenance lane
display acceptance (for-display) → the \ref, and the placement record
points back at THIS sentence
A binding that landed on its topic page but never reached the owing sentence is this page's open work, visible at its gate. The hole grammar itself is the phases' (page-phases/); this page only says where the paid debt lands.
🔁 What a retarget rewrites
A section page is venue-ALIGNED: retargeting the work to another venue rewrites the venue contract block, re-resolves the template, and re-judges the prose against the new floor, while the section's claims, evidence bindings, and unit identity survive. The split between what survives and what rewrites is for-stage's venue-free against venue-aligned rule, applied at unit grain.
The template. NOT fixed here, and resolved by a PAIR, (venue, section_kind). The venue page's matching ### Sec-<n>-<Kind> division states the shape that desk expects, and the venue pack carries the skeleton. A MISQ introduction and a Nature introduction differ in SHAPE, not only in wording, so one template for this type would flatten the very difference a venue page exists to record. Both halves of the pair are declared in the page's own head, which is what makes the lookup mechanical rather than a hunt.
📂 Files
haipipe-board-page-for-section/
├── SKILL.md this variant contract
└── CHANGELOG.md version history
Owns no scripts. The frame is haipipe-board-page-for-stage; the catalog side is haipipe-board-page-for-venue; the record producers are -for-literature, -for-value, -for-display; the paper family's stage is paper/S06-main/section-edit/stage.md, which declares the closed kind set and the per-unit identity this contract requires but never contains.
