The loop we are building
This is the first working loop on the roadmap. None of it runs yet. It is what the code will do, and what you will be able to check it against.
-
1
Ticket
You describe a change in a ticket, in the tracker you already use.
-
2
Change
An agent reads the ticket and the code, and writes the change in a sandbox.
-
3
Tests
The agent runs your test suite against the change.
-
4
Pull request
The agent opens a pull request that says what it changed and why.
-
5
Your review
A person reviews it. By default, nothing is merged without that approval.
Sovereignty
Where does it run?
Who holds the keys?
Under which law?
For every installation of Opificia, you should be able to answer these three questions yourself. The eight commitments below are how we intend to keep it that way. Each one comes with a test, so you can check it.
Proposed All eight stay proposed until the maintainers accept them as architecture decision records.
-
Runs anywhere you choose
Fully self-hostable, including on air-gapped networks. No feature needs a service hosted by us or by anyone else.
Test Every feature works with no outbound internet access.
-
No phone-home
Telemetry is off by default. If you turn it on, it goes only to an endpoint you configure.
Test A default installation connects only to endpoints you configured.
-
Model-agnostic
Any model behind an open, documented interface. Open-weight models, whose weights are published and can run anywhere, are first-class.
Test The reference tests pass with an open-weight model running locally.
-
Open standards
Open protocols and formats first. Proprietary integrations can exist as plugins, never as requirements.
Test Every external interface in the core follows a published specification.
-
Your data stays yours
Code, prompts, logs and traces stay where you configure them. The project does not train models on them.
Test Nothing is written or sent outside the destinations in your configuration.
-
Humans decide
By default, nothing is merged or deployed without a person approving it. You can change that, but only explicitly.
Test No agent can merge or deploy without a recorded human approval.
-
Transparent supply chain
For the first release, we aim to publish SBOMs, sign releases and make builds reproducible.
Test An independent rebuild produces the same artefacts.
-
A European reference deployment
The project's own reference deployment runs on providers headquartered in Europe. It sets no limit on where you run Opificia.
Test The providers are listed publicly, with their country.
Licensing in plain words
You may use, study, change and share Opificia. If you modify the core and offer it to other people over a network, you share your changes under the same licence. Plugins built on the SDK carry no such obligation.
| The core | AGPL-3.0-only |
|---|---|
| SDK, plugins and examples | Apache-2.0 |
| Documentation | CC-BY-4.0 |
| Name and logo | Trademark, not open source |
Roadmap
Four phases to a first release. No dates yet: we will add them when we can keep them.
-
Phase 0
Foundations In progress
Licences, governance, security policy and the sovereignty commitments.
-
Phase 1
A first working loop
One agent, one ticket, one pull request, fully self-hosted with an open-weight model.
-
Phase 2
Hardening
Sandbox isolation, credential handling, audit logs and a test for each commitment.
-
Phase 3
First release
Signed, documented and installable, with an SBOM and a European reference deployment.
Every factory needs a twelfth tooth.
There is no product code yet, which makes this a good time to shape it. We need people to review the policies, write RFCs, discuss the design and translate the documentation.
Every commit is signed off under the Developer Certificate of Origin. You keep your copyright.