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

docs: capture risk methodology v0.3 (8 ? 5 dimensions) [OPE-16] #5

Open
brandon wants to merge 1 commit from OPE-16-capture-risk-methodology-v0.3 into main
pull from: OPE-16-capture-risk-methodology-v0.3
merge into: openhaven:main
Conversation 0 Commits 1 Files changed 1 +35 -74
brandon commented 2026-06-26 20:55:57 +00:00
Collaborator
Copy link

Ports the v0.3 methodology from the parallel repo where it was authored.

Collapses the original 8 evaluation dimensions to 5:

  • Governance + Legal Control merged into one dimension
  • Funding Concentration + Key-person/Key-org Dependency merged into one dimension
  • Implementation Diversity dropped (nearly universal high-score; redundant signal that correlates with funding, forking viability, and key-org dependency)

Also adds the inline reference-tag convention for the Capture Risk Assessment field ([a], [d][n] etc. pointing to the row's References field).

This doc governs how captureRiskReasoning entries are authored in the data � it is the methodology input Zach is tracking on OPE-16. Unblocks that story from a methodology standpoint; the data-authoring pass (populating the field across protocols.json) is the remaining downstream work.

Ports the v0.3 methodology from the parallel repo where it was authored. Collapses the original 8 evaluation dimensions to 5: - Governance + Legal Control merged into one dimension - Funding Concentration + Key-person/Key-org Dependency merged into one dimension - Implementation Diversity dropped (nearly universal high-score; redundant signal that correlates with funding, forking viability, and key-org dependency) Also adds the inline reference-tag convention for the Capture Risk Assessment field (`[a]`, `[d][n]` etc. pointing to the row's References field). This doc governs how `captureRiskReasoning` entries are authored in the data � it is the methodology input Zach is tracking on OPE-16. Unblocks that story from a methodology standpoint; the data-authoring pass (populating the field across protocols.json) is the remaining downstream work.
brandon self-assigned this 2026-06-26 20:55:57 +00:00 
Simplifies evaluation from 8 dimensions to 5 by merging Governance +
Legal Control into one, merging Funding Concentration + Key-person Dependency
into one, and dropping Implementation Diversity (redundant signal). Updates
overall-average wording to reflect five dimensions. Adds inline reference-tag
convention for the Capture Risk Assessment field. This is the methodology that
informs captureRiskReasoning data entries (Story 8.3 input).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
brandon reviewed 2026-07-21 06:05:23 +00:00
brandon left a comment
Author
Collaborator
Copy link

Reviewed

Reviewed
This pull request has changes conflicting with the target branch.
  • docs/capture-risk-methodology.md
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin OPE-16-capture-risk-methodology-v0.3:OPE-16-capture-risk-methodology-v0.3
git switch OPE-16-capture-risk-methodology-v0.3

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-16-capture-risk-methodology-v0.3
git switch OPE-16-capture-risk-methodology-v0.3
git rebase main
git switch main
git merge --ff-only OPE-16-capture-risk-methodology-v0.3
git switch OPE-16-capture-risk-methodology-v0.3
git rebase main
git switch main
git merge --no-ff OPE-16-capture-risk-methodology-v0.3
git switch main
git merge --squash OPE-16-capture-risk-methodology-v0.3
git switch main
git merge --ff-only OPE-16-capture-risk-methodology-v0.3
git switch main
git merge OPE-16-capture-risk-methodology-v0.3
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!5
No description provided.