| name | haipipe-board-page-for-meeting |
| description | The VARIANT contract for a MEETING Page: one page per conversation worth keeping, generated by cli/meetingpage.py from a dated note. It loads haipipe-board-page for the base frame and adds only what a record of talk needs: the cast, the dated record in the speakers' own words, and the routing rule that a decision spoken in a meeting is not RULED until it lands as a Decision Now row or record on the page that owns the subject. A meeting page decides nothing and is never counted in a board's settled total. Use when writing or fixing a Meeting page, when a spoken decision never reached its owning page, when a meeting page starts accumulating Aims as if it were a decision page, or when the record paraphrases what a person actually said. Trigger: meeting page, Meeting-1, meeting note, record what was said, route the decision, minutes, /haipipe-board-page-for-meeting. |
| metadata | {"version":"0.1.0","last_updated":"2026-08-05","summary":"First cut, on JL's 260805 admission; closes the gap QB6 §1.1 had recorded since the page existed."} |
/haipipe-board-page-for-meeting · talk is recorded here, and ruled elsewhere
LOAD haipipe-board-page FIRST. It owns the base frame. This file adds only what a meeting record needs, and it is short because a meeting page owns almost nothing.
The kind this variant covers: one page per conversation worth keeping.
kind filename generated by closes when
────────────────────────────────────────────────────────────────────────
Meeting Meeting-<n>-<slug> cli/meetingpage.py the record is faithful AND
from a dated note every decision in it is ROUTED
· NEVER counted in settled totals
Like a mirror page, it does not take the base's create a new page steps: the generator writes it and registers it.
🗣 What the page owes: fidelity, then routing
Fidelity: the cast by their own initials, the date, and what was said in the speakers' own words. A paraphrase that sharpens what someone said is a record of a meeting that did not happen; quote, then interpret below the quote if needed.
Routing, the one rule this type exists for: a decision spoken in a meeting is NOT RULED until it lands on the page that owns the subject.
spoken in the meeting ruled on the board
────────────────────── ─────────────────────────────────
"let's split QC then" ──route──▶ the owning page's Decision Now row,
ticked with the date and the words
the meeting page keeps the OWNING page keeps the ruling;
the QUOTE + a pointer `haipipe-board-routing` is the verb
A decision that lives only in the meeting record has the same defect as one that lives only in chat: no Blocks, no Default, no trace of the options weighed, and nobody finds it when they open the owning page. The meeting page's closing test is therefore mechanical: every decision-shaped line either points at where it landed or is marked not-yet-routed, and the second set is the page's only open work.
🚫 What a meeting page never does
It never carries Aims of its own beyond the routing debt, never argues a position, never closes a question, and never counts toward the board's settled total. The moment a meeting note starts growing an argument, that argument is a Q page waiting to be proposed, and haipipe-board-routing proposes it.
The template. template.md, beside this file. ONE template serves every page of this type: two pages of it differ in what they say, never in what shape they are, so nothing has to be resolved before writing one. Copy it, fill every <slot>, and delete each RULE comment as you satisfy it.
📂 Files
haipipe-board-page-for-meeting/
├── SKILL.md this variant contract
└── CHANGELOG.md version history
Owns no scripts. The generator is haipipe-board/cli/meetingpage.py; the routing verb is haipipe-board-routing; the base is haipipe-board-page.
