The account takes shape
one citation at a time.
As the SOA Junior, you produce the technical statements of account. You select the right pattern for each contract, then fill in each line — either with free-form documentary values or by citing the exact Manager graph node that produced the figure.
Your role in the chain
You are the last step before the account is final. Everything upstream — clause structuring, actuarial formalisation, Manager instanciation — flows into your work.
Contracts & instances
The sidebar lists all contracts in your tenant. Each contract can have one or more SOA instances — one per pattern used.
Selecting a contract
Click any contract in the sidebar (or use the search box) to open its detail panel. You will see the contract's treaty types and its existing SOA instances.
Creating an instance
Deleting an instance
Click the 🗑 button next to an instance in the list. All its dimension values will be permanently deleted. This action is irreversible — confirm carefully.
SOA Patterns
The SOA Patterns section (read-only) gives you a reference view of all patterns designed by the SOA Senior — accessible directly from the Contracts section in the sidebar.
Each pattern shows its structure: nodes, link types, treaty type restrictions, and the dimensions the SOA Senior has attached to each node. Use this section to understand a pattern before instantiating it, or to check which dimensions you will need to fill.
Pattern compatibility
When creating an instance, the dialog shows a compatibility badge based on the overlap between the contract's treaty types and the pattern's restrictions.
| Badge | Meaning | Can you proceed? |
|---|---|---|
| ✓ Compatible | The contract shares at least one treaty type with the pattern's restrictions | Yes — recommended |
| 🌐 Universal | The pattern has no treaty type restriction — applies to all contracts | Yes — always valid |
| ⚠ Mismatch | No treaty type overlap — the pattern may not be designed for this contract type | Yes, with caution |
| ⚠ cycle | The pattern has a detected cycle — it cannot produce a valid account | No — blocked |
If the pattern you need shows a cycle warning, contact the SOA Senior to fix it before proceeding.
Filling dimensions
After creating an instance, click any node in the pattern DAG to open the dimension fill drawer on the right side of the screen.
The fill drawer
The drawer shows the node's label, its link type (colour-coded), and one fill section per attached dimension. Each section has a general hint (in yellow) and numbered instruction fields to complete.
Fields with a green border are already filled. Click 💾 Save at the bottom of the drawer to persist your values. You can return to any node and update its values at any time.
FORMULA lines — citing Manager data
Some account lines — marked with a 🔗 icon and a dashed border — are FORMULA nodes. Instead of entering a free-form value, you cite the exact Manager graph node that produced the figure for this line.
How to fill a FORMULA node
What if no graph appears?
If all three groups are empty, the Manager has not yet instantiated any relevant graph on a compatible contract. Contact the Manager — the FORMULA node will stay amber (unwired) until a source exists. This is intentional: an unwired FORMULA node signals a gap between the actuarial model and the account structure.
Tracking progress
Fill progress is tracked at two levels simultaneously.
| Where | What it shows |
|---|---|
| Toolbar (DAG viewer) | Live fraction — e.g. "25% filled (2 / 8 nodes)" — updates after every save |
| DAG canvas (FORMULA nodes) | 🔗 green = wired ✓, amber = unwired — updated after every save |
SOA Instances Explorer
A cross-contract view of all your SOA instances — accessible from 🔭 SOA Instances Explorer in the sidebar.
Each card shows the instance identifier, the contract name, the pattern name, and the contract status. Click a card to navigate directly to that contract and instance.
Filters
| Filter | What it restricts |
|---|---|
| All contracts | Show only instances for a specific contract |
| All patterns | Show only instances of a specific SOA pattern |
| All statuses | Show only instances whose contract has a specific status (ACTIVE, CLOSED…) |
The instance count updates in real time as filters are applied. Filters are independent — combine them freely.
Data Checks
Live SQL queries on your tenant data — accessible from 📊 Data Checks in the sidebar.
| View | What it shows |
|---|---|
| SOA Instances — overview | All instances with contract, pattern, status, and treaty types |
| FORMULA citations | Which SOA node cites which Manager graph node — with label, operand, value type |
| Dimension values — detail | All dimension values entered, with node and dimension context |
| Production — technical account export | Full account: all instances × nodes × values + FORMULA citations. One row per node per instance — exportable for reporting. |
Each view has a ▶ Run button. Results display inline with a ⬇ Download CSV link for full export.
Maintenance
Eight cleanup checks accessible from 🔧 Database purge in the sidebar. Always diagnose first — executions are irreversible.
| Code | What it cleans | Risk |
|---|---|---|
| J1 | SOA instances on a contract that no longer exists | High |
| J2 | SOA instances on a pattern that no longer exists | High |
| J3 | Dimension values whose instance was deleted | Medium |
| J4 | Dimension values whose node dimension was detached by the SOA Senior | Medium |
| J5 | Dimension values whose instruction was deleted by the Senior Underwriter | Low |
| J6 | FORMULA citations whose SOA instance was deleted (safety check — normally handled by cascade) | Low |
| J7 | FORMULA citations whose pattern node was deleted by the SOA Senior | Medium |
| J8 | FORMULA citations pointing to a Manager instance that no longer exists — wiring is broken | Medium |
Recommended order: J1 → J2 → J3 → J4 → J5 → J6 → J7 → J8. Running J1 and J2 first removes stale instances and their FORMULA citations. J8 signals broken wiring — the SOA Junior must re-cite the affected FORMULA nodes.