Docs

Board Capital Reallocation Brief docs

This surface packages trim, protect, hold, and redeploy decisions into reproducible routes and JSON outputs.

{
  "generatedAt": "2026-06-01T00:00:00Z",
  "summary": {
    "items": 6,
    "averageSavingsReleaseScore": 56,
    "averageRedeploymentReadinessScore": 75,
    "averageDownsideContainmentScore": 77,
    "averageTimingScore": 74,
    "averageBoardAlignmentScore": 86,
    "averageUrgencyScore": 73,
    "trimCandidates": 1,
    "protectLanes": 2,
    "totalCapitalShiftMillions": 30,
    "highFindings": 2,
    "recommendation": "Trim duplicate procurement packaging, reallocate into the AI and revenue cores, protect identity and biotech continuity, and hold FinTech expansion until proof improves."
  },
  "reallocationBrief": [
    {
      "owner": "Procurement intelligence lead",
      "audience": "Operating committee",
      "action": "TRIM",
      "trimSource": "Duplicate procurement wrappers and one-off trust packaging",
      "reinvestTarget": "Reusable answer packs and evidence reuse core",
      "recommendedMove": "Trim duplicate procurement wrappers and preserve only the reusable answer-pack and evidence core.",
      "nextMove": "Approve a trim across overlapping procurement packaging and redirect the released capacity into reusable answer and trust-evidence assets."
    },
    {
      "owner": "AI operating partner",
      "audience": "Board strategy committee",
      "action": "REALLOCATE_IN",
      "trimSource": "Released procurement and duplicate memo capacity",
      "reinvestTarget": "AI governance and agent-readiness flagship",
      "recommendedMove": "Redirect released capital into the governed AI flagship rather than spread it across disconnected experiments.",
      "nextMove": "Approve reallocation into AI governance, agent readiness, and memo packaging as one flagship operating system."
    },
    {
      "owner": "Identity assurance lead",
      "audience": "Risk committee",
      "action": "PROTECT",
      "trimSource": "Non-core identity presentation overhead",
      "reinvestTarget": "Identity evidence ledger and control-plane continuity",
      "recommendedMove": "Protect the identity evidence spine and harvest savings only from duplicate packaging around it.",
      "nextMove": "Ring-fence the identity evidence core and cut only the duplicate review wrappers around it."
    },
    {
      "owner": "Revenue systems partner",
      "audience": "CFO operating review",
      "action": "REALLOCATE_IN",
      "trimSource": "Underperforming reporting backlog and low-yield experiment noise",
      "reinvestTarget": "Margin leak recovery and revenue infrastructure stabilization",
      "recommendedMove": "Redeploy into the highest-recovery revenue lane and let lower-yield backlog work wait.",
      "nextMove": "Approve a revenue redeployment plan centered on margin leak recovery and experiment-proof reuse."
    },
    {
      "owner": "FinTech diligence lead",
      "audience": "Investor diligence committee",
      "action": "HOLD",
      "trimSource": "Expansion capital for adjacent FinTech wrappers",
      "reinvestTarget": "No move until reserve, KYC, and merchant proof tighten",
      "recommendedMove": "Hold FinTech expansion flat until reserve, KYC, and merchant proof become easier to defend.",
      "nextMove": "Keep FinTech capital flat until reserve exposure, KYC refresh posture, and merchant review timing improve together."
    },
    {
      "owner": "Quality systems sponsor",
      "audience": "Regulated growth committee",
      "action": "PROTECT",
      "trimSource": "Peripheral biotech presentation work",
      "reinvestTarget": "GxP, CAPA, specimen, safety, and narrative continuity",
      "recommendedMove": "Protect the biotech quality system and only defer peripheral presentation work if savings are required.",
      "nextMove": "Protect the biotech quality system and approve only narrow follow-on evidence improvements."
    }
  ],
  "trimCandidates": [
    {
      "owner": "Procurement intelligence lead",
      "audience": "Operating committee",
      "action": "TRIM",
      "savingsReleaseScore": 92,
      "downsideContainmentScore": 73,
      "timingScore": 82,
      "trimSource": "Duplicate procurement wrappers and one-off trust packaging",
      "companyTags": [
        "Procurement",
        "Trust center",
        "Questionnaires",
        "RFP"
      ]
    },
    {
      "owner": "FinTech diligence lead",
      "audience": "Investor diligence committee",
      "action": "HOLD",
      "savingsReleaseScore": 48,
      "downsideContainmentScore": 46,
      "timingScore": 49,
      "trimSource": "Expansion capital for adjacent FinTech wrappers",
      "companyTags": [
        "Payments",
        "Treasury",
        "KYC",
        "Merchant risk"
      ]
    }
  ],
  "redeploymentPlan": [
    {
      "owner": "Procurement intelligence lead",
      "audience": "Operating committee",
      "capitalShiftMillions": 5.4,
      "redeploymentReadinessScore": 78,
      "boardAlignmentScore": 85,
      "urgencyScore": 81,
      "headline": "Procurement is the cleanest release-of-capital lane because overlap is visible and reusable proof already exists.",
      "relatedSurfaces": [
        "procurement.kineticgain.com",
        "questionnaire.kineticgain.com",
        "proofgap.kineticgain.com"
      ],
      "requiredEvidence": [
        "Procurement OS",
        "Questionnaire answer studio",
        "Trust center evidence room",
        "Vendor proof gap monitor"
      ]
    },
    {
      "owner": "AI operating partner",
      "audience": "Board strategy committee",
      "capitalShiftMillions": 7.8,
      "redeploymentReadinessScore": 95,
      "boardAlignmentScore": 94,
      "urgencyScore": 76,
      "headline": "AI is the strongest redeployment target because it multiplies governance, board, and buyer narratives at once.",
      "relatedSurfaces": [
        "scorecard.kineticgain.com",
        "memo.kineticgain.com",
        "watsonx.kineticgain.com"
      ],
      "requiredEvidence": [
        "AI governance scorecard",
        "Executive board brief",
        "Procurement-ready proof set"
      ]
    },
    {
      "owner": "Identity assurance lead",
      "audience": "Risk committee",
      "capitalShiftMillions": 3.1,
      "redeploymentReadinessScore": 69,
      "boardAlignmentScore": 91,
      "urgencyScore": 68,
      "headline": "Identity should be protected because it keeps access, device, and remediation evidence coherent.",
      "relatedSurfaces": [
        "identity.kineticgain.com",
        "protect.kineticgain.com",
        "guest.kineticgain.com"
      ],
      "requiredEvidence": [
        "Identity risk ledger",
        "Access review posture",
        "Remediation queue proof"
      ]
    },
    {
      "owner": "Revenue systems partner",
      "audience": "CFO operating review",
      "capitalShiftMillions": 6.5,
      "redeploymentReadinessScore": 89,
      "boardAlignmentScore": 90,
      "urgencyScore": 79,
      "headline": "Revenue is a strong redeployment target because the savings story is visible to a CFO immediately.",
      "relatedSurfaces": [
        "revenue.kineticgain.com",
        "leak.kineticgain.com",
        "martech.kineticgain.com"
      ],
      "requiredEvidence": [
        "Platform margin leak report",
        "Revenue infrastructure scorecard",
        "Benchmark waterfall"
      ]
    },
    {
      "owner": "FinTech diligence lead",
      "audience": "Investor diligence committee",
      "capitalShiftMillions": 2.8,
      "redeploymentReadinessScore": 54,
      "boardAlignmentScore": 63,
      "urgencyScore": 74,
      "headline": "FinTech should hold because downside clusters are outrunning the current proof quality.",
      "relatedSurfaces": [
        "payments.kineticgain.com",
        "treasury.kineticgain.com",
        "merchant.kineticgain.com"
      ],
      "requiredEvidence": [
        "Investor diligence pack",
        "Treasury signal lab",
        "Merchant review posture",
        "KYC queue evidence",
        "Vendor replacement intelligence"
      ]
    },
    {
      "owner": "Quality systems sponsor",
      "audience": "Regulated growth committee",
      "capitalShiftMillions": 4.2,
      "redeploymentReadinessScore": 67,
      "boardAlignmentScore": 92,
      "urgencyScore": 62,
      "headline": "Biotech should be protected because the regulated system already reads as one defensible story.",
      "relatedSurfaces": [
        "gxp.kineticgain.com",
        "capa.kineticgain.com",
        "specimen.kineticgain.com"
      ],
      "requiredEvidence": [
        "Change control board",
        "CAPA ledger",
        "Specimen custody proof",
        "Safety signal router"
      ]
    }
  ],
  "riskMap": [
    {
      "code": "downside-cluster",
      "severity": "high",
      "track": "FINTECH",
      "audience": "Investor diligence committee",
      "message": "Downside pressure is clustering faster than the current plan contains it."
    },
    {
      "code": "timing-fragile",
      "severity": "high",
      "track": "FINTECH",
      "audience": "Investor diligence committee",
      "message": "Timing is fragile enough that the board should sequence this move carefully rather than assume immediate execution."
    },
    {
      "code": "thin-proof",
      "severity": "medium",
      "track": "FINTECH",
      "audience": "Investor diligence committee",
      "message": "The reallocation narrative still rests on thin proof and needs tighter evidence before approval."
    },
    {
      "code": "trim-ready",
      "severity": "medium",
      "track": "PROCUREMENT_TRUST",
      "audience": "Operating committee",
      "message": "This lane can release capital now without breaking the board story."
    },
    {
      "code": "protect-core",
      "severity": "info",
      "track": "IDENTITY_SECURITY",
      "audience": "Risk committee",
      "message": "This lane behaves like protected core infrastructure and should be defended from opportunistic cuts."
    },
    {
      "code": "protect-core",
      "severity": "info",
      "track": "BIOTECH_DIAGNOSTICS",
      "audience": "Regulated growth committee",
      "message": "This lane behaves like protected core infrastructure and should be defended from opportunistic cuts."
    },
    {
      "code": "redeploy-now",
      "severity": "info",
      "track": "AI_PLATFORM",
      "audience": "Board strategy committee",
      "message": "This lane is ready to absorb released capital in the next committee cycle."
    },
    {
      "code": "redeploy-now",
      "severity": "info",
      "track": "REVENUE_SYSTEMS",
      "audience": "CFO operating review",
      "message": "This lane is ready to absorb released capital in the next committee cycle."
    }
  ],
  "verification": [
    "Synthetic capital-reallocation data only - no live committee memos, internal forecasts, or actual budget approvals are included.",
    "Savings release, redeployment readiness, downside containment, timing, board alignment, urgency, and capital-shift metrics are modeled from the sample executive-intelligence estate in this repo.",
    "This surface is read-only and shows how Kinetic Gain can package trim, protect, hold, and redeploy decisions into one board-readable capital brief.",
    "Company tags and track labels are synthetic design aids rather than audited market or financial signals.",
    "Every route and packet is reproducible from the included sample export."
  ],
  "sample": [
    {
      "id": "procurement-trim-duplicate-wrappers",
      "owner": "Procurement intelligence lead",
      "audience": "Operating committee",
      "track": "PROCUREMENT_TRUST",
      "action": "TRIM",
      "trimSource": "Duplicate procurement wrappers and one-off trust packaging",
      "reinvestTarget": "Reusable answer packs and evidence reuse core",
      "boardQuestion": "Where can we release spend without weakening the trust story buyers already expect?",
      "currentPosture": "Procurement proof is strong, but too many buyer-facing wrappers still overlap before reuse is maximized.",
      "recommendedMove": "Trim duplicate procurement wrappers and preserve only the reusable answer-pack and evidence core.",
      "savingsReleaseScore": 92,
      "redeploymentReadinessScore": 78,
      "downsideContainmentScore": 73,
      "timingScore": 82,
      "boardAlignmentScore": 85,
      "urgencyScore": 81,
      "capitalShiftMillions": 5.4,
      "headline": "Procurement is the cleanest release-of-capital lane because overlap is visible and reusable proof already exists.",
      "narrative": "The board can approve savings here without undermining the core trust story, as long as the released effort moves into reusable answer and evidence infrastructure.",
      "nextMove": "Approve a trim across overlapping procurement packaging and redirect the released capacity into reusable answer and trust-evidence assets.",
      "companyTags": [
        "Procurement",
        "Trust center",
        "Questionnaires",
        "RFP"
      ],
      "relatedSurfaces": [
        "procurement.kineticgain.com",
        "questionnaire.kineticgain.com",
        "proofgap.kineticgain.com"
      ],
      "requiredEvidence": [
        "Procurement OS",
        "Questionnaire answer studio",
        "Trust center evidence room",
        "Vendor proof gap monitor"
      ]
    },
    {
      "id": "ai-redeploy-governance-flagship",
      "owner": "AI operating partner",
      "audience": "Board strategy committee",
      "track": "AI_PLATFORM",
      "action": "REALLOCATE_IN",
      "trimSource": "Released procurement and duplicate memo capacity",
      "reinvestTarget": "AI governance and agent-readiness flagship",
      "boardQuestion": "Where does released capital compound governance, diligence, and procurement leverage fastest?",
      "currentPosture": "The AI governance lane already resolves into scorecards, procurement proof, and executive memos.",
      "recommendedMove": "Redirect released capital into the governed AI flagship rather than spread it across disconnected experiments.",
      "savingsReleaseScore": 41,
      "redeploymentReadinessScore": 95,
      "downsideContainmentScore": 81,
      "timingScore": 88,
      "boardAlignmentScore": 94,
      "urgencyScore": 76,
      "capitalShiftMillions": 7.8,
      "headline": "AI is the strongest redeployment target because it multiplies governance, board, and buyer narratives at once.",
      "narrative": "If capital is being reallocated, the AI governance flagship is the lane most likely to turn that move into visible leverage across procurement, platform, and board surfaces.",
      "nextMove": "Approve reallocation into AI governance, agent readiness, and memo packaging as one flagship operating system.",
      "companyTags": [
        "IBM",
        "Azure",
        "OpenAI",
        "MCP"
      ],
      "relatedSurfaces": [
        "scorecard.kineticgain.com",
        "memo.kineticgain.com",
        "watsonx.kineticgain.com"
      ],
      "requiredEvidence": [
        "AI governance scorecard",
        "Executive board brief",
        "Procurement-ready proof set"
      ]
    },
    {
      "id": "identity-protect-control-spine",
      "owner": "Identity assurance lead",
      "audience": "Risk committee",
      "track": "IDENTITY_SECURITY",
      "action": "PROTECT",
      "trimSource": "Non-core identity presentation overhead",
      "reinvestTarget": "Identity evidence ledger and control-plane continuity",
      "boardQuestion": "Which lane should be protected because it carries trust for multiple exposure narratives at once?",
      "currentPosture": "Identity proof is live across review, posture, and entitlement lanes, but it still acts as one control spine.",
      "recommendedMove": "Protect the identity evidence spine and harvest savings only from duplicate packaging around it.",
      "savingsReleaseScore": 53,
      "redeploymentReadinessScore": 69,
      "downsideContainmentScore": 89,
      "timingScore": 72,
      "boardAlignmentScore": 91,
      "urgencyScore": 68,
      "capitalShiftMillions": 3.1,
      "headline": "Identity should be protected because it keeps access, device, and remediation evidence coherent.",
      "narrative": "The board does not benefit from cutting the lane that underwrites access, posture, and remediation trust. Protect the core and only trim duplicate shells.",
      "nextMove": "Ring-fence the identity evidence core and cut only the duplicate review wrappers around it.",
      "companyTags": [
        "CyberArk",
        "Okta",
        "Entra",
        "Intune"
      ],
      "relatedSurfaces": [
        "identity.kineticgain.com",
        "protect.kineticgain.com",
        "guest.kineticgain.com"
      ],
      "requiredEvidence": [
        "Identity risk ledger",
        "Access review posture",
        "Remediation queue proof"
      ]
    },
    {
      "id": "revenue-redeploy-margin-recovery",
      "owner": "Revenue systems partner",
      "audience": "CFO operating review",
      "track": "REVENUE_SYSTEMS",
      "action": "REALLOCATE_IN",
      "trimSource": "Underperforming reporting backlog and low-yield experiment noise",
      "reinvestTarget": "Margin leak recovery and revenue infrastructure stabilization",
      "boardQuestion": "Which revenue lane best converts released capital into visible savings and cleaner growth math?",
      "currentPosture": "Revenue infrastructure already exposes leak recovery, experiment proof, and reporting-path uplift.",
      "recommendedMove": "Redeploy into the highest-recovery revenue lane and let lower-yield backlog work wait.",
      "savingsReleaseScore": 64,
      "redeploymentReadinessScore": 89,
      "downsideContainmentScore": 77,
      "timingScore": 84,
      "boardAlignmentScore": 90,
      "urgencyScore": 79,
      "capitalShiftMillions": 6.5,
      "headline": "Revenue is a strong redeployment target because the savings story is visible to a CFO immediately.",
      "narrative": "This is the easiest capital-rotation story to tell finance: pull effort from low-yield reporting noise and redirect into the lane that already recovers margin.",
      "nextMove": "Approve a revenue redeployment plan centered on margin leak recovery and experiment-proof reuse.",
      "companyTags": [
        "Klaviyo",
        "VWO",
        "Power BI",
        "Tableau"
      ],
      "relatedSurfaces": [
        "revenue.kineticgain.com",
        "leak.kineticgain.com",
        "martech.kineticgain.com"
      ],
      "requiredEvidence": [
        "Platform margin leak report",
        "Revenue infrastructure scorecard",
        "Benchmark waterfall"
      ]
    },
    {
      "id": "fintech-hold-until-proof-clears",
      "owner": "FinTech diligence lead",
      "audience": "Investor diligence committee",
      "track": "FINTECH",
      "action": "HOLD",
      "trimSource": "Expansion capital for adjacent FinTech wrappers",
      "reinvestTarget": "No move until reserve, KYC, and merchant proof tighten",
      "boardQuestion": "Where should the board hold capital steady until downside clusters and proof fragmentation improve?",
      "currentPosture": "Payments, KYC, treasury, and merchant review are live, but the story still clusters across multiple risk motions.",
      "recommendedMove": "Hold FinTech expansion flat until reserve, KYC, and merchant proof become easier to defend.",
      "savingsReleaseScore": 48,
      "redeploymentReadinessScore": 54,
      "downsideContainmentScore": 46,
      "timingScore": 49,
      "boardAlignmentScore": 63,
      "urgencyScore": 74,
      "capitalShiftMillions": 2.8,
      "headline": "FinTech should hold because downside clusters are outrunning the current proof quality.",
      "narrative": "The disciplined answer is not to cut the lane, but to stop feeding expansion capital into it until reserve, KYC, and merchant review evidence get tighter.",
      "nextMove": "Keep FinTech capital flat until reserve exposure, KYC refresh posture, and merchant review timing improve together.",
      "companyTags": [
        "Payments",
        "Treasury",
        "KYC",
        "Merchant risk"
      ],
      "relatedSurfaces": [
        "payments.kineticgain.com",
        "treasury.kineticgain.com",
        "merchant.kineticgain.com"
      ],
      "requiredEvidence": [
        "Investor diligence pack",
        "Treasury signal lab",
        "Merchant review posture",
        "KYC queue evidence",
        "Vendor replacement intelligence"
      ]
    },
    {
      "id": "biotech-protect-quality-system",
      "owner": "Quality systems sponsor",
      "audience": "Regulated growth committee",
      "track": "BIOTECH_DIAGNOSTICS",
      "action": "PROTECT",
      "trimSource": "Peripheral biotech presentation work",
      "reinvestTarget": "GxP, CAPA, specimen, safety, and narrative continuity",
      "boardQuestion": "Which regulated lane already behaves like one working operating system and should be defended from opportunistic cuts?",
      "currentPosture": "GxP, CAPA, specimen, safety, and narrative review now read as one coherent regulated stack.",
      "recommendedMove": "Protect the biotech quality system and only defer peripheral presentation work if savings are required.",
      "savingsReleaseScore": 39,
      "redeploymentReadinessScore": 67,
      "downsideContainmentScore": 93,
      "timingScore": 71,
      "boardAlignmentScore": 92,
      "urgencyScore": 62,
      "capitalShiftMillions": 4.2,
      "headline": "Biotech should be protected because the regulated system already reads as one defensible story.",
      "narrative": "The mistake would be harvesting short-term savings from the one regulated lane that already behaves like a mature operating layer.",
      "nextMove": "Protect the biotech quality system and approve only narrow follow-on evidence improvements.",
      "companyTags": [
        "GxP",
        "CAPA",
        "Specimen",
        "Safety"
      ],
      "relatedSurfaces": [
        "gxp.kineticgain.com",
        "capa.kineticgain.com",
        "specimen.kineticgain.com"
      ],
      "requiredEvidence": [
        "Change control board",
        "CAPA ledger",
        "Specimen custody proof",
        "Safety signal router"
      ]
    }
  ]
}