Notice Intake
Normalize the revised notice and preserve section-level source anchors.
Context TriageFinance Demo
MAS Document Analysis Pipeline
A five-step analyst workflow: ingest a revised MAS notice, compare versions, extract obligations, map products and create an impact report.
Structure Blueprint
Step-by-step Design
Version Diff
Compare the revised notice with the baseline and isolate material changes.
Semantic CompactionObligation Extract
Turn changes into obligations, deadlines, owners, and evidence.
Prompt ChainingProduct Mapping
Connect obligations to product lines, customers, controls, and operational teams.
RAG PipelineImpact Report
Produce readiness score, risk matrix, executive summary, and action register.
Progress TrackingReview Loop
Ambiguous or high-impact findings remain reviewable and traceable.
Approval GateScreenshots
Pattern Mapping
| Pattern | Design role |
|---|---|
| Context Triage | Separate source sections, changed clauses, and background context. |
| Semantic Compaction | Convert a long notice into reviewable changes and obligations. |
| Progress Tracking | Expose readiness score, risk matrix, and action register. |
| Approval Gate | Preserve human review for ambiguous or high-impact changes. |
Design Insights
Document change must become product impact
Finance teams act on affected products and controls, not raw paragraphs.
Progress visibility matters
Compliance work is collaborative, so status and action ownership must be visible.
The pipeline is the explanation
Each step is inspectable, which makes the final report more trustworthy.
Run Path
cd showcases/finance/demo-doc-analysis
streamlit run app.pyshowcases/finance/demo-doc-analysis/README.mdimages/training/visual/mas-document-analysis-blueprint.png