KAINORA PHOENIX | v1.4 KAINORA PHOENIX AI-Powered Turnaround and Recovery Management Shared intelligence, accountable decisions and dependable operating capabilities For owners, private equity operating teams and turnaround principals A valuable business can retain its customers, expertise and assets while losing the ability to execute a consequential commitment. Recovery requires establishing what must work, who carries it and what evidence will show that it does. Oleg Cohen | Founder, Kainora Version 1.4 | 6 November 2026 Recover. Rebuild. Outperform. Executive brief Kainora Phoenix equips turnaround professionals and management teams with a shared intelligence and execution system, helping them understand the business, develop and challenge the recovery plan, coordinate action, and verify whether the intervention is working. Kainora also helps establish the operating capabilities the recovery requires. A turnaround plan depends on the business becoming able to do something it cannot currently do reliably. That may mean reconciling supplier purchases, making credible delivery commitments, coordinating an acquisition or preserving essential judgment during a transition. Advanced AI can help establish these abilities when it is applied to a defined operating problem and carried through to dependable use. Smart turnaround, as used in this paper, is a practical approach to that work. It combines experienced business judgment, AI-assisted interpretation and engineering, explicit operating controls and accountable delivery. The unit of purchase is a business capability, including recovery management itself: a repeatable ability to accomplish meaningful work under agreed conditions. Two connected operating capabilities Managing the recovery is itself an operating capability. The team must establish a defensible understanding, choose a response, coordinate people and dependencies, verify effects and adjust the course. Phoenix supports that work from permissioned discovery through assessment, delivery and continuing operation under the agreed scope. A completed or approved plan is one entry point; uncertainty about the situation or the plan is another. Establishing the business capabilities required by the recovery is a connected undertaking. The business may need dependable supported billing, supplier reconciliation, service delivery or continuity of essential knowledge. Phoenix can engineer, connect and support those abilities under an agreed scope. The management capability helps decide which interventions matter and whether they are working. Kainora Phoenix • 1 KAINORA PHOENIX | v1.4 These scopes can continue together or separately after assessment. Continuing recovery management support requires defined sources, participants, review cadence, duties, access, acceptance, fees and an exit arrangement. Target capability delivery requires its own authorization and acceptance. Each commitment makes the responsibilities, access and evidence of completion explicit. You lead the relationship and the turnaround. Phoenix helps your team understand the client, explain how you work, shape the engagement and carry that understanding through the recovery. The adviser remains involved in diagnosis, planning, execution and adaptation according to the mandate. Management contributes knowledge, challenges interpretations and owns its decisions. Kainora owns the delivery and service responsibilities it contracts to perform. The proposed discipline Choose a consequential commitment and identify the operating constraint behind it. Define the smallest complete capability that can materially change the situation. Combine AI with reliable calculations, business rules, qualified people and existing systems. Rehearse the proposed capability with stakeholders using an installed model, synthetic situations and recorded walkthroughs. Name the sponsor, operating owner, authorizer, contracting party, payer and acceptance authority. Test real work and material exceptions, then observe the business effect against a baseline. Leave usable knowledge, operating ownership and a practical continuation or transition path. What Phoenix contributes Phoenix supports the adviser and management team through investigation, planning, coordination and review, and can establish the operating capabilities the chosen response requires. Kainora brings experienced judgment, reusable AI-native foundations and accountable delivery. Qualified specialists retain financial, legal and transaction mandates. The first purchase is a bounded paid assessment with an installed Recovery Capability Rehearsal near its conclusion. Stakeholders try synthetic operating scenarios and revisit narrated walkthroughs. The next decision may authorize continued recovery management support, target capability delivery, both, or neither. Kainora Phoenix • 2 KAINORA PHOENIX | v1.4 How Phoenix fits together: recovery management and the operating capabilities it requires. The operating work of recovery Financial headroom and a sound strategy create room to act. The operating business still has to fulfill commitments. If returns remain uncredited, delivery dates remain unreliable or critical knowledge disappears with one person, the recovery plan retains a practical dependency. Phoenix focuses on making that dependency explicit and establishing the ability needed to address it. An operating failure can persist even when people are capable and systems individually function. The missing ability may sit between departments, records or decision rights. Treating the problem respectfully matters: recovery requires the participation of the people who understand the work, including those who have been keeping it moving through informal arrangements. Situation Operating ability to examine Supplier leakage or fragmented purchasing Reconcile evidence and carry discrepancies to an authorized resolution. Unreliable quoting or delivery promises Connect costs, capacity, pricing authority and customer commitments. Acquisition or carveout dependency Establish a defined ability before an inherited service or arrangement ends. Failed critical implementation Recover the business function the implementation was intended to support. Kainora Phoenix • 3 KAINORA PHOENIX | v1.4 Situation Operating ability to examine Owner or expert departure Preserve recurring judgment, decisions and work in an owned operating process. These are candidate situations, not prepackaged promises. Industry, data, systems, timing and delivery capacity determine feasibility. The preferred moment is early enough that authority, funding and recovery options remain. Financial distress is neither necessary nor sufficient. The starting conversation concerns a commitment and its consequence: what the business must be able to do, who depends on it, where the work currently fails and what useful evidence is available. A platform deployment becomes an option only after that inquiry. The recovery team needs a shared understanding A recovery mandate may begin with an approved plan, a plan under development or uncertainty about the situation. Its assumptions need examination throughout the undertaking. A changed deadline, departing expert or unavailable integration can alter what the business should do next. The team needs a way to connect those changes to its decisions and delivery commitments. Phoenix Recovery Planning and Execution Intelligence is the shared intelligence and coordination capability for directing the recovery undertaking. It connects the mandate, company knowledge, history, constraints, plans, responsibilities, decisions and results. It helps the team examine the situation, develop and challenge the operational strategy, coordinate action and adjust course as evidence changes. A bounded, permissioned prospect context begins during discovery. The paid assessment deepens and validates it. Integration, automation, access and continuing service are qualified for the agreed scope at each stage. Maintain two linked views: the business situation, including its commitments, people, knowledge and constraints; and the recovery undertaking, including its assumptions, workstreams, decisions, scenarios, releases and evidence. A changed business condition identifies affected work and decisions. Preserve sources, versions, conflicting accounts and unresolved questions. Relevant knowledge comes from permitted records and conversations with the people who handle the work. The guidance loop observes relevant conditions, interprets their implications, compares options, obtains authorization, coordinates permitted work and verifies effects. Operating feedback tests whether the capability works. Delivery feedback tests whether the intervention is progressing. Strategic feedback tests whether assumptions and the chosen course still hold. Missing evidence remains an open condition. The recovery record begins in the first conversation An adviser can learn something decisive before an engagement exists. A sponsor may describe a collections problem. A branch lead may say the work is complete but the records needed to bill it are missing. Both accounts deserve to be preserved. The team has a question to investigate, not yet a verified diagnosis. Kainora Phoenix • 4 KAINORA PHOENIX | v1.4 Phoenix helps the team prepare for those conversations, capture permitted information, compare explanations and present its own method in terms the prospective client can recognize. A versioned method profile connects the team’s phases, responsibilities and supported capabilities to the proposed work. The adviser retains the relationship, professional judgment and identity; Kainora’s contribution is explicit. Consider a fictional industrial-services business. An early conversation introduces the belief that customer approvals exist for completed jobs. The proposal makes checking that condition part of the assessment. The receiving team gets the original account, the open question and the accepted obligation. When the records do not establish approval, it can revisit the billing approach and the affected scope assumption without rewriting the earlier conversation as fact. That is continuity with practical value. The next person can find what was said, what was promised, what remains uncertain and why the work is being undertaken. The client can correct the shared understanding. Information supplied once can inform the next decision, subject to its permitted use. Discovery does not authorize implementation. The team records permission to use the information, the adviser’s engagement authority and the specific Phoenix scope separately. A bounded synthetic example can illustrate the method early. The installed client-specific Recovery Capability Rehearsal remains near the end of a paid assessment. Learning means maintaining a reviewable context and history. Private commercial notes and another client’s information do not become part of a shared client brief or a foundation-model training set. Advanced AI in a complete operating design Advanced AI expands the design options for work involving documents, correspondence, dispersed knowledge and changing circumstances. In a Phoenix undertaking, its role is selected around the capability. The following are candidate contributions to validate in the customer's conditions, rather than assumed performance characteristics. Contribution Use in a recovery undertaking Required complement Interpret evidence Extract proposed facts and relationships from invoices, receipts or correspondence. Retain the source and validate critical fields. Assemble context Bring the relevant history, records and rules together for a case. Apply permissions and identify missing or conflicting evidence. Support judgment Compare explanations, investigate discrepancies and prepare proposed actions. Use qualified reviewers and explicit decision rights. Coordinate work Prepare follow-up and route authorized tasks through connected systems. Track ownership, verify effects and handle failure. Assist engineering Help create designs, configurations and tests for the capability. Review and test changes before releasing them. Kainora Phoenix • 5 KAINORA PHOENIX | v1.4 The practical pattern combines flexible interpretation with explicit rules where correctness must be established. Arithmetic, eligibility, approval limits and permitted system updates should not depend solely on plausible generated text. An uncertain interpretation can be useful if it remains visible as uncertain and moves to the right review. A study with BCG consultants found benefits on tasks within the tested AI's capability and reduced correctness on a task outside it. [1] The useful implication is to evaluate the intended work, including difficult cases, rather than import a productivity percentage into a turnaround business case. The capability must remain understandable to its owner. Internal component names and model choices are secondary to the operating questions: what information enters, what judgment occurs, who may act, what changes and how the result is confirmed. Evidence that can be inspected and challenged For every consequential conclusion, retain the relevant source, date or period, location within the source, and the interpretation made from it. Distinguish reported information, observed evidence, assumptions, inference, disputed accounts and confirmed decisions. Let a qualified person challenge the interpretation, contribute contrary evidence and see what the correction affects. Unreconciled records become investigation and reconciliation work. Assign an owner, identify the dependent decisions and expose the limitation. Useful inquiry can begin before all information is clean; a dependent action must still wait for the evidence its acceptance or authorization conditions require. AI does not establish financial truth merely by producing a coherent explanation. Keep the first response concise: the question, relevant evidence, uncertainty, options and the next decision. Supporting detail remains inspectable. A dashboard may summarize status, but the capability is demonstrated through the work of investigation, decision, coordination and adaptation. Client separation, permitted access, model-provider handling, retention, auditability and deployment choices must be qualified for the actual arrangement. Describe demonstrated controls and known limitations accurately. The terms enterprise and closed application do not establish these properties by themselves. Participation is part of the design Invite management and staff to explain the work, challenge interpretations and identify exceptions. Preserve disagreement until the responsible person resolves it; a generated consensus statement is not agreement. For each contribution, record who is needed, what they must provide, when it is needed and which decision depends on it. Make participation manageable through short, role-relevant tasks and concise reviews. Preserve the distinction between an assigned owner and an owner who has accepted responsibility. Rehearsal helps expose ambiguity, learning needs and unintended workload. It can support confidence and adoption; it cannot guarantee cooperation or remove organizational politics. Kainora Phoenix • 6 KAINORA PHOENIX | v1.4 Selecting the first capability The first capability should be important enough to affect the recovery and bounded enough to establish under the conditions available. A broad transformation ambition can be decomposed into complete operating abilities. The word complete matters: a document extraction step alone may leave the unresolved work, ownership and business consequence untouched. Five considerations for selection Consequence: the commitment, exposure or dependency is material enough to justify attention. Causal relevance: there is a credible reason that improving this ability could affect the result. Controllability: the required authority, access and participation can be obtained. Feasibility: the scope fits the deadline, dependencies and available delivery capacity. Observability: a baseline and evidence of useful operation can be established. This is a decision discipline, not an invented scoring formula. A highly valuable problem may be unsuitable if the critical system cannot be accessed. A technically simple improvement may be immaterial to the recovery. Selection should expose these tradeoffs before capacity is committed. A useful capability statement For the agreed stores and suppliers, reconcile deliveries, parts records, invoices and statements; assign each material discrepancy to an authorized owner; and retain evidence of resolution before the relevant payment decision. This statement gives an illustrative purchasing capability a boundary, intended behavior and acceptance logic. The assessment then tests what that statement requires. It may reveal a smaller first scope, an urgent temporary intervention or a different provider. Temporary containment needs separate authority, limits and a review or expiry condition. It should not become an unowned permanent dependency. Use the customer's existing assets wherever they remain useful. Replacing a core system is a consequential choice with its own cost and disruption; it should follow from the capability requirement rather than from the desire to standardize a technology stack. Copper Basin illustrates the connected work Copper Basin Industrial Services is a fictional business used in synthetic demonstrations. Its starting completed-work register totals USD 140,000: USD 37,000 ready, USD 82,000 blocked and USD 21,000 with outcome unknown. Receiver acceptance starts at zero. These are synthetic work classifications, not reported revenue, cash collections or Phoenix results. The recovery question is whether completed work can become supported billing before the business adds more volume. One USD 18,000 job, CB-J02, has unresolved scope authorization, cost review, accepted ownership and controller approval. The recovery team must establish what the records support and choose the response; the target operating capability must enforce those conditions when work proceeds. Kainora Phoenix • 7 KAINORA PHOENIX | v1.4 In the revised demonstration, a completion record and a scope record conflict. A manager challenges a proposed interpretation. The team inspects the sources, compares waiting, seeking missing evidence and narrowing the supported scope, then records the authorized course and accepted responsibilities. Later synthetic evidence reopens an assumption and requires a reviewed adjustment. This is a specified demonstration sequence; availability is established only by the verified application build. The existing demo packs distinguish scripted AI assistance, modeled rehearsal and software execution against a local receiver simulator. A simulated receiver response demonstrates the tested software behavior under those conditions. It does not establish customer acceptance, live integration, revenue or cash. A seeded handover must remain labeled seeded until it is actually linked to an assessment run. Illustrative supplier purchase assurance Canyon Ridge Auto Service is an illustrative business, not a reported client engagement. It represents a multi-location operator where delivery evidence, parts records, returns and supplier statements are fragmented. The intended outcome is a dependable purchase-topayment capability with clear exception ownership and retained evidence. Stage Operating behavior Authority or proof Capture delivery Associate the invoice and receiving evidence with the delivery. Preserve original evidence and record who received it. Account for parts Identify whether parts are sold, on an open job, in stock or returned. Reconcile against the relevant operating records. Reconcile Compare delivery, internal records and supplier statement. Apply explicit matching rules and expose uncertainty. Resolve exceptions Assign an owner, required action and due date. Retain correspondence and evidence of the decision. Authorize payment Present the supported transaction for accounting review. Retain payment approval and confirm any authorized update. Follow one return. The business has evidence that a part went back, but the supplier statement still shows the charge. AI can help interpret the documents and assemble the case. The workflow identifies the unresolved credit, assigns responsibility and prepares the evidence needed for follow-up. The authorized owner decides the action. Closure requires evidence that the credit was received and reconciled. A system that merely flags the discrepancy has completed only part of that work. The operating capability must also deal with missing receipts, disputed quantities, partial credits, duplicates, unavailable records and delayed responses. Those cases belong in acceptance testing. Measures might include verified recoveries, unresolved exception age, recurring leakage and net staff effort. The example offers no recovery estimate. Candidate credits require validation; benefits require observation. Existing operating and accounting systems remain authoritative according to the agreed design. Kainora Phoenix • 8 KAINORA PHOENIX | v1.4 A paid assessment with a tangible conclusion The assessment is substantive work with its own value. It should reduce uncertainty enough for a sponsor to decide what to do next. It is not a promise that implementation will follow, and an implementation recommendation should not be its predetermined outcome. The assessment culminates in a chance to experience the proposed capability. This is a substantial part of its value: the sponsor sees the approach, operating stakeholders try the work, and the team turns their feedback into an informed next-phase decision. Minimum decision package A description of the failed or missing operating ability and the affected commitment. Current-state evidence, including representative transactions, exceptions and dependencies. A bounded capability definition and alternatives, including preserving current arrangements where appropriate. Named responsibilities, required customer effort, access and decision dependencies. An initial value case including delivery and continuing operating costs. Acceptance conditions, proposed measures and a proceed, redirect, defer or stop recommendation. An installed Recovery Capability Rehearsal, agreed stakeholder access, narrated walkthroughs and reviewed scenario evidence. The payer, authority to conduct the assessment and access it requires must already be workable. Assessment can resolve a bounded uncertainty; it cannot compensate for the absence of a sponsor or an unfunded undertaking. Fees, duration and participation are agreed for the specific scope. Separate commitments after the assessment Implementation establishes the agreed capability. It covers engineering, connections to existing systems, evaluation with intended users and preparation for use. Acceptance and stabilization make limitations, unresolved issues, support and escalation visible. Any urgent containment or temporary bridge has its own authorization and limits. Continuing operation covers only the responsibilities actually contracted, such as monitoring, maintenance, incident response and agreed improvements. Material changes and additional capabilities require a new decision. The customer retains a practical transition path. This structure gives the sponsor reviewable commitments while preserving continuity across the work. It also makes a credible stop decision possible before a disappointing demonstration becomes a much larger obligation. Recovery Capability Rehearsal Experience the capability before committing to the build. Illustrative rehearsal using synthetic situations. Kainora Phoenix • 9 KAINORA PHOENIX | v1.4 Recovery Capability Rehearsal is an installed, interactive model of the proposed operating capability. It is included near the end of the paid assessment and uses synthetic data and situations grounded in the problem that has been assessed. A working experience stakeholders can return to The guided walkthrough introduces the work and its important choices. Direct access lets stakeholders act in their intended roles and explore agreed scenarios themselves. Short narrated recordings make the experience easy to revisit and explain to authorized colleagues. This is a tangible expression of Kainora’s delivery approach. It helps participants understand what is within reach, exposes questions while the design can still change and makes the next investment decision more concrete. What the rehearsal makes visible Rapid capability modeling creates a digital twin of the assessed problem: a bounded representation of the relevant work, participants, records, rules, decisions and target conditions. The operating owner helps confirm its fidelity. Synthetic execution then runs the proposed behavior against representative situations. Experience What stakeholders can examine Ordinary work A transaction progresses from evidence through the assigned work to an observable modeled result. Material exceptions Missing evidence, disputed returns or conflicting records remain visible and route to the appropriate owner. Decision authority The model shows what a role may decide, what requires approval and where an action must stop. State and evidence Participants inspect what changed, why it changed and what supports closure. Feedback and refinement Questions and discovered gaps update the capability definition and implementation decision. A supplier credit example Use synthetic records to follow a returned part whose credit is missing. Assign the exception, review the return evidence, request the modeled credit and reconcile the simulated response. Then remove the receipt or introduce a disputed return. Stakeholders experience how ownership, evidence and authorized decisions affect the next step. Reusable platform foundations and a focused scenario set make this economical to include in assessment. The scope identifies stakeholder access, its duration, scenarios, recordings and review effort. It creates a shared understanding without assuming an unrestricted sandbox. Kainora Phoenix • 10 KAINORA PHOENIX | v1.4 A rehearsal demonstrates modeled operating behavior under stated assumptions. Live integration, production readiness, adoption and realized business benefits require subsequent implementation and evidence. A rehearsal is neither a live pilot nor a standalone technical proof of concept. Its purpose is to let people experience and refine the proposed operating capability before authorizing production implementation. Recovery Capability Rehearsal: see it, try it and revisit it within the scoped assessment. ASCENT connects the recovery journey Kainora Phoenix ASCENT is the agile, AI-native recovery and transformation method. It combines highly automated execution, AI-assisted analysis and guidance, experienced judgment and accountable human direction. Every stage has a value objective, an owner, a decision, evidence and an explicit handover. Routine actions can execute within approved delegation. People retain authority over funding, scope, risk acceptance, activation and material changes. The journey is Align and authorize; Assess and define; Model and rehearse; Engineer and connect; Prove and activate; Stabilize and transfer; Operate and evolve. Shared context, decisions and evidence carry forward. Discoveries can reopen affected decisions without discarding valid work. Agree the people, access, decisions and participation the customer must supply. Kainora coordinates the contracted delivery so a stretched team can focus on its own knowledge and authority. Use rehearsal to identify disputed responsibilities, informal workarounds and learning needs. Acceptance checks whether intended people can do the work; stabilization observes whether they actually use the capability. Retire obsolete arrangements only under an authorized transition plan. When a commitment cannot wait, authorize a bounded temporary intervention while assessment and durable capability formation proceed. Give that intervention an owner, limits Kainora Phoenix • 11 KAINORA PHOENIX | v1.4 and a review or expiry condition. Define delivery coverage, escalation, receiving ownership and a transition path so continuity does not depend on one person. Actual coverage must be confirmed before commitment. Controls that belong in the work Governance becomes practical when it determines what happens in an ordinary transaction and when something goes wrong. The design should specify source records, permissions, review conditions and evidence of completion. A general instruction to keep a human involved is too vague to establish who must decide, what they see and what they are authorized to do. Operating question Design requirement What can be trusted as evidence? Retain provenance, distinguish inference and flag missing or conflicting records. Who may decide and act? Assign role permissions, approval conditions and explicit delegations. What happens when confidence is insufficient? Route to a qualified owner with the relevant evidence and an unresolved status. Did the action actually occur? Verify the intended effect in the authoritative system. How is a mistake contained? Provide escalation, recovery procedures and a controlled fallback. What changes after launch? Review and test material changes; retain the decision and version history. NIST's generative AI profile recommends evaluating capabilities in relevant conditions and verifying source material. [2] Phoenix translates those concerns into scope-specific operating tests; this is an application of the method, not a claim of NIST certification. Acceptance should exercise ordinary work and material exceptions with intended users. For purchasing, that includes ambiguous records, partial returns and mismatched statements. For delivery commitments, it may include changed capacity or an unavailable supplier. Test conditions and unresolved issues should be visible to the acceptance authority. The security and deployment arrangement must be qualified for the actual information and systems involved. Access controls, data handling, retention and provider dependencies require explicit choices. A recovery deadline is a reason to narrow the undertaking, not to leave consequential operating authority undefined. Evidence and economics for the sponsor The sponsor needs evidence at three levels. Rehearsal enriches assessment evidence by showing modeled behavior and capturing stakeholder experience. Accepted live capability and observed business benefit require their own evidence. Kainora Phoenix • 12 KAINORA PHOENIX | v1.4 Evidence level What it establishes What still needs proof Accepted assessment The analysis, rehearsal and recommendation support an informed decision. Implementation feasibility and outcomes within the agreed next scope. Accepted capability Defined work passes its agreed operating conditions. Actual use, adoption and the intended business effect. Observed benefit A relevant measure improves against a stated baseline and period. Attribution limits, persistence and full economics. For each intended effect, record the baseline, measure, period, owner and evidence source. Note other changes that could influence the result. Separate one-time recovery from recurring improvement and avoid counting the same effect twice. Cash margin and capacity A verified refund or applied supplier credit can substantiate a recovery; an identified discrepancy cannot. A recurring savings estimate must include the relevant continuing cost. Released hours represent capacity until the business redeploys that time or changes spending. Revenue improvements should be considered with contribution economics and the constraints on fulfilling additional demand. The full undertaking includes external delivery effort, customer participation, integration, platform and model use, support, review, recovery and change. Reusable foundations may improve delivery economics, but they do not eliminate the work of establishing a particular customer's capability. For a PE operating team, this supports a practical sequence: identify the operating dependency within the value-creation plan, fund a bounded intervention, examine accepted useful operation and review the business consequence. A pattern may later be relevant across a portfolio, but each company still requires its own authority, configuration and evidence. An owner for realized value For each intended benefit, name a value owner, the action required to realize it, the baseline, measure, observation period, evidence source and review decision. A suspected overcharge is not a recovery. Released hours are capacity until redeployed or reflected in spending. Include delivery, participation, platform, model use, support and change costs; separate onetime recoveries from recurring effects and avoid double counting. Recovery Planning and Execution Intelligence begins during permissioned discovery. The paid assessment deepens and validates the earlier context. Its situation model, decision record and installed rehearsal make the next commitment reviewable. Agreed access and continuing operation remain explicit. Kainora Phoenix • 13 KAINORA PHOENIX | v1.4 Working within the turnaround ecosystem Phoenix equips the turnaround principal and management team throughout the recovery. It supports the management of the undertaking and can take responsibility for target capability delivery under the agreed mandate. Management retains the business authority not explicitly delegated. Qualified professionals retain financial restructuring, insolvency, legal, capital and transaction responsibilities. Party Responsibility to make explicit Owner or economic sponsor Priority, investment decision, funding path and escalation authority. Turnaround principal or adviser Overall recovery mandate and interfaces with other workstreams. Operating owner Business decisions, customer participation, use and continuing ownership. Kainora Phoenix Contracted assessment, capability engineering, delivery and service obligations. Specialist or delivery partner Assigned contribution, dependencies, handoff and acceptance evidence. The introducer, authorizer, contracting party, payer and acceptance authority may be different. A warm referral creates access; it does not establish a funded mandate. Before work begins, the parties should be able to name who carries the business consequence, who permits the intervention, who signs, who pays and who accepts the result. Referral, subcontracting, co-delivery and licensing create different obligations. Agreements should make communication ownership, confidentiality, interfaces, acceptance and any compensation explicit. Introductions and information exchange require permission. A useful partner relationship reduces ambiguity for the client. Problems should be disclosed early. The aim is to make the operating work dependable without asking the turnaround leader to become the coordinator of every technical handoff. A practical mandate for the first conversation Bring one consequential commitment and the operating problem that prevents the business from fulfilling it. The first conversation establishes fit and whether a paid assessment has a worthwhile purpose. It should not require a large presentation, a company-wide AI roadmap or premature access to sensitive records. Question Useful starting information What must become possible? The commitment, affected business result and reason action is needed. What currently fails? A concrete example, recurring exception or missing ability. Kainora Phoenix • 14 KAINORA PHOENIX | v1.4 Question Useful starting information Who carries the result? The operating owner, sponsor and decision authority. What can be funded? The contracting and payment path; limits on the undertaking. What must the work respect? Deadline, existing systems, access constraints and customer availability. How will acceptance be decided? The acceptance owner and candidate evidence of useful operation. Who owns the result after launch? Support, escalation and a continuation or transition path. A useful capability statement names the business ability, the population or work covered, the decisions and exceptions included, the operating conditions and the evidence of completion. It creates a basis for assessment; it is not a substitute for discovery or a fixed scope before the evidence is examined. Proceed when consequence, sponsorship, funding, access, feasibility, acceptance and continuity can be made workable. Defer when a named condition is missing. Decline when the assignment remains uncontrollable or cannot support a worthwhile result. That discipline protects the customer as well as the delivery team. A credible engagement also addresses what happens if the investigation disproves the original hypothesis. The ability to stop or choose a different route is part of the assessment's value. Kainora Phoenix and the next conversation Kainora Phoenix equips turnaround professionals and management teams with a shared intelligence and execution system, helping them understand the business, develop and challenge the recovery plan, coordinate action, and verify whether the intervention is working. Kainora also helps establish the operating capabilities the recovery requires. Its signature is Recover. Rebuild. Outperform. Improvement is an ambition to establish with evidence, not a universal outcome promise. The differentiation is the continuity of the undertaking: business judgment shapes the capability, reusable foundations make it tangible during assessment, and coordinated delivery carries it into accepted operation. Recovery Capability Rehearsal gives stakeholders direct experience of the proposed work before the implementation commitment. About Oleg Cohen Oleg Cohen is the founder of Kainora. His background spans more than three decades of enterprise solutions, architecture and business building. He brings that enterprise delivery experience to Phoenix's defined operating recovery workstreams. Oleg is also the author of Managing After Intelligence. Kainora Phoenix • 15 KAINORA PHOENIX | v1.4 The next conversation Where does the recovery get stuck: establishing reliable information, reaching a decision, coordinating people, or making the operation work reliably? Bring one consequential recovery situation and the person responsible for it. We can examine the decision or operating constraint and determine whether a scoped paid assessment would help. The assessment includes a bounded installed Recovery Capability Rehearsal near its conclusion, with agreed stakeholder access, narrated walkthroughs, reviewed feedback and a next-commitment recommendation. Contact Which part of your recovery or value-creation plan depends on getting something working that the current arrangements have not been able to deliver? Bring that situation to a conversation with Oleg. If there is a fit, the next step is a bounded paid assessment with explicit deliverables and a decision at the end. Oleg Cohen | Founder, Kainora info@kainora.ai | kainora.ai Source and method notes Primary basis: Kainora Phoenix Canon and Philosophy v1.4, 6 November 2026; Kainora Phoenix Offering Definition v1.4, 6 November 2026; Kainora Business Capability Engineering and Operation v1.0, 1 November 2026. This external white paper interprets those offering documents and does not amend them or a customer contract. [1] Dell'Acqua et al., Navigating the Jagged Technological Frontier, Organization Science, 2026. https://doi.org/10.1287/orsc.2025.21838 [2] NIST, Generative Artificial Intelligence Profile, AI 600-1, 2024. https://doi.org/10.6028/NIST.AI.600-1 Research is supporting context, not evidence of Phoenix results. Scenarios and editorial artwork are illustrative. Version 1.4 | 6 November 2026. Version 1 point 4 revision note Discovery and Engagement is now included from the first substantive conversation, with the team’s method profile, reviewed claims, explicit authority, versioned commitments and an acknowledged assessment handover. Source: Discovery and Engagement Amendment v1.0, 6 November 2026. The seven ASCENT stages and separately authorized assessment, delivery and operation remain intact. Application implementation is specified separately. Kainora Phoenix • 16