This case follows our existing public case validation process—it is not a new demonstration format, and no case-specific product mode has been added. The source is MorganFranklin Consulting's official public case description. We isolate the later-stage answers first, then reconstruct only what was knowable at the time of the decision into an educational data package. This is an independent teaching simulation based on that public source. It does not represent real correspondence or real client results, and MorganFranklin Consulting has not used, reviewed, endorsed, sponsored, certified, or commissioned Minerva Advisor.

The case opens with a Fortune 50 aerospace, defense, and technology company that divested into three businesses. Two of the divested entities had to rebuild identity and access management from the ground up. Their existing processes were highly manual and outdated, and both companies faced approaching regulatory deadlines. The question before the committee: replicate the entire legacy platform immediately, or validate in phases by critical privileges, controls, and integration risk against clear deadlines first—and what signals would justify stopping, expanding, or reversing course.

This run leaves a five-item work receipt. One, a single selected public source. Two, four defined advisory roles. Three, a clean separation of six known facts, two inferences, and three open questions. Four, a structured comparison of two build paths. Five, three retained alternative explanations plus one explicit reversal condition. Together these give executives an auditable trail behind the final judgment.

What was known: both divested entities needed to rebuild identity and access management, and the inherited legacy process was outdated and manual. What remained unknown at decision time: the true scope of critical-access and service-account gaps, segregation-of-duties issues, termination-of-access weaknesses, cloud-to-on-premises integration dependencies, certification cycles, and whether minimum viable controls could realistically be delivered on schedule.

The strongest challenge: critical gaps might be concentrated in only a few systems, integration dependencies could be minimal, and rollback concerns may not apply everywhere—meaning phasing could be overcautious. The reversal condition is explicit: if a joint inventory proves gaps are limited, dependencies are few, and rollback is verified, the recommendation reverses toward accelerated, hybrid replication with compensating controls rather than a full phased pause.

Held out from Minerva entirely was MorganFranklin's later-stage published outcome: the strategic roadmap it built, control verification and quality assurance work, AWS integration, SailPoint IIQ design and deployment, a certification-framework proof of concept, more than forty thousand privileges assessed, over four thousand controls established or validated, and a seventy percent reduction in manual audit review time. None of that appeared in Minerva's input.

Three advisors cross-check the same judgment from different angles. Marcus frames the real control scope that must be delivered before the regulatory deadline. Sofia models consequences for identity security, audit, and cloud migration. Evelyn challenges whether phasing itself causes delay. All three converge on the same first move: lock down critical access, segregation of duties, and verifiable rollback before anything else. Evelyn adds one caveat—if the deadline is truly imminent and gaps turn out to be limited, over-phasing could raise compliance risk above the risk of straight replication.

The executive enters one condition into the Decision Room: first inventory critical access, segregation of duties, termination of access, and integration dependencies, and verify rollback; if gaps prove limited and minimum controls can be verified, accelerate expansion immediately. The system logs this as a formal response receipt tied to the case record.

The comparison shows exactly how that input changes the judgment. Full legacy replication could shorten some build time but risks carrying outdated processes and unresolved control gaps into both new environments unchanged. Phased verification protects critical access first, at the cost that weak scope discipline could threaten the deadline. With the executive's condition attached, Minerva confirms the phased path—while preserving a clear, evidence-based trigger to accelerate.

The committed action: commission a joint inventory of high-risk privileges, service accounts, and segregation-of-duties gaps across both entities before any replication or migration scoping decision proceeds. Identity security, audit and compliance, and cloud migration teams submit that inventory, along with minimum control scope and rollback evidence, before the expansion decision is finalized against the regulatory deadline.

This run used four model calls. The first decision-ready judgment was delivered in 18.387 seconds, and the complete result, including all three advisor cross-checks, finished in 25.459 seconds—passing the thirty-second first-decision threshold and the forty-five-second complete-result threshold. The case passed all ten decision quality checks. Minerva does not constitute security or compliance advice, and does not claim that official technical work or outcomes occurred. This remains a single-case test and does not represent production service levels or real customer outcomes.