Sep 4, 2026

The room's contributions, proposed against the tree

The review page: Priya Raghavan's contribution quoted at full size on the left with the reader's proposed change beneath it, and on the right the Second Renaissance goal tree as an indented outline — the path from the goal down to the condition under discussion at full strength, the rest of the tree quiet, a dashed rust challenge attached to that condition, and three proposals the room has already accepted sitting solid in green further up.

A new contribution-proposals skill turns a batch of raw participant contributions — a Google Doc export, a form dump, whatever a room actually wrote — into one reviewable proposal each for how it might extend, support, challenge, or fail to fit an existing tree, and renders the set as a page the group works through together: accept, edit, or reject, with accepted proposals turning from dashed to solid and staying, so by the last one the tree on screen is the original plus everything the room agreed to. Contributions are quoted verbatim, the machine's reading is labelled as the machine's, and nowhere to put it is a first-class result rather than a failure — a contribution the tree cannot hold may be the most useful thing in the batch. Nothing merges: ltp/ltp-model.yaml is read-only to the whole pipeline, and refreshing the page throws the room's decisions away, which is the honest behaviour for a tool with no standing over the tree. The skill builds to a stamped, unpublished test route by default, so a half-read batch can be served and clicked through before anything touches the page that ships. Reading a contribution that arrives in its own vocabulary — a permaculture cooperative, a mutual credit network — is most of the work, and the skill's guidance is about finding the operative claim inside the experience that earned it rather than reaching for the nearest keyword. Ancestors of whatever is under discussion stay at full strength up to the root, because a claim you cannot trace to a goal is not one anyone can review. Built for Demo C of the talk, where it ships with a rehearsal build from nine contributions. Running Demo C is the runbook for presenting it without having built it.