Sequence hierarchy

Start with an overview, then explain how receivers handle individual interactions.

Acefy Architecture Language (AAL) · AAL Sequence 0.1 · Dictionary 0.1.0

On this page

Overview, interaction details, and All interactions

Start with the journey overview. Each detail explains how the receiving participant handles its parent message, including calls to collaborators. For Customer → Portal: Sign in, focus on the Portal. When Portal calls Authentication API to validate credentials, that message’s detail focuses on the Authentication API. Avoid repeating the incoming request as an additional call. This is authoring guidance; existing explanations remain valid.

  1. Select a message and choose Create Detail Sequence. The empty detail reuses its endpoints; add collaborators and interactions as needed.
  2. Active sequence lists each detail with its owning interaction and receiver. Choose a parent sequence to return with its owning message selected.
  3. Use the ownership tree to open a focused diagram. Two detail layers are supported beneath the overview. L1/L2/L3 describe depth, not fixed business, service, or component viewpoints.
  4. All interactions combines the explanations on shared participant columns, with named entry and Back to parent separators. Selecting a message edits its owner without leaving this view. Opening a detail or choosing a sequence returns to the focused view.

Details remain independent explanations, not executable expansion. Activations and lifetimes are local to each sequence. Flat visual refinements save separately; individual layouts remain intact. Focused image exports include their title, parent interaction, and receiver.

Three-level login journey
Digital ApplicationApplicationData PlatformData platformOverview · Customer LoginDetail · Customer → Customer Portal · Sign in · Focus: Customer Portal · Authenticate CustomerDetail · Customer Portal → Authentication API · Validate credentials · Focus: Authentication API · Validate Credentials and Issue TokenBack to Authenticate CustomerBack to Customer LoginCustomeractorCustomer PortalsystemAuthentication APIapiToken StoredatabaseSign inValidate credentialsHTTPSValidatecredentialsStore token hashSQLStoredTokenSession tokenWelcome

Sign in focuses on the Portal. Validate credentials focuses on the Authentication API, which validates credentials and stores a token hash. Return separators show where each parent explanation resumes. Scroll inside the diagram to see its full size. These previews use the editor’s actual layout and SVG renderer.

Read the complete AAL
Three-level login journey
aal sequence "0.1" dictionary "0.1.0"
interaction LoginJourney "Customer Login" {
    participant Customer "Customer" { type actor }
    participant Portal "Customer Portal" { type system }
    participant Auth "Authentication API" { type api technology "HTTPS" }
    participant Tokens "Token Store" { type database }
    group Application "Digital Application" { participants [Portal, Auth] type "Application" icon "/deployment-icons/generic/application.svg" }
    group Storage "Data Platform" { participants [Tokens] type "Data platform" }
    sequence Overview "Customer Login" {
        participants [Customer, Portal]
        message Login Customer -> Portal sync "Sign in" { detail Authenticate }
        message Welcome Portal -> Customer return "Welcome"
    }
    sequence Authenticate "Authenticate Customer" {
        participants [Customer, Portal, Auth]
        message Credentials Portal -> Auth sync "Validate credentials" { detail TokenExchange protocol "HTTPS" }
        message Session Auth -> Portal return "Session token"
    }
    sequence TokenExchange "Validate Credentials and Issue Token" {
        participants [Portal, Auth, Tokens]
        message Issue Auth -> Auth sync "Validate credentials"
        activate TokenWork Auth
        message Persist Auth -> Tokens sync "Store token hash" { protocol "SQL" }
        message Stored Tokens -> Auth return "Stored"
        message Token Auth -> Portal return "Token"
        deactivate TokenDone TokenWork
    }
}

Try an interaction detail

  1. Select Sign in in the overview and create its detail.
  2. Add detail to Validate credentials, then choose its parent in Active sequence to return.
  3. Turn on All interactions to read the combined journey.

What you should see: one root with separate details owned by their messages. All interactions reveals the hierarchy without combining the editable sequences.

Each Sequence diagram has exactly one L1 root. Other sequences are L2/L3 details owned by interactions. An owning message has one detail, and each detail has one owner. Deleting an owner or containing branch confirms descendant removal. Undo restores the entire transaction.