Getting Started

Getting Started routes you through Merulan without defining the features you use. Start with the Core concepts when you need to place your work. Start with a Tutorial when you have one outcome in mind.

Choose a path

The Core concepts explain the shared boundaries before you act. Each page points to the owner when a rule, access decision, or interface detail matters.

• How Merulan works places a Capability, a Surface, and an operation in one path.
• Workspace and access points to the owner of membership and permission decisions.
• Selecting a Surface helps you choose the browser, code, terminal, or agent entrypoint.

Choose a journey

Each Tutorial gives one short route to a visible result and sends feature choices back to its owner. If the result is refused, keep the returned message and use the recovery pointer on that page.

• Create a list starts a named collection in the Console and points to Records & Lists for its rules.
• Run a data pipeline follows one input to a readback and points to Data Pipelines for the workflow.
• Use Merulan in a coding agent records a provider-neutral request, recovery, diff, and outcome.

Use the owner

Getting Started is a map, not a second contract. Use the named Capability for object behavior and recovery. Use the named Surface for access and invocation. The owner remains the authority when the Console, a script, or an agent reports a result. That boundary keeps one answer current when work changes.

Next steps

Getting Started points to the owners that carry work beyond this path.

• Workspaces and membership owns Workspace membership.
• Administer workspace access owns access recovery.
• Surfaces explains each public entrypoint before you choose one for work.