openhaven/openhaven.net
1
0
Fork 0
Code Issues Pull requests 8 Projects Releases Packages Wiki Activity Actions 121

docs: affordance definitions draft for team review [OPE-41] #6

Open
brandon wants to merge 1 commit from OPE-41-9-5-affordance-defs into main
pull from: OPE-41-9-5-affordance-defs
merge into: openhaven:main
Conversation 0 Commits 1 Files changed 1 +545
brandon commented 2026-06-26 23:16:06 +00:00
Collaborator
Copy link

AI-drafted definitions for all 43 affordances per Story 9.5 AC.

Each definition covers:

  • What it enables � plain language, aimed at a community organizer with no technical background
  • Why it matters � the governance/community-power argument for this capability
  • Protocols providing this � example entries from the matrix

How to review

This PR is the review vehicle per the Story 9.5 multilateral process:

  • Edit definitions inline (direct commits or suggestions on this PR)
  • Answer the four review prompts in the doc (rename/merge/split candidates, missing affordances, domain coverage gaps)
  • Propose new affordances at the bottom

Once approved and merged, the definitions flow to the description field in affordances.json. The draft file in _bmad-output/ serves as the record of the review.

Next step after merge

Extract approved definitions into src/data/affordances.json and tighten AffordanceSchema.description from optional ? required (coordinated with Story 8.3).

AI-drafted definitions for all 43 affordances per Story 9.5 AC. Each definition covers: - **What it enables** � plain language, aimed at a community organizer with no technical background - **Why it matters** � the governance/community-power argument for this capability - **Protocols providing this** � example entries from the matrix ## How to review This PR is the review vehicle per the Story 9.5 multilateral process: - Edit definitions inline (direct commits or suggestions on this PR) - Answer the four review prompts in the doc (rename/merge/split candidates, missing affordances, domain coverage gaps) - Propose new affordances at the bottom Once approved and merged, the definitions flow to the `description` field in `affordances.json`. The draft file in `_bmad-output/` serves as the record of the review. ## Next step after merge Extract approved definitions into `src/data/affordances.json` and tighten `AffordanceSchema.description` from optional ? required (coordinated with Story 8.3).
brandon self-assigned this 2026-06-26 23:16:06 +00:00 
AI-drafted definitions for all 43 affordances per Story 9.5 AC —
one definition per affordance covering what it enables, why it matters,
and example protocols. Includes review prompts for rename/merge/split
candidates and missing affordance proposals.

Per AC: this PR is the review vehicle. Approved definitions flow to
affordances.json description fields; new affordances added during the
same review window.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin OPE-41-9-5-affordance-defs:OPE-41-9-5-affordance-defs
git switch OPE-41-9-5-affordance-defs

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff OPE-41-9-5-affordance-defs
git switch OPE-41-9-5-affordance-defs
git rebase main
git switch main
git merge --ff-only OPE-41-9-5-affordance-defs
git switch OPE-41-9-5-affordance-defs
git rebase main
git switch main
git merge --no-ff OPE-41-9-5-affordance-defs
git switch main
git merge --squash OPE-41-9-5-affordance-defs
git switch main
git merge --ff-only OPE-41-9-5-affordance-defs
git switch main
git merge OPE-41-9-5-affordance-defs
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
brandon
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
openhaven/openhaven.net!6
No description provided.