Your accumulated reasoning should survive a change of tool or model. Portability is part of what a commons owes its participants.
What can travel today
The application supports JSON and YAML reasoning exports. The 1.2 format carries the model and its history, plus supported decision and learning records: retained objections, scoped reliance, expectations, executions, observations and assessments. Coverage states what was read and what was omitted. It concerns records available to the exporter, not a guarantee of access to every record in a space.
The extraction skill uses the same envelope for candidate reasoning and structured capture notes. Source excerpts, uncertainty and reasons for withholding a relationship can travel together. A well-formed file is not proof that an interpretation is right.
On import, you can inspect an inherited decision, its original case, later results and remaining objections. Supported graph changes still go through local review. The source-retention migration saves the parsed original alongside the proposal so later exports can carry it forward; deployments need that migration before using this import path. Reading another commons' record does not give it authority here. Full space restoration is not implemented.
Carried digest checks detect certain inconsistencies. They do not authenticate the source or prove that an expectation existed before its outcome.
Download an example reasoning record. This is a real interchange-format sample about project delivery, separate from the illustrative Garden story.
Download a synthetic decision and learning record, which preserves a limited pilot decision, a retained objection, a failed prediction and a later hold. It demonstrates the format, not an experimental result.
Who can read a commons
The hosted prototype is currently broadly readable: signed-in users can read reasoning spaces outside their own teams. Spaces marked public are also readable without an account. Team membership controls participation separately from reading access.
Do not assume that an unlisted space is private. Use non-sensitive questions in this early version. Confidential deployments and access guarantees require their own verified configuration.
The web app is one way in
The project is developing toward a reasoning platform whose records can outlive its interface, host, database, and model provider. Different clients should be able to work with the same governed record.
That direction does not mean that integrations with every chat service exist today. In particular, this site's Substack mirror republishes public articles; it does not ingest comments, confirm commenters' meaning, or turn discussion into accepted reasoning.
The longer view
Distinct commons could eventually exchange reasoning without sharing authority or surrendering their own norms. Federation is a direction for the project, not an available network being advertised here.
Read the manifesto for the institutional argument, and the protocol for the proposed semantics.