Skip to content

why: add outcome-oriented workflows and impact reporting - #43

Merged
dantheuber merged 3 commits into
mainfrom
feature/deep-workflows-impact
Aug 19, 2026
Merged

dantheuber merged 3 commits into
mainfrom
feature/deep-workflows-impact

Conversation

@dantheuber

Copy link
Copy Markdown
Member

Summary

  • Add bootstrap, maintain, review, and impact workflow interfaces.
  • Add decision-impact summaries to the PR gate and GitHub job summary.
  • Update OKF v0.2 compatibility, relative links, workflow documentation, and review metadata.
  • Add workflow, impact, initialization, and review coverage.

Testing

  • npm test
  • npm run why -- lint
  • npm run why -- impact "origin/main...HEAD"
  • Verify the PR gate emits the decision-impact summary.

- Add bootstrap, maintain, review, and impact interfaces
- Document OKF v0.2 compatibility and workflow operations
- Surface decision impact in the PR gate
- Adjust DESIGN.md line anchor to reflect the current document layout
…s-impact

# Conflicts:
#	.why/decisions/ui-data-contract.md
@dantheuber
dantheuber merged commit eab8a44 into main Aug 19, 2026
2 checks passed
@dantheuber
dantheuber deleted the feature/deep-workflows-impact branch August 19, 2026 05:58
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