GitHub repository
Source code, README, crates, tools, and the implementation history.
Open resourceResources
Everything you need to inspect and understand the project.
OpenSymphony has a strong repo-first posture. Start with the source, then move through the docs, DeepWiki, template repo, and companion material depending on how deep you want to go.
README
The fastest path to installation, architecture orientation, and the command surface.
Open resourceDocumentation directory
Architecture, deployment modes, testing, workspace lifecycle, and runtime integration notes.
Open resourceDeepWiki
Indexed subsystem pages and code-oriented walkthroughs of the repository.
Open resourceOpenSymphony template
A greenfield starting point with workflow files, project skills, and AI PR review automation.
Open resourceWork Orchestration course
The broader category framing for orchestration as a work system around the agent.
Open resourceLaunch video
Short release companion for the project.
Open resourceSuggested path
A route through the material.
A focused reading path is enough to understand the project.
01
Read the README first
That gives you the problem statement, architecture summary, and install surface in one place.
02
Use docs for operational depth
The docs directory is where the crate boundaries, deployment modes, and runtime choices are spelled out.
03
Use DeepWiki for deeper architectural analysis
It is best when you want indexed subsystem pages, code-oriented walkthroughs, and a stronger development and analysis view of the repository.
04
Use the template when you want to adopt the workflow
The template repo matters when you want the repo-owned contract, skills, and review automation in a new project.