Build together
Build with the Starlight Intelligence community
Contribute to open agent systems, share reproducible work and build your own business around a portable intelligence foundation.
A shared foundation. Room for your own company.
Bring an idea that matters to you: a better research workflow, a useful creator tool, a reliable agent adapter or a system for a community you understand. Starlight's direction is to make the shared intelligence layer stronger while letting builders own the businesses they create above it.
Today, participation starts in the public repositories. The contributor programme, showcases and commercial collaboration model below are proposals. There is no membership fee, pooled payout scheme or certification programme launched on this page.
Make something together this week.
Choose a small goal, record what you make, and carry the lessons into your next attempt. Plan privately, then decide what to share.
Prepare a creation week ↗Ways to begin today
Bring a useful lesson
Write a case, inspect its sources and permissions, and export it for someone to review. Carry the Commons covenant into Memory Studio when you choose to adopt it.
Open Starlight CommonsContribute a repair
Bring a reproducible issue and a narrow fix to the foundation. A maintainer can review concrete evidence.
Explore the foundation issuesBuild an application
Inspect the released source, choose one useful task and record the result, permissions and recovery path in your own project.
Choose your foundationShare a reproducible example
Document the exact source revision, prerequisites, steps, failures and output. Bring the example to the relevant repository.
Read the architecture notePropose a joint build
Name the users, the job and the contribution each party owns. Scope, support and any commercial terms are agreed separately.
Contact FrankThe contributor model we want to build
Useful contributions earn visibility through inspectable work. A proposed showcase would link to a builder's own project, identify the maintained source and explain which result was reproduced. Maintaining an adapter, teaching a workflow and running a service are different responsibilities; each should have a named owner.
Start with a small founding builder group that can reproduce one workflow each. Publish the contribution path and maintainer responsibilities before expanding the catalogue. People should be able to challenge a result, repair a defect and leave with their work.
How independent businesses can earn
A builder can sell an application, scoped deployment, integration, private operation or accountable maintenance around appropriately licensed source. The customer should understand what the builder supplies, what remains open and which operating obligations the price covers.
Starlight's product direction is portable capabilities that customers run with their own accounts, data and tools. Any maintained package, referral or shared delivery arrangement needs a defined scope, evidence and explicit terms. Participation does not automatically create an endorsement or a claim on anyone's revenue.
Read the business design note for an example of how to turn one useful open workflow into a repeatable service.
From a name to a body of work
The name gains meaning when a builder says: “I used this, I checked it, and here is what it helped me make.” Software, examples, critical feedback and independently run businesses can give Starlight that meaning. The invitation is open: bring work worth building on.
