feat: Process Hub current-state + Layered Process View V1#95
Merged
Conversation
Three-band visual language (Outcome / Process Flow / Operations) layering Watson's Makigami-style levels around the existing river-styled SIPOC FRAME workspace. V1 wraps ProcessMapBase without changing the data model; later phases add Operations band content, Process Hub current-state, and multi-hub aggregation. Captures design alignment from a brainstorm session (incorporating Codex's review feedback on phasing and component placement). Plan handoff to V1 implementation work next. Co-Authored-By: ruflo <ruv@ruv.net>
Co-Authored-By: ruflo <ruv@ruv.net>
Co-Authored-By: ruflo <ruv@ruv.net>
…around Per code-quality review of Task 2: - Drop trailing space inside <dt> labels; brittle to formatter passes. - Switch outcome-band assertions to within().getByText() per element so Target:/value pairs are matched independently. - Rename target test to drop the unrelated "Cpk" framing — `target` is a generic spec value, not specifically Cpk.
Co-Authored-By: ruflo <ruv@ruv.net>
Co-Authored-By: ruflo <ruv@ruv.net>
Co-Authored-By: ruflo <ruv@ruv.net>
…-model Appended a 2026-04-27 update section to ADR-070 noting that ProcessMapBase is now wrapped by LayeredProcessView with Outcome/Process Flow/Operations bands. Added the matching paragraph to methodology.md after the Process Learning Levels table, a layered-band note to the FRAME section in mental-model-hierarchy.md, and a spec entry in llms.txt.
Fix meaningful-anchor, stacked-bands, and drop-(this-update) nits flagged in code review of commit 441bf6e. Co-Authored-By: ruflo <ruv@ruv.net>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Apr 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two related changes that share methodology vocabulary updates and ship together because they touch overlapping doc files (
methodology.md,llms.txt):Process Hub current state + product roadmap (commit
a58b60a7)@variscout/coremodules:processState.ts(318 LOC) +processHub.ts(37 LOC) — deterministic projections, no data-model rewriteProcessHubCurrentStatePanel.tsxrender surface in Azureprocess-learning-operating-model-design.md,product-method-roadmap-design.mdLayered Process View V1 (commits
aa5c9fe2..bdc6386a, 12 commits)<LayeredProcessView>in@variscout/ui— wraps existingProcessMapBaseriver-SIPOC in three bands (Outcome / Process Flow / Operations); props-only, no data-model changeFrameViewswap to the layered component (props pass through unchanged)docs/superpowers/plans/2026-04-27-layered-process-view-v1.mddocs/superpowers/specs/2026-04-27-layered-process-view-design.mdTest plan
pnpm --filter @variscout/ui build— cleanpnpm test— all packages green (PWA: +1 FrameView test, Azure: +1 FrameView test, UI: +9 LayeredProcessView tests, total ~5800+)pnpm build— full monorepobash scripts/pr-ready-check.sh— greenclaude --chromewalk on PWA (Showcase: Fill Weight): three bands render, factor chips show " at ", Outcome band shows Target/USL/LSLclaude --chromewalk on Azure (Coffee Moisture): three bands render, Operations placeholder when no factors mappedKnown follow-ups
setState-in-renderwarning in PWAAppMaintriggered byuseQuestions → setQuestions → useInvestigationStore.loadInvestigationStatecall chain. Confirmed bygit diff main HEADoveruseQuestions.ts+App.tsx+investigationStore.ts(zero diff) — preexisting on main, not introduced by this branch.Out of scope (deferred per the spec)
tributary→factorcode rename — separate PR before V3