A layered Swift package ecosystem organized around shared conventions.
The public contributor front door is swift-institute/Workspace: clone it for the package inventory, setup instructions, synchronization tooling, and checkout diagnostics.
Rules sit at the heart of every system we build on. When rules are expressed clearly and consistently, everything built on top of them becomes simpler, safer, and more predictable. We believe rules deserve a form that can be validated rather than interpreted — and Swift's type system makes that possible.
Swift Institute applies that idea to infrastructure itself: specifications become types, conventions become compiler guarantees, and the same discipline runs from the smallest buffer primitive to a complete PDF renderer.
The realised ecosystem spans GitHub organizations for three package layers. Layers are intended to depend downward only, and packages are converging on shared dependency, naming, typed-error, memory-ownership, and API-shape conventions. Components and Applications remain planned layers, not evidence of a populated package tier.
| Layer | Organization | Role |
|---|---|---|
| 1 | swift-primitives | Atomic building blocks — buffer, memory, geometry, time, async |
| 2 | swift-standards + per-authority orgs | Specification implementations — RFC, ISO, W3C, WHATWG |
| 3 | swift-foundations | Composed systems — I/O, filesystem, HTML, CSS, PDF, networking |
| 4 | Components — planned | Opinionated assemblies |
| 5 | Applications — planned | End-user systems |
Layer 2 is an organization of organizations: each standards authority has its own GitHub organization — swift-ietf (RFCs), swift-iso, swift-w3c, swift-whatwg, plus single-package organizations for IEEE, IEC, ECMA, INCITS, ARM, Intel, RISC-V (pending), and Microsoft.
| If you want to... | Go to |
|---|---|
| Set up the ecosystem or inspect its public package inventory | Workspace |
| Read the website, architecture overview, or blog | swift-institute.org |
| Use atomic primitives | swift-primitives |
| Consume an RFC, ISO, W3C, or WHATWG specification | swift-standards |
| Use composed systems (I/O, filesystem, HTML, CSS, PDF) | swift-foundations |
| Browse design rationale | Research |
| Browse the experiments behind technical claims | Experiments |
| Call the reusable CI workflows | .github/workflows — pin an immutable SHA; not formally supported outside the ecosystem |
| Report a security vulnerability | Security policy |
| Report an issue or contribute | Open an issue or pull request on the relevant repository |
Public alpha. The realised layer organizations are public and packages continue to land repository by repository; APIs may change until first tagged releases.
Swift Institute is an independent open-source project, not affiliated with Apple or the Swift open-source project.
Maintained by Coen ten Thije Boonkkamp — contributions welcome via pull request.
Policy requires Apache License 2.0 for packages in the three realised layers. The public fleet is
being reconciled against that policy; until that work is complete, each repository's LICENSE
file is the authority for that repository.