Not a suite. Not a platform. A constellation.

The word you use for your tools shapes how you design them. If you call your AI setup a "suite," you will be tempted to bundle everything. If you call it a "platform," you will build for lock-in. The word "constellation" is doing real architectural work.

What a suite actually is

A suite bundles crafts into one interface. Adobe Creative Suite. Microsoft Office. You buy the whole thing or nothing. Features pile on features because the business model requires constant additions to justify the subscription. Complexity is the product.

In AI terms, a suite is a single system prompt that tries to be a writer, a designer, and a strategist simultaneously. The outputs are competent and interchangeable. Nothing sounds like it came from someone who thinks in a specific craft.

What a platform actually is

A platform hosts things. Notion, Salesforce, Figma's component library. The platform wins when you build on it, not around it. Vendor lock-in is not a bug — it is the business model.

An AI platform would be one place where all your prompts live, maintained by one provider, with one API, one pricing tier. The surface area is clean. The leverage is held by someone else.

What a constellation actually is

A constellation keeps each craft in its own plugin. great-authors does not know about great-filmmakers. They share an architectural shape — the same skeleton — but they run independently. You install what you need. You version them separately. When great-authors ships a new Baldwin persona, you update that plugin; everything else holds still.

This is the software engineering principle of separation of concerns applied to creative work. It is not a metaphor. The .great-authors/ directory is a distinct repository. The .great-filmmakers/ directory is a distinct repository. They share nothing at runtime.

The architectural insight

Most attempts at AI-staffed pipelines fail because they are built as suites: one big context window, one system prompt, one river of conversation. Everything affects everything. The marketers' output bleeds into the writers' context. The engineers' constraints contaminate the designers' brief.

The Constellation solves this by making the contamination impossible. The craft context is sealed inside the plugin. The orchestration layer — great-minds — passes structured handoffs between plugins, not raw conversation history.

If you get stuck

If you find yourself asking "should this persona live in great-authors or great-minds," the question reveals the answer. Personas who write live in great-authors. The persona who decides who writes lives in great-minds. The orchestrator is never a craftsperson.

If two plugins feel like they are overlapping, look for the interface between them. What does great-authors pass to great-publishers? A finished draft. What does great-publishers return? A packaged artifact with a format decision. The handoff is the boundary.

Cross-reference

Lesson 5 (One plugin equals one craft) goes deeper on where the boundary falls and how to test it when you are designing a new plugin.

Deliverable

State in one sentence what the Constellation has that a suite does not, and what a platform has that the Constellation does not. If you cannot produce both sentences without looking, the lesson has not landed yet.