Service Architecture

The strategy was sound. The org chart was clean. The consultant was credentialed, the process was well-designed, and the facilitated retreat produced genuine moments of clarity. Then six months later, someone in that organization told you: we went back to the old way. The report didn't hold.

This is not unusual. It is the most common outcome of a particular kind of organizational consulting — the kind that treats the presenting problem as the actual problem, optimizes for a deliverable, and hands over findings before those findings encounter the organization's actual conditions.

What doesn't hold isn't what you can see in the report. It's what the report had to pass through to become real: the informal authority structure that doesn't appear on any org chart, the conversation two specific people keep almost having, the story the organization carries about whether the stated change matches what leadership is actually rewarding. These are not soft considerations. They are the mechanism by which change holds or reverts.

Every Limicelia engagement operates at three layers simultaneously. Layer 1 is what the client buys. Layer 2 is what the practitioner holds. Layer 3 is what's being cultivated at the substrate. Most organizational consulting only reaches Layer 1.

Layer 3 is the long measure. Not whether the org liked the process. Whether, two years later, they're handling the same class of problem without calling us.

A service catalog names what you can buy. A pattern language names what works, and under what conditions, and when it fails. The difference matters because it determines what accumulates. A catalog can grow indefinitely without adding up to anything. A pattern language builds toward a body of practitioner knowledge that gets sharper with use.

Patterns, in the sense Chris Alexander developed the concept, are not invented. They are recognized: something that keeps working across different contexts, with different organizations, in different conditions. When you've navigated the same configuration enough times to name the forces that make it work or fail, you have a pattern. "Conflict as Data" is a pattern. "Conflict Resolution Service" is a deliverable description. The pattern carries entry conditions, what the practitioner holds, what changes, and what it costs when it fails.

Limicelia is building toward this. The Service Studio exists to surface what's been learned across engagements, test whether it holds as a pattern, and give it a name that captures the actual dynamic rather than the deliverable or the method. Not everything that gets surfaced becomes a pattern. Premature naming produces false certainty about when to offer something.

Each domain is a family of patterns and forms organized around a recurring class of organizational problem. Click any domain to see entry conditions, the arc of work, and exit criteria. Tier status: Settled — proven, delivered multiple times. Forming — delivering, exit criteria still sharpening. Tending — recognized but not yet reliably offered.

Vibes are not static. An org can be in Repair Vibe around one issue and Emergent around another. Read the vibe of the specific problem, not the organization as a whole.

These are not services — they are the geometry of how a client relationship unfolds. Every engagement is priced and contracted at this level.

What we've actually done. The real relationships behind each domain — where the patterns were first recognized.

How the model connects. Each domain mapped to its operating layer, offer maturity, client evidence, and methods drawn on. Use this to check whether a proposed engagement fits the architecture — and which layer the practitioner needs to be holding.

ISI fiscal sponsorship as the legal and financial container. Revenue flows through ISI. We are not a separate legal entity.

These are wisdom traditions, each held and transmitted by a named practitioner. Limicelia practitioners have trained in or worked directly alongside these lineages. They are not Limicelia's patterns. Attribution stays explicit whenever they appear in client work.

External methodologies practitioners are credentialed or trained in, plus forms Limicelia is developing from its own practice. The external ones appear in proposals when the client context calls for them. The Limicelia forms are ours, still being named and codified.

External — credentialed or trained

Limicelia forms — emerging from practice

These belong in the story of where we came from, not in any pitch, proposal, or service page. Recorded here to prevent regression.