ORBI+ / DEVELOPERS
Build on ORBINTU. Build with ORBINTU.
Build on ORBINTU: integrate with the platform when there is a public surface to integrate with. Build with ORBINTU: help build the platform itself.
02 / BUILD ON ORBINTU
Integrate with ORBINTU.
NO PUBLIC API OR SDK YET
- PUBLIC API
- Not yet. When ORBINTU opens an integration surface, it will be documented here with its authentication model, permissions, rate limits and request/response contracts.
- WHAT IT WILL COVER
- Bringing a capability to the work, and letting a person connect a system they already use — under permissions they grant and can withdraw.
- WHAT IT WILL NOT COVER
- ORBINTU’s own intelligence. That stays ORBINTU’s.
We would rather publish an integration surface once it is real than describe one that is not.
03 / BUILD WITH ORBINTU
You don’t need a job title to understand a problem.
If there is real, bounded work and you have the capability to solve it, there should be a path to contribute.
REMOTE BY DEFAULT
Contribution is organized around the work, the capability and the result, not a location.
EVIDENCE OVER CLAIMS
What was built and whether it worked matters more than a title.
SMALL AND REAL
Bounded problems with a clear definition of done.
04 / WHERE THE WORK IS
The hard parts.
Open contribution work NONE OPEN YET — until then, tell us what you build.
05 / INTRODUCE YOURSELF
Tell us what you build.
- WHAT CAN YOU BUILD?
- WHAT HAVE YOU BUILT?
- WHAT PART OF ORBINTU?
- Optional: GitHub, portfolio or a project.
DRAFT · COUNSEL REVIEW REQUIRED Participation does not by itself create an employment, contractor, partnership, agency or compensation relationship. Specific paid work, if offered, will have separate written terms. Contribution terms (licence, IP representations and a CLA or DCO) will be published before external code is accepted.