Skip to content

hub PRD: the adoption gap sets priority; real-community scenario (AIC Portland chapter) - #991

Merged
dp-web4 merged 1 commit into
mainfrom
claude/prd-human-layer-aic
Nov 11, 2026
Merged

dp-web4 merged 1 commit into
mainfrom
claude/prd-human-layer-aic

Conversation

@dp-web4

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

Copy link
Copy Markdown
Owner

Follow-up to #990, at dp's direction (2026-11-11). Companion commit on hestia#1561.

The gap, in dp's words. Every audience says "show me what I can use and I'll tell you if it's useful." Nobody wants to co-develop or spend time building a solution out of the tools. Today Hestia gates agents for CLI harnesses only, with an unintuitive setup, and Hub connects those agents across Hestia machines. That is hobbyist use: not mature enough for corporate, not easy enough for consumer. The human layer (social channels, member discovery, committees and workgroups, events) is planned with mostly-ready primitives, and none of it is built.

What this changes in hub/docs/PRD_MEMBER_WEBSITE_FIRST_USER_2026-11-11.md:

  • §2a. The gap sets priority. The synthetic community (§5) becomes the rehearsal and privacy test. A real group's use and verdict becomes the pass gate.
  • W11, coexistence. Email, Slack, Zoom and Luma keep working, and Hub adds ownership, record and discovery on top. The README currently says "Not Slack-integrated (deferred until pilot…)". This makes coexistence a requirement instead.
  • W12, workgroups, offices and events.
  • §5b, the AI Collective Portland chapter. The requirements come from the chapter itself: six interest committees, 1:1 intake, a bi-weekly all-group meeting, and the 10-27 pain points (missed inbound mail, single-owner events, no nudges). The first deliverable is inbound triage with owner, backup and nudges, event ownership, a who-owns-what page, and the record presented as minutes.
    • Pass: one event cycle run by the chapter's own officers, with no fleet or dp operating it, and their verdict recorded verbatim.
    • Not a pass: a demo, a pilot we operate for them, or a requirement that they leave Slack.
  • Slice F0b goes first. Officer and co-lead personas are added.

Docs only; no code or protocol change.

🤖 Generated with Claude Code

…IC chapter)

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 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 exact-head review: GO for docs-only adoption-oriented PRD expansion. It puts real-community use and the chapter officers' independent verdict ahead of prototype elegance; provides a bounded first deliverable of assigned inbound mail, owner+backup, nudges, event ownership, and record/minutes; preserves coexistence with existing Slack/email/Zoom/Luma workflows rather than requiring migration; synthetic community remains a privacy rehearsal, not a successful field pilot. Crucially this is a proposal and no chapter agreement, functioning integration, or deployment is claimed. Companion Hestia #1561 defines the personal app slice. Green Web4 CI. Ready to merge.

@dp-web4
dp-web4 merged commit 69a2337 into main Nov 11, 2026
4 checks passed

dp-web4 commented Nov 12, 2026

Copy link
Copy Markdown
Owner Author

Closing the adoption gap with code: #992 adds the runnable public visitor shell; #993 tracks public projection integration and community ownership/event utility. In parallel Hestia #1567/#1568 handle a visible first-run governance journey. The pass remains an outside group accomplishing real work without constructing a workflow, not a fleet-operated demo.

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