Perpetual Core Studio · Orchestration layer
The orchestration layerfor operators.
Tagline
Sage thinks. Atelier makes.
Atelier is the orchestration layer underneath Perpetual Core Studio. Operators compose Flows — versioned playbooks that weave together Sage skills, cross-product actions, and human approvals — and your team’s collective memory becomes a real artifact instead of an oral tradition.
What Atelier is for
Atelier is for the operator who has, by hand, written down the way their team actually runs. The discovery cadence. The QA gate. The grant-pipeline rhythm. The onboarding ritual. The work that’s real — the work that decides whether an engagement renews, a cohort lands, a campaign ships clean.
We built Atelier on a thesis that’s held up across every engagement we’ve run: the playbooks that run a real organization are software systems whether or not anyone calls them that. Treating them as paperwork — Notion docs, Slack threads, tribal memory — is what makes ops feel chaotic. Treating them as software is what makes ops scale. Atelier is where you treat them as software.
The vocabulary
Five primitives. Every operations playbook composes from them.
We didn’t pick five because five tested well. We picked five because every orchestrated workflow we’ve seen — in consulting, in nonprofits, in agencies — resolves down to these primitives. Adding a sixth would be cosmetic. Removing one would lose something real.
Sage skill
Call a Sage agent inside a Flow. The output threads into the next step like any other value.
Human task
Assign a checkpoint to a teammate by role. The Flow pauses until the human signs off.
Product action
Invoke any other PC product — Sentinel, Janice, RFP Engine, Sage Mnemosyne — under shared identity.
Event wait
Pause the Flow until a cross-product event arrives. Stripe checkout, RFP match, intern offer accepted.
Gate
Branch on accumulated context. Halt, escalate, or proceed — with the reason written to the trace.
Three workdays in Atelier
What an operator’s week looks like with the playbook running itself.
We built Atelier for three operator shapes: the managing partner at a consulting firm, the executive director at a mission-driven nonprofit, and the account director at a creative agency. The work is different. The orchestration substrate is the same.
Consulting firms
Managing partner · Chief of staff
Productize the playbooks your senior people are running by memory.
Read the workday →
Nonprofits
Executive director · Director of programs
Run grant-funded programs like an operating company, without hiring an ops team you can't afford.
Read the workday →
Agencies
Account director · Ops lead
Run client onboarding, deliverable QA, and renewal nurture as Flows — stop reinventing the playbook every project.
Read the workday →
The worldview
We don’t treat the orchestration layer as a moat. The engine is a standard that will eventually exist somewhere for every operator. We treat the implementation as a commitment to the people whose work depends on it being correct, observable, and honest about what it is.
Read the six principles →
Open a workspace
Stand up your team's first Flow this afternoon.
Atelier opens in fifteen minutes with five starter Flows and every Perpetual Core product already connected. Evaluate for fourteen days; bring your team when you're ready.