Skip to content

Hub member-facing website: browser-first society experience - #990

Merged
dp-web4 merged 1 commit into
mainfrom
prd/frontend-first-user-20261111
Nov 11, 2026
Merged

dp-web4 merged 1 commit into
mainfrom
prd/frontend-first-user-20261111

Conversation

@dp-web4

@dp-web4 dp-web4 commented Nov 11, 2026

Copy link
Copy Markdown
Owner

Proposes a member-facing Hub website PRD under canonical web4/hub, not the 4-hub mirror. Covers public browsing, governed joining, privacy-scoped profiles, consented introductions, contextual reputation, evidence, self-hosting and synthetic community acceptance. Coordinates with Hestia personal-app PRD. Docs-only; existing admin GUI is not represented as a public member website.

@dp-web4 dp-web4 left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NOVA independent exact-head review: GO as a proposed PRD, pending full exact-head CI. The new Hub website proposal explicitly distinguishes the existing operator/admin GUI from a public member website, puts product functionality in canonical web4/hub rather than its mirror, and preserves law/governance as the sole authority under a public site. Its acceptance scenario uses synthetic community profiles and consented introductions, with separate public/member/private fields; an observed/allowed act is not falsely equated to a verified external result. Strong non-negotiables: public browser access without compulsory Hestia install, no privileged local daemon/admin surface from the browser, and no self-declared skills presented as earned reputation. Scope clearly says no release, partner or implementation approval. Nonblocking implementation decisions still needed: membership authentication/account recovery and anti-abuse threat model; domain/origin trust and law display; data-retention/withdrawal versus immutable witnesses; AGPL boundaries and accessibility. A companion Hestia PRD #1561 is not yet merged, so the canonical blob/main link will resolve when that lands. Documentation-ready once CI green.

@dp-web4
dp-web4 merged commit d0b0dfd into main Nov 11, 2026
4 checks passed
dp-web4 added a commit that referenced this pull request Nov 11, 2026
…IC chapter) (#991)

Follow-up to #990, at dp's direction (2026-11-11). Every audience says "show
me what I can use"; nobody will co-develop; the human layer (channels,
discovery, committees/workgroups, events) is the unbuilt gap.

- 2a: the gap; the synthetic community becomes the rehearsal, a real group's
  use and verdict becomes the pass gate
- W11 coexistence with email/Slack/Zoom/Luma (Hub is not Slack-integrated
  today); W12 workgroups, offices and events
- 5b: AI Collective Portland -- inbound triage with owner+backup+nudges,
  event ownership, who-owns-what, the record as minutes; pass = one event
  cycle run by the chapter's own officers
- F0b slice first; officer and co-lead personas

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

dp-web4 commented Nov 12, 2026

Copy link
Copy Markdown
Owner Author

Implementation kickoff (2026-11-11): this merged PRD is followed by #992, the first public-visitor website shell in canonical hub/site/, and #993, binding the visitor site to real public projections and a real chapter officer workflow. The static preview is not called a launched Hub website; security and public/operator-plane separation are release gates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant