Context
The tazama-lf/tazama-demo repo is migrating the legacy EVENT ADJUDICATOR panel to a new ALERTS panel containing three sub-panels (EVENT FLOW, TYPOLOGY PROCESSOR, EVENT ADJUDICATOR). The implementation PR is tracked at tazama-lf/tazama-demo#124 and the full spec is in that PR's description (originated from temp-files/alerts-result.md).
The current Demo User Guide at Guides/demo-ui-guide.md documents the legacy single EVENT ADJUDICATOR panel with a single status light and a yellow ALRT badge. After the demo-side PR merges, the guide will be out of step with the UI.
What needs to change in Guides/demo-ui-guide.md
Update the section(s) covering the right-hand-side EVENT ADJUDICATOR panel to describe the new ALERTS panel layout and behaviour. Specifically:
- Panel name:
EVENT ADJUDICATOR -> ALERTS.
- Sub-panels: the single panel body is now three vertically-stacked sub-panels of equal height:
EVENT FLOW - mirrors the upstream EFRuP rule outcome.
TYPOLOGY PROCESSOR - shows when an interdicting typology fires.
EVENT ADJUDICATOR - shows the final adjudicator decision.
- Sub-panel layout: each sub-panel has a small uppercase gradient header (
EVENT FLOW / TYPOLOGY PROCESSOR / EVENT ADJUDICATOR), a status light on the left, and a centred recessed-pill outcome label on the right. The pill is omitted entirely when there is no outcome (the TYPOLOGY PROCESSOR and EVENT ADJUDICATOR sub-panels render no pill until their first message arrives).
- Outcome mapping (status-light colour / pill label):
EVENT FLOW:
- no message yet -> grey light,
NONE pill
- EFRuP rule result
subRuleRef = block -> red light, BLOCK pill
- EFRuP rule result
subRuleRef = override -> green light, OVERRIDE pill
- EFRuP rule result
subRuleRef = none -> grey light, NONE pill
- EFRuP rule result
subRuleRef = .err -> previous state is preserved; an error line is logged to the browser console (EFRuP error <reason>).
TYPOLOGY PROCESSOR:
- no message yet -> grey light, no pill
- any message on the
interdiction-service-tp socket subject -> red light, INTERDICT pill (terminal; once shown, stays interdict for the rest of the transaction).
EVENT ADJUDICATOR:
- no message yet -> grey light, no pill
report.status = ALRT -> red light, ALRT pill
report.status = NALT -> green light, NALT pill
- Transaction boundary: when a new transaction is submitted (new
MsgId registered as the active correlation id), all three sub-panels are atomically reset to their default state.
- Removed visuals: the legacy single yellow
ALRT badge and the single combined status indicator that lived next to the EVENT ADJUDICATOR h2 are gone. Anything in the guide describing them should be removed.
Source-of-truth references
- Demo repo PR description (when opened) - full spec, screenshots if available.
temp-files/alerts-result.md in the demo repo (working spec used to drive the migration). Sections most relevant to the guide: §4 (layout), §5 (state -> display mapping), §6.5 (transaction boundary), §7 (component sketch).
- Provider socket-handler shapes are in
store/processors/processor.provider.tsx of the demo repo.
Suggested PR scope
- Update
Guides/demo-ui-guide.md only. No structural changes to the docs site needed.
- Include a screenshot of the new panel if possible (the demo repo has a running TEST_MODE that drives all three sub-panels to red
BLOCK / INTERDICT / ALRT for a deterministic capture).
- Target
dev per the docs repo's contribution conventions.
Spec reference
This issue is the tazama-lf/docs follow-up tracked by spec step 9 (A15 audit, "raise an issue in the /docs repository to update the Demo User Guide") of the ALERTS panel migration in tazama-lf/tazama-demo.
Context
The
tazama-lf/tazama-demorepo is migrating the legacyEVENT ADJUDICATORpanel to a newALERTSpanel containing three sub-panels (EVENT FLOW,TYPOLOGY PROCESSOR,EVENT ADJUDICATOR). The implementation PR is tracked attazama-lf/tazama-demo#124and the full spec is in that PR's description (originated fromtemp-files/alerts-result.md).The current Demo User Guide at
Guides/demo-ui-guide.mddocuments the legacy singleEVENT ADJUDICATORpanel with a single status light and a yellowALRTbadge. After the demo-side PR merges, the guide will be out of step with the UI.What needs to change in
Guides/demo-ui-guide.mdUpdate the section(s) covering the right-hand-side
EVENT ADJUDICATORpanel to describe the newALERTSpanel layout and behaviour. Specifically:EVENT ADJUDICATOR->ALERTS.EVENT FLOW- mirrors the upstream EFRuP rule outcome.TYPOLOGY PROCESSOR- shows when an interdicting typology fires.EVENT ADJUDICATOR- shows the final adjudicator decision.EVENT FLOW/TYPOLOGY PROCESSOR/EVENT ADJUDICATOR), a status light on the left, and a centred recessed-pill outcome label on the right. The pill is omitted entirely when there is no outcome (theTYPOLOGY PROCESSORandEVENT ADJUDICATORsub-panels render no pill until their first message arrives).EVENT FLOW:NONEpillsubRuleRef = block-> red light,BLOCKpillsubRuleRef = override-> green light,OVERRIDEpillsubRuleRef = none-> grey light,NONEpillsubRuleRef = .err-> previous state is preserved; an error line is logged to the browser console (EFRuP error <reason>).TYPOLOGY PROCESSOR:interdiction-service-tpsocket subject -> red light,INTERDICTpill (terminal; once shown, stays interdict for the rest of the transaction).EVENT ADJUDICATOR:report.status = ALRT-> red light,ALRTpillreport.status = NALT-> green light,NALTpillMsgIdregistered as the active correlation id), all three sub-panels are atomically reset to their default state.ALRTbadge and the single combined status indicator that lived next to theEVENT ADJUDICATORh2 are gone. Anything in the guide describing them should be removed.Source-of-truth references
temp-files/alerts-result.mdin the demo repo (working spec used to drive the migration). Sections most relevant to the guide: §4 (layout), §5 (state -> display mapping), §6.5 (transaction boundary), §7 (component sketch).store/processors/processor.provider.tsxof the demo repo.Suggested PR scope
Guides/demo-ui-guide.mdonly. No structural changes to the docs site needed.BLOCK/INTERDICT/ALRTfor a deterministic capture).devper the docs repo's contribution conventions.Spec reference
This issue is the
tazama-lf/docsfollow-up tracked by spec step 9 (A15audit, "raise an issue in the /docs repository to update the Demo User Guide") of the ALERTS panel migration intazama-lf/tazama-demo.