Title here
Summary here
Contributing
Reporting Issues
Found a bug or have a feature request? Open an issue on the relevant GitHub repository:
- Unbound Force Website — this website
- Gaze — test quality analysis tool
- Dewey — semantic knowledge retrieval
- Replicator — multi-agent coordination
- Unbound Force — agent personas and roles
Include steps to reproduce, expected behavior, and actual behavior. For feature requests, describe the problem you are trying to solve.
Submitting Pull Requests
We follow the standard GitHub pull request workflow:
- Fork the repository
- Create a feature branch named with a number prefix (e.g.,
003-feature-name) - Make your changes
- Submit a pull request against the
mainbranch - Address any review feedback from The Divisor council
All pull requests are reviewed by The Divisor — a council of nine sub-personas. Six review personas (The Guard, The Architect, The Adversary, The Operator (SRE), The Tester, and The Curator) evaluate intent, structure, resilience, operational readiness, and test quality. Three content personas (The Scribe, The Herald, and The Envoy) ensure documentation, blog posts, and public communications meet quality standards. Collective approval from all active personas is required before merge.
Conventional Commits
All commit messages must follow the Conventional Commits format:
type: descriptionValid types:
| Type | Purpose | Example |
|---|---|---|
feat: | New feature | feat: add Gaze project page |
fix: | Bug fix | fix: correct broken link in team navigation |
docs: | Documentation | docs: update getting started guide |
chore: | Maintenance | chore: update dependencies |
style: | Formatting | style: fix indentation in config file |
refactor: | Code restructuring | refactor: simplify homepage template logic |
ci: | CI/CD changes | ci: add build verification step |
The Speckit Workflow
All non-trivial feature work goes through the Speckit pipeline. This ensures structured planning before implementation:
constitution -> specify -> clarify -> plan -> tasks -> analyze -> checklist -> implementEach stage builds on the previous one:
- Constitution — project-level governance and principles
- Specify — turn a feature description into a structured specification
- Clarify — reduce ambiguity before planning
- Plan — generate the technical implementation plan
- Tasks — create actionable, dependency-ordered task list
- Analyze — cross-artifact consistency check
- Checklist — requirement quality validation
- Implement — execute the plan task by task
The constitution (.specify/memory/constitution.md) is the highest-authority document in any Unbound Force project. All work must align with it.