Skip to content

Contributing

CORE is an open project. Contributions are welcome — but CORE has a higher bar than most projects.

Read CONTRIBUTING.md in the repository root before anything else.

The short version: if you have not read .specs/ and .intent/, you are not ready to contribute. The architectural papers explain why the constitution is what it is. The constitution is the starting point, not an afterthought.

What Good Collaboration Looks Like

CORE is looking for people who:

  • Think in systems and constraints, not features
  • Get uncomfortable with "it mostly works" as a standard
  • Can read .intent/ and reason accurately about what it means
  • Are willing to engage with the architecture before proposing changes

You do not need to be a programmer. Clear thinkers who can reason about governance, traceability, and constitutional correctness are as valuable as code contributors.

How to Engage

GitHub — open an issue or discussion before writing code. Intent clarification is always preferred over corrective cleanup.

Dev.to — Dariusz publishes technical threads documenting CORE's development and architectural thinking. Follow @DNewecki for context on where the project is heading.

X — @DNewecki

Areas Where Help Is Genuinely Useful

  • Documentation — keeping docs accurate and current as the architecture evolves. Start with .specs/ — papers, requirements, and ADRs are a natural contribution surface.
  • Governance reasoning — stress-testing constitutional decisions and finding gaps
  • Regulated industry context — particularly GxP, Annex 11, and validated-state environments
  • A3 operational hardening — CORE is currently at A3 (Governed Autonomy). The daemon runs continuously. Contributions that improve the autonomous loop, convergence signal, or governor experience are directly useful.
  • Ideation — the path from A3 to A4 (self-replication) is genuinely open. Architectural thinking welcome.

CORE is governed by intent. Contributions that respect that are welcome.