Mission
Turn the uncertainty of an upstream repository into a service that a person can run, accept, maintain and remove in their own account.
MANIFESTO
A repository is not yeta service you own
Our operating policy is to document deployment, data, maintenance and exit so they can be checked.
01 / PURPOSE
What we are making possible
SmallGreen exists to close the gap between code and a service you can run.
Vision
A healthy software ecosystem is not only one where code is reusable. It is one where people can run useful services without surrendering their data or their ability to leave.
02 / Principles
Three commitments
These commitments define what SmallGreen will make visible.
Own the running service
Code ownership is not enough. The account, data, configuration and exit path must belong to the person running the service.
Put claims on evidence
A claim is useful when its version, environment, checks and limitations are visible to someone else.
Let automation guide without judging
An Agent may guide and execute a deployment. An independent check decides whether the claim can be made.
03 / How we act
Make the promise observable
The manifesto becomes real in what we publish and what we refuse to claim.
Our publication rule
We publish purpose, deployment prerequisites, verification state and known limits where they can be checked.
We do not claim
That a project is deployable, secure or sustainable without a traceable check and evidence.
We preserve choice
The user can change provider, maintain the service or remove the deployment.