Guava Nexus Product Evolution Roadmap — From Provenance to Participation

Discover, Understand, and Create are so far acceptable. Evolve, Steward, and Anchor needs work. EVOLVE needs product work because the mechanics exist, but the experience of returning to a Seed, creating another version, adding evidence, and understanding lineage is not yet strong enough. STEWARD exists through the Producer Experience, but it still needs full end-to-end validation and likely refinement based on actual use. ANCHOR works mechanically, but the transition from authored version → canonical/public record needs to feel clearer and more intentional in the product. VERIFY is already implemented and is currently getting its visual fidelity correction. So the MVP work sequence should now be: 1. Finish VERIFY fidelity 2. Improve EVOLVE 3. Validate/refine STEWARD 4. Validate/refine ANCHOR 5. Run the entire journey end-to-end

MVP Stabilization 01 Preserve - Grow - existing Seed/Version model - lineage/provenance behavior that is already working - Source attribution where currently valid Fix / reconcile - mobile/tablet navigation defect - legacy Open App and legacy-route leakage - homepage/Start/Civic relationship - header/sidebar/footer inconsistencies - Seed creation/editor density - cognitive-continuity / save-state behavior Improve through PDS/design - Seed vs Version citation/reference UX - verification UX - current return/continuation experience where the walkthrough exposes friction Defer - Orchard Compass - knowledge graph redesign - six-stage semantic model - broad Reflect redesign - Figma archaeology