Ceylon Horos: The Lion at the Boundary
Horos is Ceylon's security umbrella — the conceptual boundary between identity, credentials, authentication, sessions, and authority. The name comes from an old Greek word for a limit or boundary marker.
Every profile on Ceylon eventually needs to answer the same handful of questions: who is this, what are they allowed to prove, what does proving it actually grant them, and where exactly does that authority stop. I gave the umbrella concept covering all of that a name: Horos — the Ceylon security architecture.
What Horos actually covers
Conceptually, Horos spans directory services, a credential authority, authentication, authorization, session authority, a secure-random and cryptographic substrate, recovery, and provisioning. That's a wide net on purpose, because the whole point of naming it as one umbrella instead of a pile of unrelated features is to force the boundaries between those pieces to be explicit instead of assumed.
The boundaries, which are the actual point
The thing Horos is really about is drawing clean lines: between identity and credentials, between credentials and authentication, between authentication and a session, between a session and authorization, between raw authority and how it's presented to a user, between raw entropy and the random output something actually consumes, and between a pre-authentication screen and an authenticated desktop. Every one of those is a place where a lot of systems quietly blur two things that should be separate, and blurring them is usually where the security bugs live later.
I'll get into one of those boundaries in real, specific detail a couple of entries from now — the entropy one, and a bug that came out of a place I genuinely didn't expect. For this entry, I want to stay at the conceptual level, because the shape of the boundaries matters more than any one implementation detail sitting inside them.
Where the name comes from
Horos is an old Greek term, used in Gnostic writing, roughly meaning a boundary or a limit — a marker of where one thing ends and another begins. I picked it because that's exactly what this umbrella is: not a single feature, but the discipline of knowing precisely where one kind of authority ends and the next one's responsibility begins. The lion-at-the-boundary framing is symbolism, not a literal mascot and not a statement about anything beyond the naming itself — I want to be clear about that so nobody reads more into it than a name chosen because it fit.
With the security umbrella named and the boundaries drawn, the next real question is what actually runs inside those boundaries — and that turns out to require rethinking what an "application" even means on a platform that was never going to pretend to be Unix. That's next.
Originally published on The Weekend Report: https://theweekendersproject.com/report/ceylon-horos-the-lion-at-the-boundary