Dev Workflow

Every contribution path runs through this portal first, then into the repo that actually owns the change. Here's the loop:

1. Discuss

Got an idea, a question, or aren't sure where something belongs? Start in Discussions — it's the lowest-friction place to float something before it's a formal ask.

2. Find the right repo

Fate's Edge is split across five repos by concern. The wiki's Repo Map is the quick lookup; Architecture explains the layering behind the split.

3. Open an issue

Each repo has issue templates tuned to what actually lives there — a bug report for the AI GM reads differently than one for the web client or a rules erratum. Use the template; it's there so maintainers don't have to ask the same three clarifying questions every time.

4. Open a PR

Reference the issue. Keep it small and focused where you can — see Ways to Contribute for the areas most in need of hands, and each repo's PR template for what's expected (tests for the rules engine, transport layer, and Tag DSL; docs updates for anything contributor-facing).

5. It lands somewhere durable

Stable, versioned reference (architecture, contribution guide, Art Bible orientation, roadmap) lives on this portal. Living working notes — deep-dives, in-progress references, FAQs that change often — live on the wiki, editable without a PR review. Announcements and dev logs go to the blog.