Changelog

The reason-commons skill now generates standalone HTML diagrams with inline SVG, so accepted trees open in a browser without Graphviz, Node, or a Mermaid renderer.

The new reason-commons skill helps individuals and groups develop Thinking Process trees through concise conversations, retaining contributors' ideas and unfinished reasoning. Explicitly accepted changes now preserve a numbered snapshot and produce two diagrams: the accepted tree and its latest changes, with earlier wording and removed connections visible for review.

Sessions offer labeled choices to refine the reasoning, explore difficulties, capture another thought, or view the tree, with a compact status line showing the driver, other participants, and current focus. Tree requests include clearly labeled proposals so the reasoning is visible before anything is accepted. Natural review checkpoints now invite users to test, revise, continue developing, or provisionally accept a coherent proposal.

Collaboration sessions now resume through the existing Beads handoff, with outstanding reasoning linked to work items and task completion kept separate from endorsement.

Standalone LTP previews now open with the Current Reality tree expanded, showing the source's causal links and feedback loops immediately while leaving disconnected observations separate.

You can now export an .ltp.yaml candidate as a standalone HTML dashboard and open it directly in the browser with the ltp-visualize skill. A local-server preview is available too; neither path changes the candidate or imports it into a Reason Commons space.

The landing page now offers a low-volume way to register interest in future Reason Commons updates. It records the request without starting a newsletter or sending email.

ltp/reason-commons/reason-commons.ltp.yaml is Reason Commons — the group developing the app — as one Logical Thinking Process model in the interchange format the app imports, written with ltp-project from the app repository's docs and features, this repository's own statements of purpose, and every open issue here. All seventeen open issues sit in its transition tree with the need and expected effect their authors stated; the report beside it says where each landed and why, what the model does not claim, and which calls are still a person's. It is a candidate until ratified in the Reason Commons commons; the folder is kept off the published site because the reviewing surface for a candidate is GitHub. NEXT.md is now generated from the model's transition tree by the app repository's bun scripts/next-from-ltp.ts — actions nothing precedes first, then the rest in the order their links give — so what to do next is a consequence of the reasoning rather than a second list.

There is now one way to write an LTP model with an AI: skills/ltp-project, which produces the Reason Commons *.ltp.yaml project file — the same interchange document the app imports and exports as JSON or YAML, version and event history included — from a PDF, a Markdown document, a repository's plans and issues, a roadmap or meeting notes, with a report of every judgment call. It is a byte-identical mirror of the canonical skill in Promise-Foundation/reason-commons; edit it there and copy it here. The older project-ltp skill is deprecated: its ltp-model.yaml was a second, incompatible format that the app cannot import and that carries no history, and its GitHub issue sync is now done by the Reason Commons projection, which writes and reconciles managed issues itself. The skill's read-only dashboard stays as a viewer for the legacy models still bundled here.

The 2R Research Circle project is gone from the dashboard: its model was the July 2026 analysis, superseded by the live Reason Commons space connected to the 2R-Research repository, which exports the current model to that repository as .reason-commons/<space-id>.ltp.json. The throughput track that fed it — counted from this repository's Git history — went with it, so throughput.config.json now holds no tracks and the generator tolerates that. The dashboard was rebuilt and republished; the Second Renaissance and the software-engineer example remain.

The annotation demo now opens on “Can the world switch to clean energy in time?” with three linked IEA reports mapped to specific claims about emissions pace, renewable scale, grids, electrification and nuclear tradeoffs. The closing now leads to an on-page appendix with AI-control evidence from METR, the International AI Safety Report and Eliezer Yudkowsky, plus the original randomized Ctrip remote-work experiment.

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.

The dashboard now keeps the open project and tree in the URL, so a single view — the Second Renaissance current reality tree, say — can be linked to directly instead of "open the dashboard, pick the project, click Reality", and Back and Forward walk the views visited. Stale links degrade rather than break: a tree the project has not modelled opens its overview, and an unknown project lands on the picker. The shape of the links is in docs/dashboard.md.