profile/README: founder welcome on-ramp (replaces Package 3 paragraph) (#7)

* profile/README: replace Package 3 paragraph with founder welcome on-ramp

Replaces the "Public Research Observatory Blueprint" section with a warm,
near-first-person Welcome from the founders. The intent is a softer first-
contact landing for visitors arriving at github.com/Panta-Rhei-Research:

- States who built this and why, in two voices ("we" + signed names).
- Routes first-time visitors directly to the public Discussions board as
  the easiest on-ramp.
- Lists the three contributor-facing routes (issues, PRs, email) with
  emoji bullets matching doctrine §7.1 (🐛 defects, 🔁 changes, 📬 contact).
- Preserves the locked engagement-without-endorsement signal inline:
  "Participation does not imply endorsement."
- Signs off as "— Thorsten & Anna-Sophie" to anchor the founder voice.

The Package 3 references (Public Research Observatory white paper, Newsroom
brief, Inspection Observatory page) are retained in a footnote-style
blockquote at the end of the Welcome, so they remain one click away
without occupying the first-contact load-bearing paragraph.

Org-profile-specific change: only `profile/README.md` is edited. The root
`README.md` of the .github repo serves a different purpose (repo-self-
description) and does not carry the founder welcome — synchronization rule
in doctrine §11.2 covers canonical statement and v4 vocabulary, not the
profile's first-contact greeting.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* profile/README: trim white-paper footnote — drop press-kit framing

Per user feedback, the post-Welcome blockquote should keep the white paper
link only and lose the Newsroom brief + Inspection Observatory page links.
Those latter two carried media-kit / press-briefing flavoring that doesn't
belong on the org-page first-contact greeting.

Reframed from "documented separately in [three links]" to a friendlier
single pointer: "If you'd like a sense of how this is set up, the white
paper *Building a Public Research Observatory* walks through the
architecture." Sentence order on the GitHub-doesn't-validate disclaimer
flipped so the substantive sentence carries the disclaimer (carries source +
formalization + conversation; does not validate).

Net change: -2 links, +friendlier framing, same disclaimer.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: ThorFuchs

profile/README.md

@@ -4,15 +4,23 @@ 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
+## Welcome
 
-Package 3 documents the implementation architecture behind this organization and the public website:
+We — Thorsten and Anna-Sophie — built this organization as the public substrate for the program. The website at [panta-rhei.site](https://panta-rhei.site) is the research observatory; this GitHub org is where the source, formalization, artifacts, and conversation happen in the open.
 
-- White paper: https://panta-rhei.site/publications/white-papers/building-a-public-research-observatory/
-- Newsroom brief: https://panta-rhei.site/media/public-research-observatory-brief/
-- Inspection Observatory: https://panta-rhei.site/program/about/inspection-observatory/
+If you've found your way here, the easiest first move is the [public Discussions board](https://github.com/orgs/Panta-Rhei-Research/discussions) — ask anything, including hard or critical questions. We read what gets posted there.
 
-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.
+For more concrete engagement:
+
+- 🐛 **Found a defect or have a correction to suggest?** Open an issue on the relevant repo (`site`, `taulib`, `publications`, `research`, or `community`).
+- 🔁 **Want to propose a change?** Open a pull request against the relevant repo.
+- 📬 **Private, institutional, media, or sensitive contact?** Email [`hello@panta-rhei.site`](mailto:hello@panta-rhei.site).
+
+You don't need to agree with the framework to engage — curiosity, scrutiny, or pure skepticism are equally good reasons to be here. *Participation does not imply endorsement.*
+
+— Thorsten & Anna-Sophie
+
+> If you'd like a sense of how this is set up, the white paper [*Building a Public Research Observatory*](https://panta-rhei.site/publications/white-papers/building-a-public-research-observatory/) walks through the architecture. GitHub carries the source, the formalization, and the conversation; it does not validate the scientific theory.
 
 ## 🎯 Start Here