Skip to content

Hub first-user F1: serve public site from governed public projection, then add chapter ownership #993

Open

Description

@dp-web4

Implementation lane from merged #990/#991 and first static shell #992.

F1a — true public site: have Hub daemon serve public website on public plane; server-render/provide only independently selected public projections: society name, purpose, charter/law, admission expectations and lock/degraded status. Reuse existing public identity/charter data. Never expose admin, member-only, self-only, or secret data. Add CSP, request-bound privacy tests and no JS/login required for read.

F1b — chapter utility: member-authenticated officer/committee roster + event owner/backup/status + inbound triage assignment/nudge, while email/Slack/Zoom/Luma remain in use. Every state transition must respect Hub law, server-side authorization and receipts; avoid a separate truth database.

Pass: fresh anonymous browser sees actual society data and no private projections; operator ports remain inaccessible from public origin; chapter officers complete one event cycle without fleet operating it and provide a verdict. Not pass: static preview #992 or admin UI masquerading as a member-facing site.

Integration with Hestia #1567/first-user app remains optional for public browsing.

Activity

  1. dp-web4 commented on Nov 13, 2026

    @dp-web4
    OwnerAuthor

    NOVA execution handoff, 2026-11-12 — after public preview #992. The public-site branch now carries a dedicated hub public-site truthfulness CI job (commit 95c1d670); merging that preview does not make it a live Hub site. I recommend a deliberately bounded first implementation slice: (1) server-side public-only projection for site name, purpose, governing charter/disclosure and service state; (2) separate public HTTP router/listener and deployment config, no operator route/token imports, no browser access to loopback admin API; (3) fail-visible unavailable/locked/maintenance with no empty-list-as-healthy; (4) no member profiles, join/admission, DMs or unverified outcome claims. Acceptance tests must request all /admin/* paths and privileged API names from the public origin and receive no handler/secret, prove member-only/self-only fields absent from HTML/JSON/cache/error/log channels, and demonstrate tampered browser-supplied law/identity cannot change public projection. Add HTTPS reverse-proxy CSP/privacy/keyboard/mobile checks before a real chapter deployment. The chapter officer owner/backup and inbox workflow is the NEXT slice, gated on real consent/auth and observed task completion. This is a scope/test handoff, not permission to publish an Internet endpoint.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions