AAL Sequence and examples

AAL reference

Start with aal sequence "0.1" dictionary "0.1.0", then an interaction containing shared participants and sequence blocks. Every participant, sequence, message, activation event, fragment, branch, note, and reference has a globally unique stable ID. Each sequence explicitly lists its participants.

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 "Token Exchange" {
        participants [Portal, Auth, Tokens]
        message Issue Portal -> Auth sync "Issue token"
        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
    }
}

Strings use JSON quoting. Leading // comments survive serialization. Message metadata may contain detail ChildId and description "Text". Participant metadata supports type, description, technology, and optional icon. Source order is event order; coordinates, palette choices, header placement, and Show all belong to layout preferences.

Group declarations without type or icon remain supported; omitting icons selects generic defaults. Invalid typed source remains saveable, with the last valid canvas held until errors are fixed. Format is available only for valid source. Click a diagnostic to reach its line.

AI drafts

Choose End-to-end hierarchy, High-level interaction, System/service interaction, or Technical interaction. Explain your participants, intent, alternatives, and where detail is useful. A technical focus can start at L1: levels describe depth, not allowed participant types.

Describe a customer login with an L1 portal interaction, L2 credential validation, and L3 token persistence. Include a rejected-password alternative and explicit activation spans. Use generic participant icons unless a specific catalog icon is needed.

Review the complete draft before applying it. Application is unsaved and undoable, clears obsolete layouts, and uses the same compiler on server and client. Failures preserve the current project. Existing account allowances and verification still apply.

Use Downloads → Sequence AI Instructions for an external assistant, or follow the shared AI drafting guide.