Where ideas earn the right to enter the system. Not every concept deserves to be built. The Atrium is where we find out which ones do.
The Atrium is the incubation arm of PorterLabs, the welcoming entry point where new business ideas are structured, validated, and built into MVPs before earning a place in the recursive system. It is not an accelerator. It is not a pitch competition. It is a workshop with protocols.
Ideas don't enter PorterLabs directly. They enter the Atrium. The Atrium is where the work of proving an idea happens, where the thinking that should precede every build actually gets done before a single line of code is written.
The Atrium has strict protocols. Six required documents in Phase 1. Three more in Phase 2. No code is written until Phase 1 is reviewed and approved. No exceptions.
If a company earns it: if the documents hold up, if the logic survives scrutiny, if the market is real and the plan is credible, it graduates to its own Polaris node in the PorterLabs recursive system. It enters a machine that was already running before it arrived.
The Atrium operates on a two-phase protocol. Phase 1 is documentation: six required documents that prove the idea is worth building. Phase 2 is execution: three more documents and then code. No phase can begin until the previous one is approved.
What it is, why it exists, who it's for. Core features, user flows, success metrics. The definitive spec before a line of code.
Market size and structure, competitive landscape, positioning, and customer discovery. No assumptions, only evidence.
Revenue model, unit economics, break-even analysis. The business case in numbers, not slides.
Name, tagline, voice, visual direction. The identity that will carry the company through its first chapter.
Data models, API contracts, auth strategy, tech stack with rationale, and MVP boundaries. Engineering clarity before the first sprint.
Written last. Assume 90-day failure: identify the 3 likeliest failure modes, the earliest detectable signal for each, and the cheap insurance against each. Defines kill/pause triggers before emotions are involved.
Development phases with milestones, a Deferred-Feature Ledger capturing what's intentionally excluded from MVP, and a Hardening Gate checklist before any public launch.
Pre-written, structured prompts for each build phase. The instruction set that powers AI-assisted development, so the build is consistent, repeatable, and transferable.
Path to first revenue: channels, positioning, milestones, and activation sequence. Built before launch, not after. The go-to-market plan that Phase 1 research earns.
Build begins after all three Phase 2 documents exist. Not before. The prompt package guides the development, structured, deliberate, aligned to the approved spec.
The Atrium currently holds two residents. Both entered through the Areopagus. Both are working the protocol. Neither has graduated yet, because graduation has to be earned.
When a company exits the Atrium, it doesn't just launch a product, it enters a system that was already running before it arrived. It inherits the intelligence of every company that came before it.
It gets its own Polaris node. It runs the full recursive loop: Aurelius → Polaris → Nodes → Thundr → Deployment → Analytics → Aurelius. The intelligence built for Clout flows to the next company. The lessons from Kairix flow to Lentira. The system compounds.
The Atrium is the beginning. The system is what comes after. Graduation is not the goal, it's the threshold. What matters is what the company does with the system once it's inside.
The Atrium doesn't have an open application. Companies enter when the Areopagus decides they're ready. The council deliberates. A decision is made. That's the standard, and it isn't changing.
Learn how the Areopagus works