GuestDemo Mode
Demo Workspace

Sample Agent Analysis

Legacy Application Modernisation — Customer Portal · ARQ-DEMO-LEGACY-MOD

Demo · Sample Agent Analysis — sample data onlyYou're viewing a read-only walkthrough with structured sample agent outputs. Live AI is disabled in demo mode.
Do not enter confidential or regulated data in the public demo environment.

Intake Understanding

Confidence: Medium

The 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.

Request type
Application modernisation / replacement
Business capability
Customer Engagement / Digital Self-Service
Systems involved
  • Legacy customer portal
  • Oracle customer database
  • Entra ID authentication
  • Power BI reporting
  • Downstream customer notification services
  • Target cloud platform (Azure or AWS — TBD)
Data involved
  • Customer account/profile data
  • Authentication data
  • Operational reporting data

Classification & Routing Rationale

MediumConfidence: High
Complexity
High
Risk
Medium
Required review domains
  • Application Architecture
  • Security / Identity
  • Data Architecture
  • Cloud / Infrastructure
  • Operations / Support
  • Business Continuity
Routing rationale

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

    High

    A 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

    High

    Customer 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

    Medium

    Undocumented 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

    Medium

    Legacy 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

    Medium

    Power 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
Questions for requestor
  • 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

  1. Intake Understanding Agent

    Structure the request.

    completedConfidence: MediumHuman review required
    Input summary

    Legacy core replacement, strangler-fig.

    Output summary

    6 systems, 3 data categories.

    Started 5/30/2026, 8:00:00 AM Completed 5/30/2026, 8:00:01 AMDuration: 1.6 s
  2. Classification Agent

    Score complexity/risk.

    completedConfidence: HighHuman review required
    Input summary

    Multi-quarter modernisation.

    Output summary

    Complexity 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 s
  3. Risk Discovery Agent

    Surface risks.

    completedConfidence: MediumHuman review required
    Input summary

    Cutover + data migration + dependencies.

    Output summary

    5 risks (2 High, 3 Medium).

    Started 5/30/2026, 8:00:03 AM Completed 5/30/2026, 8:00:05 AMDuration: 2.3 s
  4. Missing Information Agent

    Gap detection.

    completedConfidence: HighHuman review required
    Input summary

    Intake + classification.

    Output summary

    6 missing items + matched questions.

    Started 5/30/2026, 8:00:05 AM Completed 5/30/2026, 8:00:06 AMDuration: 1.1 s
  5. NFR Checklist Agent

    NFR generation.

    completedConfidence: High
    Input summary

    Modernisation profile.

    Output summary

    14 NFR questions across 5 categories.

    Started 5/30/2026, 8:00:07 AM Completed 5/30/2026, 8:00:08 AMDuration: 1.3 s
  6. Routing Agent

    Route to ARB sub-teams.

    completedConfidence: High
    Input summary

    Risk profile + ownership map.

    Output summary

    8 teams (6 required, 2 optional).

    Started 5/30/2026, 8:00:08 AM Completed 5/30/2026, 8:00:09 AMDuration: 850 ms
  7. Decision Evidence Agent

    Synthesise decision pack.

    completedConfidence: MediumHuman review required
    Input summary

    All agent outputs.

    Output summary

    More 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.