Use this guide before opening a Discussion, Issue, or Pull Request.
Use GitHub Organization Discussions:
- Start Here / Orientation
- Ask About the Framework
Use GitHub Organization Discussions first.
Choose the closest category:
- Research Agenda
- Corpus & Construction Spine
- Results & World Readouts
- Predictions & Falsification
- TauLib / Formalization
A good challenge names:
- the page or artifact;
- the exact claim;
- what seems wrong or unsupported;
- what would count as failure;
- relevant evidence, citation, or counterexample.
Use Issues in the relevant repo.
Examples:
- broken link;
- wrong metadata;
- typo batch;
- bad redirect;
- raw template rendering;
- incorrect source mapping;
- build failure.
If it is conceptual or not yet concrete, start in Discussions.
If it is a concrete edit, open a Pull Request in the relevant repo.
Use Discussions -> Review Offers / Domain Expertise.
Say:
- area of expertise;
- artifact or page to review;
- whether review can be public;
- what kind of review you can offer;
- any conflict or affiliation to disclose.
Use:
sitefor website/source changes;taulibfor Lean/formalization;publicationsfor publication artifacts;researchfor scripts, notebooks, or import reports;communityfor guidelines/templates/routing.
Use email.
Email is appropriate for:
- institutional review;
- collaboration proposals;
- media;
- funding/support;
- sensitive critique;
- non-public context.
Org-level contact: hello@panta-rhei.site