How Merulan works

Merulan works through three parts. A Capability owns work. A Surface reaches it. An operation is an action a Surface may offer.

Choose an owner

Merulan works through a Capability when you need an object's behavior or recovery. Start with Records & Lists when that manual owns your work. The manual stays responsible for the details that this orientation leaves out. Merulan works through a Surface when you act from a browser, code, a terminal, or an agent. Surfaces maps each caller to the current public entrypoint. The Surface guide explains access without taking the Capability's behavior.

Read the operation

Merulan works through an operation behind a supported Surface. The Capability Operations contract is the place to check whether a Surface offers an action and to read its result or refusal. A missing Surface means you must choose one the contract lists. The result or refusal stays with the Capability so every caller reads the same outcome.

Next steps

Merulan works best when the named owner stays with the work.

• Selecting a Surface matches your caller to an entrypoint before you invoke work.
• Data Pipelines shows a Capability manual that owns an object and recovery.