eos-platform 1.0: One Toolchain, Every EoS Profile
After eighteen months of incremental releases, the eos-platform meta-distribution reaches 1.0 with stable APIs, a unified package manifest, and a reproducible-build goal across the supported board set.
What is eos-platform?
eos-platform is the meta-distribution layer that sits above the EoS kernel. It bundles the kernel, HAL drivers, system services (eDB, eIPC, eLogger, eNet), and the eApps runtime into a single versioned manifest. Before 1.0, each component had its own release cadence, making reproducible builds difficult. Now, a single manifest.yml pins every component to a tested combination.
Stable API surface
The 1.0 release freezes the public C API for all 14 modules (HAL, Kernel, Multicore, Crypto, OTA, Sensors, Motor, Filesystem, Power, Networking, Debug, Drivers, Services, Logging). Any code written against the 1.0 API will compile without changes on any future 1.x release. Breaking changes require a 2.0 bump.
Unified package manifest
The new manifest.yml format specifies the board target, kernel profile (minimal, standard, full), enabled services, and pinned app versions. ebuild reads this manifest and produces a deterministic firmware image. The same manifest checked into git produces the same binary on any CI machine.
Reproducible builds
A reproducible-build claim must identify the manifest revision, build environment, target set, and binary-comparison results. Until those artifacts are published, reproducibility remains a release goal rather than an achieved property.
About these articles
How these articles are published
Every article on this site renders through this one page, from the Foundation's shared content registry. The title, date, badge, tags, and body all come from the same data the News page lists — which is why the two can never disagree about what an article says or when it appeared.
The registry replaced eight separate article pages whose metadata had drifted apart: seven of them showed a different publication date than the news listing. One source of truth is less interesting than eight bespoke pages, and considerably more honest.
What an article is
Articles are the long form: explanations of how something works, technical writing about the stack, and reflections on the work. News carries the timely announcement; the article carries the full treatment — the reasoning, the context, and the detail that would not fit in a listing.
Each article states its assumptions and links its evidence where evidence exists. The source material behind the technical claims — the code, the measurements, the filings — is public in the Foundation's repositories.
Dates and addresses
The date on an article is its publication date. The address is /article/ followed by the article's slug, and the older /article-xxx addresses from the previous site still resolve to the same pages — nothing already linked or indexed breaks.
If an article is corrected after publication, the correction is noted rather than silently made — the same standard our press releases are held to. The page you are reading is the current version, and the record of what changed stays with it.