Review guide¶

The collection welcomes precise criticism: a counterexample, a missing assumption, an ambiguous term, a stronger explanation, or evidence that changes a conclusion. The most useful review identifies a particular claim and shows how the reasoning or evidence could improve.

Send a focused review · Discuss the research

Choose a starting point¶

For the institutional argument, read Governed Autonomous Institutions, especially its treatment of continuity, obligations, and founder control.

For relationships between systems, read the architecture synthesis. Its relationship classes distinguish what a source specifies from what a comparison suggests or an integration would still need to establish.

For a focused question, choose a topic paper, read its assumptions and evidence section, and follow its source guide. The glossary helps compare terminology across works.

For a reported result, identify the proposition, premises, input or model bound, checking method, outcome, and attribution. A source-reported run, a publicly inspectable derivation, and an independent reproduction provide different grounds for appraisal. The public research map points to public arguments and their scope qualifications. For a decision rule, test an allowed case, a forbidden case, and a case where the available evidence is insufficient; keep that evidential uncertainty distinct from whether an effect occurred.

Questions that can advance the work¶

Does a conclusion follow from the stated assumptions?
Does a worked example actually satisfy those assumptions?
Could another explanation account for the same observations?
Has provenance been confused with correctness, or capability with permission?
Does a proposed composition preserve the responsibilities of each system?
Does a recovery claim account for the actual outcome and any uncertain external effects?
Can a founder, administrator, or common controller bypass the claimed constraint?
What evidence would support or defeat the next stronger claim?

A simpler architecture that satisfies the same requirements is also a useful contribution. A conceptual disagreement and an observed implementation failure may challenge different premises; identifying which one is at issue makes the review more informative.

Submit a correction or counterexample¶

Email ajdurden@getcuttlefish.app for a concrete correction, missing citation, counterexample, or reproducible problem with the website, PDFs, or build. Include:

The paper, section, and publication edition.
The claim being examined and its relevant assumptions.
The reasoning, evidence, or example that challenges it.
The correction you propose, or the question that remains unresolved.

For a reading or download problem, identify the page or file and what failed. A short example that another reader can check is more useful than a general judgment about the entire collection.

Use the same email address for broader research questions, comparisons, and proposed evaluation methods. A discussion can develop a question before it is precise enough for a focused issue.

Work within the available evidence¶

The papers disclose conceptual arguments and selected evidence qualifications while withholding proprietary implementation details. Reviews can challenge the available material directly. When a conclusion would require confidential artifacts or new experiments, state the additional evidence needed rather than inferring the result.

The evidence guide explains the standards appropriate to specifications, reference implementations, formal results, observations, and independent reviews.

Share only material you are entitled to disclose. Keep credentials, customer data, confidential implementation details, unpublished inventions, and restricted third-party material out of review correspondence.

The collection is offered for reading and review under its rights notice. Participation in review does not grant an implementation or commercial-use license. For a permissions inquiry, describe the intended use by email at ajdurden@getcuttlefish.app without including confidential material.

How corrections become part of the collection¶

An accepted correction updates the maintained text, relevant citations or qualifications, and the change history. The website and affected PDFs are then regenerated together so that readers can identify the revised edition.

Changes to this collection revise its explanations. Changes to the requirements of an underlying research work belong to that work's own version history. The sources and method describe this relationship; the author statement identifies responsibility and editorial assistance.