Review the Work
A bounded review route for domain experts, formalizers, careful readers, infrastructure contributors, and public reviewers.
Help inspect a bounded part of the research program.
The program is large. A useful review should be bounded.
Participation does not imply endorsement. A reviewer may help inspect one artifact, route, claim, module, status label, or correction path without endorsing the theory as a whole.
Review without endorsement
Review is one form of structured attention.
A useful review is bounded: it names the artifact, claim, result, note, construction step, proof route, or formalization surface being inspected.
Participation does not imply endorsement. A reviewer may inspect one part of the program without accepting the theory as a whole.
Review routes moved into Verify
The former standalone reviewer packet has been folded into the observatory’s native inspection routes.
Use:
- How to Verify — first-pass inspection route.
- Assessment Protocols — structured manual and LLM-assisted review workflows.
- Verify the Construction Spine — step-by-step construction inspection.
- This page — how to offer, route, and scope bounded review.
Review remains welcome. It is now routed through Verify and Engage rather than one standalone kit.
For package-level review context, use the three citable white papers: Inspection Architecture for High-Scope Open Research, The Shape of a Theory of Reality, and Building a Public Research Observatory for High-Scope Open Research.
Bounded review as structured attention
A useful review is bounded: it names the page, artifact, result, note, proof route, or formalization surface being inspected.
What can be reviewed
You can review:
- one Structural Challenge or Challenge Response;
- one Core Semantics / Recovery item;
- one Construction Spine step;
- one Result page;
- one Research Note;
- one TauLib module;
- one Numerical Physics Ledger entry;
- one Public-Good Briefing;
- one website lane or page template.
Review modes
- mathematical review;
- physics review;
- life / biology review;
- metaphysics / philosophy review;
- formalization review;
- source/import review;
- editorial review;
- accessibility review;
- reproducibility review;
- falsification review.
What to include
A useful review includes:
- the target page or artifact;
- review mode;
- summary verdict;
- major issues;
- minor issues;
- suggested fixes;
- open questions;
- whether the review may be cited publicly.
Where to post
Public review offers belong in GitHub Discussions under Review Offers / Domain Expertise.
Concrete fixes belong in Issues or Pull Requests.
Use email for private review reports, institutional review context, media-related review, sensitive critique, or any review that cannot be public yet.
Review route examples
| Target | Best first route |
|---|---|
| Structural Challenge / Challenge Response | Public Discussions or domain-specific review email |
| Core Semantics / Recovery item | Public Discussions, then Verify or Results route if needed |
| TauLib module | TauLib issue or pull request for concrete formalization changes |
| Research Note | Research Notes discussion category, or errata route for corrections |
| Public-Good Briefing | Impact & Public-Good Briefings discussion category |
| Website template or metadata | Site issue or pull request |
Save or share this page for inspection
Download a portable dossier, copy a reviewer note, or send this page to someone who can inspect it.