Community

Community

IntentFlow's community space is for practical architecture discussion: how to model workflows, where existing patterns become unclear, how AI agents should be constrained, and what real adoption reveals.

Channels

Channel	Use For
Discussions	Questions, ideas, adoption stories, roadmap feedback, and examples.
Issues	Reproducible bugs, concrete feature requests, documentation gaps, and AI generation feedback.
Security	Private vulnerability reporting.
Wiki	Product guide, architecture model, AI playbook, migration guidance, and operational readiness.

Discussion Categories

Category	Use It For
Announcements	Maintainer updates, release notes, and project direction.
Q&A	Adoption questions and workflow modeling help.
Ideas	Architecture, generator, examples, and roadmap proposals.
Show and tell	Real adoption stories, experiments, and example features.
General	Broader discussion that does not fit another category.
Polls	Structured tradeoff votes when a decision needs input.

Before Asking A Question

Read:

• Start Here
• Core Concepts
• Core vs AI
• Migration Playbook
• AI Agent Playbook

Then include:

• current pattern
• feature state list
• user intents
• external events
• side effects
• routes
• outputs
• what is hard to test or reason about

Discussion To Issue Flow

Discussions are for shaping understanding.

Issues are for work that is ready to track.

Move from Discussion to Issue when:

• the expected behavior is clear
• the affected runtime, generator, docs, or example area is known
• a reproduction or concrete example exists
• the change can be reviewed and tested

Good Community Feedback

The most useful feedback is concrete:

• a feature that became easier to model
• a feature that did not fit the pattern cleanly
• a ViewModel or coordinator migration that exposed tradeoffs
• an AI agent output that drifted from the manifest
• a docs page that left a question unanswered

Conduct

Keep discussions technical, respectful, and evidence-based. See the repository Code of Conduct.