A layered Swift package ecosystem organized around shared conventions.
Swift Institute is a set of layered Swift packages organized as separate GitHub organizations, one per layer. The layers share dependency rules, naming conventions, error handling, memory ownership, and API shape — so that compile-time guarantees hold across the entire stack rather than stopping at package boundaries.
| Layer | Organization | Role |
|---|---|---|
| 1 | swift-primitives | Atomic building blocks — buffer, geometry, algebra, memory, kernel |
| 2 | swift-standards + per-authority orgs | Specification implementations |
| 3 | swift-foundations | Composed building blocks — IO, HTML, CSS, SVG, PDF, networking |
| 4 | Components | Opinionated assemblies — planned |
| 5 | Applications | End-user systems — planned |
Release in progress. The organization links above are being made world-readable over the coming weeks. Some may currently 404; they resolve as each layer's release lands.
Layer 2 is an organization of organizations. Each standards authority has its own GitHub organization hosting the packages it governs: swift-ietf (RFCs), swift-iso, swift-w3c, swift-whatwg, plus single-package organizations for IEEE, IEC, ECMA, INCITS, ARM, Intel, RISC-V, and Microsoft.
| If you want to... | Go to |
|---|---|
| Read the website, architecture overview, or blog | swift-institute.org |
| Use atomic primitives (buffer, geometry, algebra, memory, kernel) | swift-primitives |
| Consume an RFC or ISO specification | swift-ietf, swift-iso, or the relevant per-authority org |
| Use composed building blocks (IO, HTML, CSS, SVG, PDF) | swift-foundations |
| Browse design rationale | swift-institute/Research |
| Browse the empirical receipts behind technical claims | swift-institute/Experiments |
| Report an issue or contribute | Open an issue or pull request on the relevant repository |
| Report a security vulnerability | See the security policy |
Initial public alpha. The website (swift-institute.org) and companion repositories (Research, Experiments) are public. The package layers they describe are being released repository by repository over the coming weeks.
Maintained by Coen ten Thije Boonkkamp — contributions welcome via pull request.
All packages use the Apache License 2.0.