Underwrite the assumptions
Inspect supplied management claims, dependencies and unresolved diligence questions. Keep the source support and the limits beside the finding.
FOR PRIVATE EQUITY & OPERATING PARTNERS
Apply a common discipline.
Keep each company’s context.
Bring a diligence question, operating priority or critical handover. Apply a shared review method while retaining each company’s evidence, qualifications and open questions—from underwriting through ownership changes.
Consulting expertise + software engineering · Scope, access and acceptance checks agreed for the work.
The method can be reused.
The company’s facts and permissions need their own basis.
UNDERWRITE / OPERATE / PREPARE FOR EXIT
Use the discipline across the hold.
Retain the basis for each decision.
Start with a scoped question at the point where evidence, operating knowledge or review continuity matters.
Operate with a reviewable next move
Turn findings into proposed actions and questions for the accountable team. Keep a proposed plan distinct from completed work or demonstrated improvement.
Prepare the record for the next owner
Retain documented decisions, qualifications and open items for authorized review. A retained record is a basis to inspect, not proof of exit readiness.
ONE REVIEW METHOD / TWO COMPANY ACCOUNTS
Both name another person.
What does that actually establish?
Explore a critical-process handover at Northline Dispatch and Harbor Field Services. Shared questions make the differences visible; they do not erase them.
TWO FICTIONAL COMPANIES / ONE REVIEW QUESTIONExplore the method · No live portfolio data
Inspect a company’s account
01 / AGREE A COMMON REVIEW
Reuse the question. Establish the company’s basis.
What supports another person carrying the process and its exceptions? Apply the same review criteria to each company while retaining its process, source and authority context.
- The common question
- What is documented, what has been practiced and what still needs a responsible review?
- Company-specific evidence
- Keep the process, people, supplied account and qualifications attached to that company.
- Acceptance & access
- Agree what would demonstrate coverage and who may inspect or use the material.
A shared protocol is a review method. It does not establish that the companies have equivalent readiness, compatible processes or shared permission.
Fictional review pattern, not a live portfolio console, completed diligence engagement or demonstrated business outcome. The example does not run an analysis.
A SHARED FOUNDATION / SCOPED COMPANY WORK
Reuse the architecture.
Configure the company’s review.
MCOS provides a reusable L1–L3 foundation. Task-specific L4 protocols define the questions, checks and deliverables for the supported company workflow.
MCOS / CONCEPTUAL COMPANY CONFIGURATION
- L1Source & context
- L2Structured evidence
- L3Scoped agent analysis
L4 / TASK-SPECIFIC PROTOCOL
Company A review
Its evidence, configured rules, qualifications and proposed follow-up.
L4 / TASK-SPECIFIC PROTOCOL
Company B review
Its evidence, configured rules, qualifications and proposed follow-up.
SENTINEL / A SEPARATE CLAIM-USE CHECK
May this claim support this purpose now?
Where integrated and configured, Sentinel separates integrity, meaning and current-use authority. A finding retained for one company does not itself establish permission to use it for another company or a later decision.
Try the separate Sentinel exampleWhat can be shared—and what needs agreement?
A review method, approved definitions or agreed protocol pattern can be reused where appropriate. Company evidence, rights, review authority and permitted uses need their own agreement. Moving a pattern between companies can require changes to inputs, extraction rules, checks and integrations.
Portfolio access and separation must be implemented for the engagement. This page’s fictional comparison does not demonstrate a deployed cross-company data service, automatic synchronization or inherited approvals.
Explore the MCOS foundationPRACTICAL STARTING POINTS
Bring one company and one question.
Establish the supported path.
Existing applications offer starting points. A broader portfolio workflow is scoped around its evidence, access and review requirements.
DILIGENCE REVIEW
M&A Diligence
Explore structured review of supplied acquisition material, findings and unresolved diligence questions.
Explore M&A DiligenceKNOWLEDGE CONTINUITY
Key Person Audit
Inspect recorded people, process knowledge and coverage questions before treating a proposed handover as complete.
Explore the KPA exampleOPPORTUNITY ASSESSMENT
AI Discovery
Review where AI could support the company, the supplied business evidence and the requirements for a scoped first application.
Explore AI DiscoveryCONTINUITY / REUSE / RIGHTS
Keep what the next team needs.
Agree what may travel.
Retained context can support a later review. Rights to inspect, reuse or transfer materials are defined for the engagement and the company.
THE COMPANY RECORD
Preserve the account, the proposal and the open state.
The next authorized team needs the source context, selected checks and qualifications. A new model run or a finished presentation should not be the only way to recover the earlier basis.
Explore operational sovereigntyTHE REUSABLE METHOD
Learn from the work. Review the next application.
Patterns can inform a proposed playbook update. Review and authorize the change before reuse, with each company’s constraints intact. No automatic cross-company learning or valuation uplift is implied.
Inspect the financial-review exampleSoftware rights and accounting treatment
Agree the record, source access, export formats, software use and other contractual rights separately from the proprietary MCOS runtime. Retaining an artifact does not establish ownership of every component or determine accounting treatment.
See the supporting CFO detailSTART WITH A SCOPED PORTFOLIO QUESTION
Establish the method.
Keep the company’s basis.
Agree the source material, protocol, responsible reviewer and acceptance checks for one company before extending the approach.