Sample Agent Analysis
Legacy Application Modernisation — Customer Portal · ARQ-DEMO-LEGACY-MOD
Intake Understanding
Confidence: MediumThe customer portal runs on an unsupported legacy runtime and is difficult to maintain. A phased strangler-fig modernisation is proposed while preserving customer-facing availability.
- Legacy customer portal
- Oracle customer database
- Entra ID authentication
- Power BI reporting
- Downstream customer notification services
- Target cloud platform (Azure or AWS — TBD)
- Customer account/profile data
- Authentication data
- Operational reporting data
Classification & Routing Rationale
- Application Architecture
- Security / Identity
- Data Architecture
- Cloud / Infrastructure
- Operations / Support
- Business Continuity
A phased modernisation of a customer-facing portal touching identity, customer data, reporting, and downstream notifications requires Application, Security/Identity, Data, Cloud, Operations, and Business Continuity review.
Key Risks
Customer-facing availability during cutover
HighA failed slice cutover could take the customer portal offline and disrupt self-service.
Control: Strangler-fig per capability; dual-write where safe; tested rollback per slice; customer comms plan.
Customer data migration integrity
HighCustomer account and profile data may not migrate cleanly, producing reporting and support drift.
Control: Migration test harness with row-level reconciliation; freeze windows; sign-off per data domain.
Hidden integration dependencies
MediumUndocumented consumers of the legacy portal (reporting, downstream notification services) may break silently after cutover.
Control: Dependency discovery (logs/network) before migration; contract tests on all known consumers; deprecation comms.
Customer identity and access regression
MediumLegacy portal uses local accounts; migration to Entra ID may miss edge roles or break sign-in for a subset of customers.
Control: Role mapping audit; pilot with shadow access checks; access review post cutover.
Reporting continuity
MediumPower BI reports depend on the legacy schema and may silently drift during phased migration.
Control: Report reconciliation per slice; retire vs re-point reports explicitly with owner sign-off.
Missing Information
- Target cloud platform and hosting pattern (Azure vs AWS) with rationale
- Dependency map for integrations and downstream reporting/notification consumers
- Identity migration approach with Entra ID for customer accounts
- Rollback and cutover plan per migration phase
- Data synchronisation and reconciliation approach between legacy and modernised components
- Operational support model and monitoring plan for the modernised portal
- What criteria will drive the Azure vs AWS decision and when?
- Has a full dependency map been produced for the customer portal?
- What is the customer identity migration approach with Entra ID?
- What rollback criteria apply per phase cutover?
- How will customer data be synchronised and reconciled between legacy and modernised components?
- What is the operational support model and monitoring plan post-migration?
Agent Traces
Intake Understanding Agent
Structure the request.
completedConfidence: MediumHuman review requiredInput summaryLegacy core replacement, strangler-fig.
Output summary6 systems, 3 data categories.
Started 5/30/2026, 8:00:00 AM Completed 5/30/2026, 8:00:01 AMDuration: 1.6 sClassification Agent
Score complexity/risk.
completedConfidence: HighHuman review requiredInput summaryMulti-quarter modernisation.
Output summaryComplexity High, Risk Medium; 6 required, 2 optional.
Started 5/30/2026, 8:00:01 AM Completed 5/30/2026, 8:00:03 AMDuration: 1.3 sRisk Discovery Agent
Surface risks.
completedConfidence: MediumHuman review requiredInput summaryCutover + data migration + dependencies.
Output summary5 risks (2 High, 3 Medium).
Started 5/30/2026, 8:00:03 AM Completed 5/30/2026, 8:00:05 AMDuration: 2.3 sMissing Information Agent
Gap detection.
completedConfidence: HighHuman review requiredInput summaryIntake + classification.
Output summary6 missing items + matched questions.
Started 5/30/2026, 8:00:05 AM Completed 5/30/2026, 8:00:06 AMDuration: 1.1 sNFR Checklist Agent
NFR generation.
completedConfidence: HighInput summaryModernisation profile.
Output summary14 NFR questions across 5 categories.
Started 5/30/2026, 8:00:07 AM Completed 5/30/2026, 8:00:08 AMDuration: 1.3 sRouting Agent
Route to ARB sub-teams.
completedConfidence: HighInput summaryRisk profile + ownership map.
Output summary8 teams (6 required, 2 optional).
Started 5/30/2026, 8:00:08 AM Completed 5/30/2026, 8:00:09 AMDuration: 850 msDecision Evidence Agent
Synthesise decision pack.
completedConfidence: MediumHuman review requiredInput summaryAll agent outputs.
Output summaryMore Information Required + 6 conditions + ADR draft.
Started 5/30/2026, 8:00:09 AM Completed 5/30/2026, 8:00:11 AMDuration: 1.9 s
Ready to run this on your own request?
Sign in to run live AI analysis on your architecture requests, or talk to us about the ARB Copilot Design Partner Program in your own workspace.