From c75c69ef4fc0ea14136ac8f729a45c73109fe6dc Mon Sep 17 00:00:00 2001 From: Thorsten Fuchs Date: Mon, 4 May 2026 22:28:05 +0200 Subject: [PATCH 1/2] profile + README: v4 terminology + light brand-styling per 00b doctrine MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Aligns the org profile and root README to the locked v4 GitHub Doctrine (atlas/website/briefings/v4/00b_v4_IA_doctrine_GITHUB.md): Terminology updates (replaces v1 with v4 canonical): - Agenda obligations: "Problem Ledger / Recovery Requirements" -> "Structural Challenge Ledger / Core Semantics & Recovery" - Results consequences: "Problem Ledger Answers / Recovery Target Status" -> "Challenge Responses / Core Semantics & Recovery Status" - Agenda link: /program/research-agenda/ -> /agenda/ Brand styling (moderate-emoji discipline per doctrine ยง7): - ๐ŸŒ web/observatory; ๐Ÿงญ agenda; ๐Ÿ“š corpus; ๐Ÿ”ญ results; ๐Ÿชž verify; ๐Ÿ’ฌ engage; ๐Ÿ“ doctrine/discipline; ๐Ÿ“– publications; ๐Ÿ”ฌ formalization/research; โš™๏ธ build; โš–๏ธ open-research-alignment; ๐Ÿ“ฌ contact; ๐ŸŽฏ start-here. - One emoji per heading; semantic only; no decorative usage. Public Repositories table: - Removed `books` row (now PRIVATE; not visible to public visitors). - Removed `formalization` row (PRIVATE archive; not visible to public visitors). - Both legacy private repos do not need to appear in the public profile. Synchronization rule (doctrine ยง11.2): profile/README.md and README.md now carry identical canonical statement, spine, repos table, and locked language. Co-Authored-By: Claude Opus 4.7 (1M context) --- README.md | 55 +++++++++++++++++++++---------------------- profile/README.md | 59 ++++++++++++++++++++++------------------------- 2 files changed, 54 insertions(+), 60 deletions(-) diff --git a/README.md b/README.md index 39bfd07..745b394 100644 --- a/README.md +++ b/README.md @@ -6,22 +6,22 @@ The Panta Rhei Research Program is an independent open research program dedicate The public website is the research observatory. GitHub is the public substrate for source, formalization, publication artifacts, engagement, correction, contribution, and review workflows. -## Public research spine +## ๐Ÿงฉ Public Research Spine The public research system is organized around: -- **Discover** -- first-contact orientation into the research system. -- **Program** -- identity, doctrine, scope, status, and scrutiny posture. -- **Agenda** -- obligations: Problem Ledger, Recovery Requirements, Kernel/Model/Reality, and Construction Roadmap. -- **Corpus** -- construction body: Construction Spine, Registry, TauLib projection, books, and dependency graph. -- **Results** -- consequence layer: Landmark Results, World Readouts, Problem Ledger Answers, Recovery Target Status, Additional Derived Results, and Progress Against Agenda. -- **Verify** -- inspection routes: formalization, construction-step verification, bridge checks, predictions, falsification, release manifest, and assessment protocols. -- **Impact** -- conditional public relevance if the work survives inspection. -- **Engage** -- structured scrutiny, correction, contribution, communication, and participation without requiring endorsement. +- **Discover** โ€” first-contact orientation into the research system. +- **Program** โ€” identity, doctrine, scope, status, and scrutiny posture. +- **Agenda** โ€” obligations: Structural Challenge Ledger, Core Semantics & Recovery, Kernel/Model/Reality, and Construction Roadmap. +- **Corpus** โ€” construction body: Construction Spine, Registry, TauLib projection, books, and dependency graph. +- **Results** โ€” consequence layer: Landmark Results, World Readouts, Challenge Responses, Core Semantics & Recovery Status, Additional Derived Results, and Progress Against Agenda. +- **Verify** โ€” inspection routes: formalization, construction-step verification, bridge checks, predictions, falsification, release manifest, and assessment protocols. +- **Impact** โ€” conditional public relevance if the work survives inspection. +- **Engage** โ€” structured scrutiny, correction, contribution, communication, and participation without requiring endorsement. -## Artifacts & Releases +## ๐Ÿ“– Artifacts & Releases -Publications are the stable artifact layer: +Publications are the stable artifact and release layer: - Research Monographs - Research Papers @@ -32,26 +32,24 @@ Publications are the stable artifact layer: - Release Artifacts - Errata -## Public repositories +## ๐Ÿ”ฌ Public Repositories | Repository | Role | |---|---| | [`site`](https://github.com/Panta-Rhei-Research/site) | Jekyll source for `panta-rhei.site`, the public research observatory. | -| [`taulib`](https://github.com/Panta-Rhei-Research/taulib) | Lean 4 formalization surface; current metrics and trusted-base details live in the Release Manifest. | +| [`taulib`](https://github.com/Panta-Rhei-Research/taulib) | Lean 4 formalization surface; current metrics and trusted-base details live in the [Release Manifest](https://panta-rhei.site/verify/release-manifest/). | | [`publications`](https://github.com/Panta-Rhei-Research/publications) | Source and release artifacts for monographs, papers, notes, briefings, white papers, ledgers, release artifacts, and errata. | | [`research`](https://github.com/Panta-Rhei-Research/research) | Public workspace for notebooks, scripts, import reports, data transforms, experiments, and exploratory supporting material. | | [`community`](https://github.com/Panta-Rhei-Research/community) | Public engagement hub: onboarding, routing, discussion guidelines, review guides, and contribution policies. | | [`.github`](https://github.com/Panta-Rhei-Research/.github) | Organization profile and shared community-health defaults. | -| [`books`](https://github.com/Panta-Rhei-Research/books) | Legacy / archival book publication surface; current artifacts live in `publications`. | -| `formalization` | Archived transitional formalization surface; superseded by `taulib` for live formalization. | -## This repository contains +## โš™๏ธ This Repository Contains - `profile/README.md`: the organization profile displayed on [github.com/Panta-Rhei-Research](https://github.com/Panta-Rhei-Research). - Shared community-health files for code of conduct, support, security, issue templates, and pull request templates. - Public routing defaults for Issues and Pull Requests across organization repositories. -## Engagement without endorsement +## ๐Ÿ“ Engagement Without Endorsement We do not ask first for agreement. @@ -59,20 +57,19 @@ We ask for structured open-research engagement: careful reading, public question 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. -## Verification note +## ๐Ÿชž Verification Note Formalization, artifacts, and repository integrity checks make parts of the program inspectable. They do not by themselves establish empirical truth, bridge adequacy, semantic correspondence, peer review, or external scientific acceptance. -For current formalization metrics, trusted-base details, and verification boundaries, see the Release Manifest: -https://panta-rhei.site/verify/release-manifest/ +For current formalization metrics, trusted-base details, and verification boundaries, see the [Release Manifest](https://panta-rhei.site/verify/release-manifest/). -## Links +## ๐ŸŽฏ Links -- **Website:** https://panta-rhei.site -- **Agenda:** https://panta-rhei.site/program/research-agenda/ -- **Corpus:** https://panta-rhei.site/corpus/ -- **Results:** https://panta-rhei.site/results/ -- **Verify:** https://panta-rhei.site/verify/ -- **Engage:** https://panta-rhei.site/engage/ -- **Public discussions:** https://github.com/orgs/Panta-Rhei-Research/discussions -- **Contact:** hello@panta-rhei.site +- ๐ŸŒ **Website:** https://panta-rhei.site +- ๐Ÿงญ **Agenda:** https://panta-rhei.site/agenda/ +- ๐Ÿ“š **Corpus:** https://panta-rhei.site/corpus/ +- ๐Ÿ”ญ **Results:** https://panta-rhei.site/results/ +- ๐Ÿชž **Verify:** https://panta-rhei.site/verify/ +- ๐Ÿ’ฌ **Engage:** https://panta-rhei.site/engage/ +- ๐Ÿ’ฌ **Public discussions:** https://github.com/orgs/Panta-Rhei-Research/discussions +- ๐Ÿ“ฌ **Contact:** hello@panta-rhei.site diff --git a/profile/README.md b/profile/README.md index fbfe474..04fc3ca 100644 --- a/profile/README.md +++ b/profile/README.md @@ -4,7 +4,7 @@ The Panta Rhei Research Program is an independent open research program dedicate The public website is the research observatory. GitHub is the public substrate for source, formalization, publication artifacts, engagement, correction, contribution, and review workflows. -## Public research observatory blueprint +## ๐ŸŒ Public Research Observatory Blueprint Package 3 documents the implementation architecture behind this organization and the public website: @@ -14,33 +14,33 @@ Package 3 documents the implementation architecture behind this organization and The blueprint describes GitHub as a source, discussion, correction, and contribution substrate. It does not imply that GitHub, the website architecture, or any infrastructure provider validates the scientific theory. -## Start here +## ๐ŸŽฏ Start Here -- Website: https://panta-rhei.site -- Agenda: https://panta-rhei.site/program/research-agenda/ -- Corpus: https://panta-rhei.site/corpus/ -- Results: https://panta-rhei.site/results/ -- Verify: https://panta-rhei.site/verify/ -- Engage: https://panta-rhei.site/engage/ -- Public discussions: https://github.com/orgs/Panta-Rhei-Research/discussions -- Contact: hello@panta-rhei.site +- ๐ŸŒ **Website:** https://panta-rhei.site +- ๐Ÿงญ **Agenda:** https://panta-rhei.site/agenda/ +- ๐Ÿ“š **Corpus:** https://panta-rhei.site/corpus/ +- ๐Ÿ”ญ **Results:** https://panta-rhei.site/results/ +- ๐Ÿชž **Verify:** https://panta-rhei.site/verify/ +- ๐Ÿ’ฌ **Engage:** https://panta-rhei.site/engage/ +- ๐Ÿ’ฌ **Public discussions:** https://github.com/orgs/Panta-Rhei-Research/discussions +- ๐Ÿ“ฌ **Contact:** hello@panta-rhei.site -## Public research spine +## ๐Ÿงฉ Public Research Spine The public research system is organized around: -- **Discover** -- first-contact orientation into the research system. -- **Program** -- identity, doctrine, scope, status, and scrutiny posture. -- **Agenda** -- obligations: Problem Ledger, Recovery Requirements, Kernel/Model/Reality, and Construction Roadmap. -- **Corpus** -- construction body: Construction Spine, Registry, TauLib projection, books, and dependency graph. -- **Results** -- consequence layer: Landmark Results, World Readouts, Problem Ledger Answers, Recovery Target Status, Additional Derived Results, and Progress Against Agenda. -- **Verify** -- inspection routes: formalization, construction-step verification, bridge checks, predictions, falsification, release manifest, and assessment protocols. -- **Impact** -- conditional public relevance if the work survives inspection. -- **Engage** -- structured scrutiny, correction, contribution, communication, and participation without requiring endorsement. +- **Discover** โ€” first-contact orientation into the research system. +- **Program** โ€” identity, doctrine, scope, status, and scrutiny posture. +- **Agenda** โ€” obligations: Structural Challenge Ledger, Core Semantics & Recovery, Kernel/Model/Reality, and Construction Roadmap. +- **Corpus** โ€” construction body: Construction Spine, Registry, TauLib projection, books, and dependency graph. +- **Results** โ€” consequence layer: Landmark Results, World Readouts, Challenge Responses, Core Semantics & Recovery Status, Additional Derived Results, and Progress Against Agenda. +- **Verify** โ€” inspection routes: formalization, construction-step verification, bridge checks, predictions, falsification, release manifest, and assessment protocols. +- **Impact** โ€” conditional public relevance if the work survives inspection. +- **Engage** โ€” structured scrutiny, correction, contribution, communication, and participation without requiring endorsement. -## Artifacts & Releases +## ๐Ÿ“– Artifacts & Releases -Publications are the stable artifact layer: +Publications are the stable artifact and release layer: - Research Monographs - Research Papers @@ -51,20 +51,18 @@ Publications are the stable artifact layer: - Release Artifacts - Errata -## Public repositories +## ๐Ÿ”ฌ Public Repositories | Repository | Role | |---|---| | [`site`](https://github.com/Panta-Rhei-Research/site) | Jekyll source for `panta-rhei.site`, the public research observatory. | -| [`taulib`](https://github.com/Panta-Rhei-Research/taulib) | Lean 4 formalization surface; current metrics and trusted-base details live in the Release Manifest. | +| [`taulib`](https://github.com/Panta-Rhei-Research/taulib) | Lean 4 formalization surface; current metrics and trusted-base details live in the [Release Manifest](https://panta-rhei.site/verify/release-manifest/). | | [`publications`](https://github.com/Panta-Rhei-Research/publications) | Source and release artifacts for monographs, papers, notes, briefings, white papers, ledgers, release artifacts, and errata. | | [`research`](https://github.com/Panta-Rhei-Research/research) | Public workspace for notebooks, scripts, import reports, data transforms, experiments, and exploratory supporting material. | | [`community`](https://github.com/Panta-Rhei-Research/community) | Public engagement hub: onboarding, routing, discussion guidelines, review guides, and contribution policies. | | [`.github`](https://github.com/Panta-Rhei-Research/.github) | Organization profile and shared community-health defaults. | -| [`books`](https://github.com/Panta-Rhei-Research/books) | Legacy / archival book publication surface; current artifacts live in `publications`. | -| `formalization` | Archived transitional formalization surface; superseded by `taulib` for live formalization. | -## Engagement without endorsement +## ๐Ÿ“ Engagement Without Endorsement We do not ask first for agreement. @@ -72,14 +70,13 @@ We ask for structured open-research engagement: careful reading, public question 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. -## Verification note +## ๐Ÿชž Verification Note Formalization, artifacts, and repository integrity checks make parts of the program inspectable. They do not by themselves establish empirical truth, bridge adequacy, semantic correspondence, peer review, or external scientific acceptance. -For current formalization metrics, trusted-base details, and verification boundaries, see the Release Manifest: -https://panta-rhei.site/verify/release-manifest/ +For current formalization metrics, trusted-base details, and verification boundaries, see the [Release Manifest](https://panta-rhei.site/verify/release-manifest/). -## Open research alignment +## โš–๏ธ Open Research Alignment This GitHub organization supports the program's open-research commitments: transparency, scrutiny, critique, reproducibility, accountability, collaboration, and responsible reuse. @@ -87,4 +84,4 @@ The website publishes the structured research object. GitHub provides the public --- -Panta Rhei - Everything Flows. +Panta Rhei โ€” Everything Flows. From eaf9bb08b0aee8d261f0b8d82257c9802cfbe5da Mon Sep 17 00:00:00 2001 From: Thorsten Fuchs Date: Mon, 4 May 2026 22:36:57 +0200 Subject: [PATCH 2/2] profile + README: align spine sublabels to canonical site copy Cascading fix from 00b doctrine correction (atlas commit 3091ab7). Updates: - Agenda spine sublabel: "Structural Challenge Ledger, Core Semantics & Recovery" -> "Core Semantics, Structural Challenge Ledger" (canonical site ordering; Core Semantics first because it asks the prior question) - Results spine sublabel: "Core Semantics & Recovery Status" -> "Core Semantics Status" (the public-facing short-form label) The site (homepage, agenda root, results root) uses these exact phrasings; this PR brings the org profile into alignment. Co-Authored-By: Claude Opus 4.7 (1M context) --- README.md | 4 ++-- profile/README.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 745b394..76273f7 100644 --- a/README.md +++ b/README.md @@ -12,9 +12,9 @@ The public research system is organized around: - **Discover** โ€” first-contact orientation into the research system. - **Program** โ€” identity, doctrine, scope, status, and scrutiny posture. -- **Agenda** โ€” obligations: Structural Challenge Ledger, Core Semantics & Recovery, Kernel/Model/Reality, and Construction Roadmap. +- **Agenda** โ€” obligations: Core Semantics, Structural Challenge Ledger, Kernel/Model/Reality, and Construction Roadmap. - **Corpus** โ€” construction body: Construction Spine, Registry, TauLib projection, books, and dependency graph. -- **Results** โ€” consequence layer: Landmark Results, World Readouts, Challenge Responses, Core Semantics & Recovery Status, Additional Derived Results, and Progress Against Agenda. +- **Results** โ€” consequence layer: Landmark Results, World Readouts, Challenge Responses, Core Semantics Status, Additional Derived Results, and Progress Against Agenda. - **Verify** โ€” inspection routes: formalization, construction-step verification, bridge checks, predictions, falsification, release manifest, and assessment protocols. - **Impact** โ€” conditional public relevance if the work survives inspection. - **Engage** โ€” structured scrutiny, correction, contribution, communication, and participation without requiring endorsement. diff --git a/profile/README.md b/profile/README.md index 04fc3ca..bb07e8c 100644 --- a/profile/README.md +++ b/profile/README.md @@ -31,9 +31,9 @@ The public research system is organized around: - **Discover** โ€” first-contact orientation into the research system. - **Program** โ€” identity, doctrine, scope, status, and scrutiny posture. -- **Agenda** โ€” obligations: Structural Challenge Ledger, Core Semantics & Recovery, Kernel/Model/Reality, and Construction Roadmap. +- **Agenda** โ€” obligations: Core Semantics, Structural Challenge Ledger, Kernel/Model/Reality, and Construction Roadmap. - **Corpus** โ€” construction body: Construction Spine, Registry, TauLib projection, books, and dependency graph. -- **Results** โ€” consequence layer: Landmark Results, World Readouts, Challenge Responses, Core Semantics & Recovery Status, Additional Derived Results, and Progress Against Agenda. +- **Results** โ€” consequence layer: Landmark Results, World Readouts, Challenge Responses, Core Semantics Status, Additional Derived Results, and Progress Against Agenda. - **Verify** โ€” inspection routes: formalization, construction-step verification, bridge checks, predictions, falsification, release manifest, and assessment protocols. - **Impact** โ€” conditional public relevance if the work survives inspection. - **Engage** โ€” structured scrutiny, correction, contribution, communication, and participation without requiring endorsement.