Skip to content
Merulan

Architecture Center

How to read Merulan's public cross-capability maps and follow each object to its owning concept or reference.

The Architecture Center is where you see how Merulan parts work as one. Its maps show links that span Capabilities and Surfaces.

Map boundaries

An Architecture Center map covers a link that no one Capability or Surface owns. It names the owner of each object. It orders the steps that cross public boundaries. It leaves out code layout, provider names, internal controls, and facts that could weaken security. This keeps the map useful without showing how Merulan is built.

Reading a map

An Architecture Center map names its objects and links. It also gives their reading order. Start from the row under Traversal that matches your question, then follow its link. A map does not restate a contract. Each object links to its Capability page. Each contract links to the reference page that states it.

Next steps

Continue from the Architecture Center to its maps and to Security.

  • Company Model maps how data, judgment, execution, and learning connect across Capabilities.
  • Operation Lifecycle follows one call from a Surface through admission to its result and readback.
  • Security explains the admission checks that apply across Capabilities and Surfaces.