• 

  Decision change. Work should catch up.

Inspiration

Draft: Teams can keep implementing tickets after the decisions behind them change. DecisionFuse aims to make that drift visible before more effort is spent. Replace with a real firsthand example only if the builder can substantiate it.

What it does

Planned: connects accepted Confluence decisions to Jira acceptance criteria, explains version-specific conflicts and obsolete scope, and presents exact owner-approved corrections. No automatic ticket deletion or closure.

How we built it

To complete after implementation: Forge modules, actual Jira/Confluence contracts, persistence, version checks, analysis engine, UI and verified optional agent/MCP integrations. Do not claim all planned tools were used.

Challenges we ran into

To complete from evidence: permissions across products, evidence grounding, source/issue concurrency and reliable remote-write recovery.

Accomplishments that we're proud of

To complete with real test counts and working demo links. No fabricated precision, time savings or users.

What we learned

To complete from build records. Working hypothesis: requirement drift needs versioned review and explicit approval, not just another summary.

What's next for DecisionFuse

Consented pilot, relevance/false-alarm measurement, richer links and optional verified Teamwork Graph integration. Separate future scope from delivered behavior.

Built With

• atlassian-forge
• confluence
• elevenlabs
• jira
• model-context-protocol
• playwright
• react
• rovo
• svg
• typescript
• videowright
• vitest
• zod