Standalone mode — your ETL hook is not configured. Reset and Deploy-changes will only remove rows tagged metadata.source='training'. Any unmarked rows are presumed to be real customer data and will be preserved. To configure an ETL hook, edit cfg.app2.etl_hook in your config.yaml.

L2 Editor

Each section below is a kind of building block in this institution's L2 shape. Expand one to browse its entries — search the summary or click a card title to see the detail. The diagram link in the top nav shows how the kinds connect.

1. Roles (19 declared)+ Add Role

How roles work — every rail, chain, and limit references a role; some roles are one ledger row (1:1), others fan out at ETL time into many runtime instances (1:N).

1:1 — Singleton accounts (16)

GL line items + control accounts — one ledger row each.

loading…

1:N — Templated roles (3)

Patterns fanned out by ETL — one declaration, many runtime rows per declaration.

loading…

Rails (29)+ Add

loading…

Transfer templates (3)+ Add

loading…

Chains (5)+ Add

loading…

Limit schedules (7)+ Add

loading…

Theme (set) Edit

Theme is a structured form — click Edit to view / change it.

Instance settings (set) Edit

Instance settings is a single YAML block — click Edit to view / change it.

Attribution (not set) Edit

Attribution is a structured form — click Edit to view / change it.