|
1 | 1 | # Panta Rhei Community Hub |
2 | 2 |
|
3 | | -This repository is the public engagement hub of the Panta Rhei Research Program. |
| 3 | +This repository is the public engagement hub of the **Panta Rhei Research Program**. |
4 | 4 |
|
5 | | -It exists for onboarding, routing, discussion norms, review guidance, and contribution policies. |
| 5 | +The Panta Rhei Research Program is an independent open research program dedicated to building a coherent theory of reality. |
| 6 | + |
| 7 | +Engage is where openness becomes operational: structured scrutiny, correction, review, communication, contribution, and participation without requiring endorsement. |
6 | 8 |
|
7 | 9 | The primary public conversation space is [GitHub Organization Discussions](https://github.com/orgs/Panta-Rhei-Research/discussions). |
8 | 10 |
|
9 | 11 | ## Engagement without endorsement |
10 | 12 |
|
11 | | -Participation does not imply endorsement. |
12 | | - |
13 | | -You can ask a question, challenge a claim, report an error, offer review, improve documentation, or contribute infrastructure without accepting the framework. |
| 13 | +We do not ask first for agreement. |
14 | 14 |
|
15 | | -The most useful engagement is structured attention: |
| 15 | +We ask for structured open-research engagement: careful reading, public questions, critique, reproducibility checks, domain review, correction, infrastructure contribution, and responsible communication. |
16 | 16 |
|
17 | | -- read carefully; |
18 | | -- inspect claims; |
19 | | -- challenge weak links; |
20 | | -- report errors; |
21 | | -- review bounded areas; |
22 | | -- contribute tooling or documentation; |
23 | | -- communicate responsibly; |
24 | | -- support continuation without implying agreement. |
| 17 | +Participation does not imply endorsement of the framework. A reader may ask a question without accepting the theory. A reviewer may challenge a result without joining the program. A contributor may improve documentation, metadata, tooling, packaging, or formalization without endorsing any conclusion. |
25 | 18 |
|
26 | 19 | ## Where to start |
27 | 20 |
|
@@ -51,3 +44,22 @@ Use Issues for concrete defects or actionable corrections. |
51 | 44 | Use Pull Requests for proposed changes. |
52 | 45 |
|
53 | 46 | Use email for private, institutional, media, sensitive, or support-related contact. |
| 47 | + |
| 48 | +## Where to post |
| 49 | + |
| 50 | +| Need | Route | |
| 51 | +|---|---| |
| 52 | +| Public question or discussion | [Organization Discussions](https://github.com/orgs/Panta-Rhei-Research/discussions) | |
| 53 | +| Concrete defect in website | [`site` issue](https://github.com/Panta-Rhei-Research/site/issues) | |
| 54 | +| Concrete Lean/formalization defect | [`taulib` issue](https://github.com/Panta-Rhei-Research/taulib/issues) | |
| 55 | +| Publication artifact correction | [`publications` issue](https://github.com/Panta-Rhei-Research/publications/issues) | |
| 56 | +| Research script/notebook issue | [`research` issue](https://github.com/Panta-Rhei-Research/research/issues) | |
| 57 | +| Discussion norm / routing / contribution policy | [`community` issue](https://github.com/Panta-Rhei-Research/community/issues) | |
| 58 | +| Private, institutional, media, sensitive, or support contact | hello@panta-rhei.site or the website contact routes | |
| 59 | + |
| 60 | +## Verification note |
| 61 | + |
| 62 | +Engagement, review, and contribution workflows make the program more inspectable. They do not by themselves establish empirical truth, bridge adequacy, semantic correspondence, peer review, or external scientific acceptance. |
| 63 | + |
| 64 | +For current formalization metrics, trusted-base details, and verification boundaries, see the Release Manifest: |
| 65 | +https://panta-rhei.site/verify/release-manifest/ |
0 commit comments