Open source
Contribute to the open system, not a black box.
ContractSpec should stay legible, standards-first, and useful in real workflows. Contributions matter most when they sharpen that clarity instead of adding abstraction for its own sake.
Fastest path
- Read the contribution guide and pick a tractable scope.
- Open a draft PR early so maintainers can steer the work.
- Ship one clear improvement with tests or validation evidence.
Where contributions matter most
Work on the parts that make the system clearer and safer.
Contracts and runtime behavior
Improve the core system surfaces that keep APIs, UI, data, and tools aligned.
Examples and templates
Show how the open system behaves in realistic verticals and team workflows.
Docs and agent-facing guidance
Tighten the human and machine-readable guides that explain how the stack actually works.
Integrations and ecosystem
Expand the bridges that make the system usable in more real-world environments.
Quality bar
The contribution should make the repo easier to trust.
- Use strict TypeScript and keep changes explicit.
- Include tests or other concrete validation where behavior changes.
- Prefer one coherent concern per PR.
- Document the public or agent-facing impact when it exists.
Governance and security
Clarity first, private disclosure when the issue is sensitive.
Architecture and roadmap decisions stay founder-led for now, but the reasoning should stay inspectable in issues, PRs, and docs. If you find a security issue, do not open a public ticket. Use security@contractspec.io instead.