GitHub is the front door.

Project repository on GitHub

Who we want to hear from

People who engineer buildings: integrators, controls technicians, programmers, commissioning engineers, operators. If you have ever built the same VAV graphic twice, your opinion on what the model should know is worth more than a pull request. Open a discussion. Tell us which of your files Archipelago should be able to read, and what it must never guess.

Developers are welcome too, and the architecture pages are written for you. But the project's direction is set by the work it removes, not by the stack.

How contributions work

• Contributions are accepted under the project's licenses with a Developer Certificate of Origin sign-off on each commit. No contributor license agreement.
• Every change is reviewed. The core and the importers get the strictest review because they touch customer files.
• No customer engineering data in any contribution, ever: no station backups, controller files, drawings, point lists or screenshots from real sites. Synthetic fixtures only, in the fixtures folder. A CI check refuses the rest.
• No vendor proprietary material: no SDK jars, no vendor documentation extracts, no pasted vendor source. If a contribution needs vendor knowledge, it cites a public interface.
• Contributor guidelines ask that vendor software and documentation are never fed into AI tools while working on the project.

Code of conduct

The project adopts the Contributor Covenant. Be direct, be kind, assume competence. Reports go privately to the maintainer through GitHub; a dedicated reporting channel is listed in the repository's code of conduct as the project grows.

Governance

Archipelago was founded by ThirtyK, which maintains it today and names the maintainers. It is a separate project from ThirtyK's own products, with its own code, written from scratch on synthetic fixtures. The governance document in the repository describes the current single-maintainer model, how additional maintainers are added, and the path to a maintainer council as the project grows. ThirtyK keeps the trademark; the code carries open licenses. The project is independent of every manufacturer and accepts no vendor endorsement.

Licensing

Everything in the repository is under the GNU Affero General Public License v3. Use it for anything, including commercial work. If you build a product on it, or run a modified version as a service for others, your version is open under the same license and its source is available. Contributions are accepted under the same license with a Developer Certificate of Origin sign-off; there is no contributor license agreement. The repository's LICENSE file is the authority.

Documents in the repository

• README
• LICENSE and a per-package license table
• CONTRIBUTING
• CODE_OF_CONDUCT
• SECURITY (disclosure and incident runbook)
• GOVERNANCE (maintainer policy)
• ROADMAP
• Dependency and release policy
• Architecture decision records
• Issue and pull request templates

Status: the organization, the repository layout and these documents are being set up as the project's foundation phase. The repository linked above is the current public home and will redirect if it moves.