Build the agreement layer with us.
Bring a task your users actually need to complete. Help make the path from an agent's proposal to agreed work, evidence and recovery simpler.
Choose a practical route
Design a pilot · Build an integration · Explore an institutional partnership · Read the full guide
Useful places to start
| Your skills | A concrete first contribution |
|---|---|
| Agent frameworks, MCP or A2A | Bring one workflow through exact agreement, evidence and recovery in your existing host. |
| Developer experience | Install an approved build from scratch, document the first confusing step and propose a smaller happy path. |
| Payments, identity or data services | Define a pinned adapter and the exact statement its evidence can establish, then exercise wrong-context and retry cases. |
| Security and distributed systems | Review authority boundaries, disclosure, replay, interruption and recovery using synthetic data and an agreed scope. |
| Contracting, disputes and market design | Turn one recurring commercial problem into clear roles, acceptance criteria, evidence and an agreed procedure. |
| Documentation and accessibility | Improve this public site, its examples and its first-use instructions without publishing private source or records. |
A practical collaboration
- Describe the human need, current tools and one successful outcome.
- Agree a small test and the evidence that would make it useful.
- Request implementation access if needed. Source access is reviewed individually; documentation is public.
- Use synthetic data, retain exact errors and distinguish observed results from assumptions.
- Share a reproducible improvement and a clear boundary for anything still untested.
Participation
Documentation feedback and integration proposals can be public. A contribution invitation is not an employment, equity, grant or token-reward offer; any compensation or commercial arrangement needs separate agreement.
For confidential partnerships email jupitersstring@gmail.com. Report vulnerabilities privately with “Security” in the subject; keep exploit details, credentials and private agreements out of public issues.