An application portfolio that inventories, scores, and rationalizes itself.

The business-architecture layer that makes the portfolio legible: the application inventory with owners, hosting and lifecycle stage; the capability map and its hierarchy; the information assets your applications depend on; the value streams that connect capabilities to outcomes; and the links between them.

She stands up the structure and fills it from what your instance already knows, so the portfolio and capability map stop being a spreadsheet nobody trusts.

She reads what each application already carries — lifecycle stage, hosting, owner, the technology behind it — and scores against that, flagging anything past end-of-life or running on unsupported technology. She proposes the risk and lifecycle model rather than inventing ratings, and every score traces back to the attributes it came from.

She frames them, she doesn't make them. Phyllis classifies each application — tolerate, invest, migrate or eliminate — with the evidence behind each call: overlapping capabilities, lifecycle position, risk and business value. The recommendation is staged for your architects to confirm; the decision stays yours.

Correct. Phyllis explores, proposes a plan, and only builds on your explicit approval, with every change staged for review. The technical inventory behind each application stays with your team — she models the architecture on top of it; she doesn't manufacture the underlying data that discovery owns.

Every claim is cited to where it came from in your own instance — the applications missing an owner, the capabilities with no supporting app, the lifecycle stage on each record. She reads your live setup rather than assuming an out-of-box baseline, because these layers ship empty and whatever exists was hand-built, with all the drift that implies.