This surface packages portfolio concentration, downside clustering, and trim-versus-protect choices into board-readable routes and JSON outputs.
/allocation-lane keeps owners, audiences, directions, and next capital moves readable./concentration-risks compares concentration, downside clustering, and diversification./downside-clusters shows urgency, board confidence, and clustered downside pressure./api/payload exposes the reproducible scenario packet.{
"generatedAt": "2026-06-01T00:00:00Z",
"summary": {
"items": 6,
"averageConcentrationScore": 59,
"averageDownsideClusterScore": 51,
"averageSavingsRecoveryScore": 63,
"averageInvestmentConvictionScore": 75,
"averageDiversificationScore": 62,
"averageBoardConfidenceScore": 81,
"averageUrgencyScore": 68,
"trimTracks": 2,
"protectTracks": 2,
"capitalAtRiskMillions": 417,
"highFindings": 2,
"recommendation": "Protect the AI and biotech flagships, increase the highest-recovery revenue lane, and trim concentrated identity and procurement overlap before funding more adjacent expansion."
},
"allocationLane": [
{
"owner": "AI operating partner",
"audience": "Board strategy committee",
"direction": "PROTECT",
"allocationTheme": "Protect the AI flagship allocation",
"boardQuestion": "Which current allocation should be protected because it already compounds board-level trust?",
"allocationMove": "Protect the AI allocation from opportunistic trimming and keep it tied to governance, procurement, and board narrative outputs.",
"nextCapitalDecision": "Protect the AI flagship allocation and only trim lower-conviction adjacent work if savings are required."
},
{
"owner": "Security operating lead",
"audience": "Risk committee",
"direction": "TRIM",
"allocationTheme": "Trim duplicate identity spend",
"boardQuestion": "Where is capital concentrated in identity without a matching increase in evidence quality or remediation speed?",
"allocationMove": "Trim duplicate identity paths and preserve one integrated evidence-and-remediation sequence.",
"nextCapitalDecision": "Trim duplicate identity allocation and consolidate spend into one evidence-led remediation sequence."
},
{
"owner": "Revenue systems partner",
"audience": "Operating committee",
"direction": "INCREASE",
"allocationTheme": "Increase high-recovery revenue allocation",
"boardQuestion": "Which revenue-system allocation has the cleanest link to savings recovery and downside reduction?",
"allocationMove": "Increase the highest-recovery revenue allocation and hold the rest flat until the next board cycle.",
"nextCapitalDecision": "Increase the top revenue allocation and defer the lower-yield reporting backlog into the next operating cycle."
},
{
"owner": "FinTech diligence lead",
"audience": "Investor diligence committee",
"direction": "HOLD",
"allocationTheme": "Hold FinTech until downside clustering clears",
"boardQuestion": "Should FinTech capital be held steady until reserve, KYC, and merchant-review pressures stop clustering together?",
"allocationMove": "Hold FinTech allocation flat and resolve clustered reserve, KYC, and merchant backlog pressure before any increase.",
"nextCapitalDecision": "Hold FinTech allocation and clear clustered downside before approving new expansion capital."
},
{
"owner": "Quality systems sponsor",
"audience": "Regulated growth committee",
"direction": "PROTECT",
"allocationTheme": "Protect regulated-quality concentration that is working",
"boardQuestion": "Which regulated allocation should be protected because it already behaves like one coherent operating system?",
"allocationMove": "Protect the core regulated-quality allocation and only trim peripheral packaging work if needed.",
"nextCapitalDecision": "Protect the flagship biotech allocation and only fund narrow follow-on proof gains around the existing system."
},
{
"owner": "Procurement intelligence lead",
"audience": "Go-to-market committee",
"direction": "TRIM",
"allocationTheme": "Trim procurement overlap and recover savings",
"boardQuestion": "Where are we funding too many buyer-proof surfaces before the reuse system is fully exploited?",
"allocationMove": "Trim overlapping procurement allocation and move the savings into the highest-leverage reusable answer and proof paths.",
"nextCapitalDecision": "Trim overlapping procurement allocation and recover savings into the highest-reuse trust and answer paths."
}
],
"concentrationRisks": [
{
"owner": "AI operating partner",
"audience": "Board strategy committee",
"allocationTheme": "Protect the AI flagship allocation",
"concentrationScore": 42,
"downsideClusterScore": 29,
"diversificationScore": 74,
"companyTags": [
"IBM",
"Azure",
"OpenAI",
"MCP"
]
},
{
"owner": "Security operating lead",
"audience": "Risk committee",
"allocationTheme": "Trim duplicate identity spend",
"concentrationScore": 78,
"downsideClusterScore": 68,
"diversificationScore": 46,
"companyTags": [
"CyberArk",
"Okta",
"Entra",
"Intune"
]
},
{
"owner": "Revenue systems partner",
"audience": "Operating committee",
"allocationTheme": "Increase high-recovery revenue allocation",
"concentrationScore": 51,
"downsideClusterScore": 43,
"diversificationScore": 72,
"companyTags": [
"Klaviyo",
"VWO",
"Power BI",
"Tableau"
]
},
{
"owner": "FinTech diligence lead",
"audience": "Investor diligence committee",
"allocationTheme": "Hold FinTech until downside clustering clears",
"concentrationScore": 63,
"downsideClusterScore": 72,
"diversificationScore": 49,
"companyTags": [
"Payments",
"Treasury",
"KYC",
"Merchant risk"
]
},
{
"owner": "Quality systems sponsor",
"audience": "Regulated growth committee",
"allocationTheme": "Protect regulated-quality concentration that is working",
"concentrationScore": 47,
"downsideClusterScore": 31,
"diversificationScore": 77,
"companyTags": [
"GxP",
"CAPA",
"Specimen",
"Safety"
]
},
{
"owner": "Procurement intelligence lead",
"audience": "Go-to-market committee",
"allocationTheme": "Trim procurement overlap and recover savings",
"concentrationScore": 74,
"downsideClusterScore": 64,
"diversificationScore": 52,
"companyTags": [
"Procurement",
"Trust center",
"Questionnaires",
"RFP"
]
}
],
"downsideClusters": [
{
"owner": "AI operating partner",
"audience": "Board strategy committee",
"urgencyScore": 53,
"boardConfidenceScore": 92,
"currentPosture": "AI governance and agent readiness already behave like a flagship wedge, not an experiment line item.",
"allocationHeadline": "AI should be protected because it is already compounding trust, not merely consuming budget.",
"relatedSurfaces": [
"watsonx.kineticgain.com",
"scorecard.kineticgain.com",
"memo.kineticgain.com"
],
"requiredEvidence": [
"AI readiness scorecard",
"Governance registry",
"Board narrative memo"
]
},
{
"owner": "Security operating lead",
"audience": "Risk committee",
"urgencyScore": 82,
"boardConfidenceScore": 74,
"currentPosture": "Identity is credible, but proof is still fragmented across access review, endpoint posture, and remediation ownership.",
"allocationHeadline": "Identity has concentrated downside because multiple spend paths still resolve into one board question.",
"relatedSurfaces": [
"identity.kineticgain.com",
"protect.kineticgain.com",
"crossrisk.kineticgain.com"
],
"requiredEvidence": [
"Identity risk evidence ledger",
"App protection posture",
"Access ownership map",
"Remediation queue"
]
},
{
"owner": "Revenue systems partner",
"audience": "Operating committee",
"urgencyScore": 74,
"boardConfidenceScore": 84,
"currentPosture": "Revenue infrastructure already shows clear margin leak reduction paths, but the best lane still competes with lower-yield work.",
"allocationHeadline": "Revenue deserves increased allocation where margin recovery is already visible and measurable.",
"relatedSurfaces": [
"revenue.kineticgain.com",
"martech.kineticgain.com",
"leak.kineticgain.com"
],
"requiredEvidence": [
"Platform margin leak report",
"Revenue infrastructure scorecard",
"Board memo"
]
},
{
"owner": "FinTech diligence lead",
"audience": "Investor diligence committee",
"urgencyScore": 71,
"boardConfidenceScore": 69,
"currentPosture": "The FinTech lane is visible, but multiple downside themes still pile onto the same investor-facing story.",
"allocationHeadline": "FinTech should hold for now because the downside is still clustered more tightly than the upside is diversified.",
"relatedSurfaces": [
"payments.kineticgain.com",
"treasury.kineticgain.com",
"merchant.kineticgain.com"
],
"requiredEvidence": [
"Investor diligence pack",
"Treasury signal lab",
"Merchant review posture"
]
},
{
"owner": "Quality systems sponsor",
"audience": "Regulated growth committee",
"urgencyScore": 48,
"boardConfidenceScore": 91,
"currentPosture": "GxP, CAPA, specimen, safety, and narrative review now read as a coherent quality system rather than scattered tools.",
"allocationHeadline": "Biotech allocation should be protected because the downside is low and the flagship quality story is already coherent.",
"relatedSurfaces": [
"gxp.kineticgain.com",
"capa.kineticgain.com",
"specimen.kineticgain.com"
],
"requiredEvidence": [
"Change control board",
"CAPA ledger",
"Specimen custody console",
"Safety signal router"
]
},
{
"owner": "Procurement intelligence lead",
"audience": "Go-to-market committee",
"urgencyScore": 79,
"boardConfidenceScore": 77,
"currentPosture": "Questionnaires, trust evidence, RFP packaging, and proof-gap scoring are all live, but overlap still exists before reuse is maximized.",
"allocationHeadline": "Procurement is over-allocated in overlapping proof paths and is ready for savings recovery through consolidation.",
"relatedSurfaces": [
"procurement.kineticgain.com",
"questionnaire.kineticgain.com",
"proofgap.kineticgain.com"
],
"requiredEvidence": [
"Procurement ready OS",
"Questionnaire answer studio",
"Vendor proof gap monitor"
]
}
],
"riskMap": [
{
"code": "concentration-overhang",
"severity": "high",
"track": "IDENTITY_SECURITY",
"audience": "Risk committee",
"message": "This allocation is too concentrated relative to its diversification and should be re-ranked quickly."
},
{
"code": "concentration-overhang",
"severity": "high",
"track": "PROCUREMENT_TRUST",
"audience": "Go-to-market committee",
"message": "This allocation is too concentrated relative to its diversification and should be re-ranked quickly."
},
{
"code": "clustered-downside",
"severity": "medium",
"track": "IDENTITY_SECURITY",
"audience": "Risk committee",
"message": "Downside signals are clustering into one allocation lane, which weakens the board story if left unresolved."
},
{
"code": "clustered-downside",
"severity": "medium",
"track": "FINTECH",
"audience": "Investor diligence committee",
"message": "Downside signals are clustering into one allocation lane, which weakens the board story if left unresolved."
},
{
"code": "thin-allocation-proof",
"severity": "medium",
"track": "FINTECH",
"audience": "Investor diligence committee",
"message": "The allocation recommendation is still resting on thin proof, which weakens the committee packet."
},
{
"code": "trim-capital-now",
"severity": "medium",
"track": "IDENTITY_SECURITY",
"audience": "Risk committee",
"message": "This lane is ready for an immediate trim and savings-recovery recommendation."
},
{
"code": "trim-capital-now",
"severity": "medium",
"track": "PROCUREMENT_TRUST",
"audience": "Go-to-market committee",
"message": "This lane is ready for an immediate trim and savings-recovery recommendation."
},
{
"code": "protect-flagship",
"severity": "info",
"track": "AI_PLATFORM",
"audience": "Board strategy committee",
"message": "This allocation behaves like a flagship and should be protected from opportunistic cuts."
},
{
"code": "protect-flagship",
"severity": "info",
"track": "BIOTECH_DIAGNOSTICS",
"audience": "Regulated growth committee",
"message": "This allocation behaves like a flagship and should be protected from opportunistic cuts."
}
],
"verification": [
"Synthetic allocation-risk data only - no live capital plans, committee packets, or private financials are included.",
"Concentration, downside clustering, savings recovery, conviction, diversification, and board-confidence metrics are modeled from the sample executive-intelligence set in this repo.",
"This surface is read-only and designed to show how Kinetic Gain can package allocation-risk judgment into one board-readable operating layer.",
"Company tags and track labels are synthetic design aids rather than audited portfolio signals.",
"Every route and packet is reproducible from the included sample export."
],
"sample": [
{
"id": "ai-allocation-protect",
"owner": "AI operating partner",
"audience": "Board strategy committee",
"track": "AI_PLATFORM",
"direction": "PROTECT",
"allocationTheme": "Protect the AI flagship allocation",
"boardQuestion": "Which current allocation should be protected because it already compounds board-level trust?",
"currentPosture": "AI governance and agent readiness already behave like a flagship wedge, not an experiment line item.",
"allocationMove": "Protect the AI allocation from opportunistic trimming and keep it tied to governance, procurement, and board narrative outputs.",
"concentrationScore": 42,
"downsideClusterScore": 29,
"savingsRecoveryScore": 38,
"investmentConvictionScore": 91,
"diversificationScore": 74,
"boardConfidenceScore": 92,
"urgencyScore": 53,
"allocationHeadline": "AI should be protected because it is already compounding trust, not merely consuming budget.",
"allocationNarrative": "The allocation risk is not overspend; it is weakening the flagship lane that already converts technical work into board-readable credibility.",
"nextCapitalDecision": "Protect the AI flagship allocation and only trim lower-conviction adjacent work if savings are required.",
"companyTags": [
"IBM",
"Azure",
"OpenAI",
"MCP"
],
"relatedSurfaces": [
"watsonx.kineticgain.com",
"scorecard.kineticgain.com",
"memo.kineticgain.com"
],
"requiredEvidence": [
"AI readiness scorecard",
"Governance registry",
"Board narrative memo"
]
},
{
"id": "identity-allocation-trim",
"owner": "Security operating lead",
"audience": "Risk committee",
"track": "IDENTITY_SECURITY",
"direction": "TRIM",
"allocationTheme": "Trim duplicate identity spend",
"boardQuestion": "Where is capital concentrated in identity without a matching increase in evidence quality or remediation speed?",
"currentPosture": "Identity is credible, but proof is still fragmented across access review, endpoint posture, and remediation ownership.",
"allocationMove": "Trim duplicate identity paths and preserve one integrated evidence-and-remediation sequence.",
"concentrationScore": 78,
"downsideClusterScore": 68,
"savingsRecoveryScore": 83,
"investmentConvictionScore": 57,
"diversificationScore": 46,
"boardConfidenceScore": 74,
"urgencyScore": 82,
"allocationHeadline": "Identity has concentrated downside because multiple spend paths still resolve into one board question.",
"allocationNarrative": "The allocation case improves by reducing overlap and moving capital toward one integrated risk-evidence story rather than parallel control narratives.",
"nextCapitalDecision": "Trim duplicate identity allocation and consolidate spend into one evidence-led remediation sequence.",
"companyTags": [
"CyberArk",
"Okta",
"Entra",
"Intune"
],
"relatedSurfaces": [
"identity.kineticgain.com",
"protect.kineticgain.com",
"crossrisk.kineticgain.com"
],
"requiredEvidence": [
"Identity risk evidence ledger",
"App protection posture",
"Access ownership map",
"Remediation queue"
]
},
{
"id": "revenue-allocation-increase",
"owner": "Revenue systems partner",
"audience": "Operating committee",
"track": "REVENUE_SYSTEMS",
"direction": "INCREASE",
"allocationTheme": "Increase high-recovery revenue allocation",
"boardQuestion": "Which revenue-system allocation has the cleanest link to savings recovery and downside reduction?",
"currentPosture": "Revenue infrastructure already shows clear margin leak reduction paths, but the best lane still competes with lower-yield work.",
"allocationMove": "Increase the highest-recovery revenue allocation and hold the rest flat until the next board cycle.",
"concentrationScore": 51,
"downsideClusterScore": 43,
"savingsRecoveryScore": 88,
"investmentConvictionScore": 86,
"diversificationScore": 72,
"boardConfidenceScore": 84,
"urgencyScore": 74,
"allocationHeadline": "Revenue deserves increased allocation where margin recovery is already visible and measurable.",
"allocationNarrative": "The strongest path is to fund the revenue lane with direct savings recovery instead of spreading capital across weaker reporting upgrades.",
"nextCapitalDecision": "Increase the top revenue allocation and defer the lower-yield reporting backlog into the next operating cycle.",
"companyTags": [
"Klaviyo",
"VWO",
"Power BI",
"Tableau"
],
"relatedSurfaces": [
"revenue.kineticgain.com",
"martech.kineticgain.com",
"leak.kineticgain.com"
],
"requiredEvidence": [
"Platform margin leak report",
"Revenue infrastructure scorecard",
"Board memo"
]
},
{
"id": "fintech-allocation-hold",
"owner": "FinTech diligence lead",
"audience": "Investor diligence committee",
"track": "FINTECH",
"direction": "HOLD",
"allocationTheme": "Hold FinTech until downside clustering clears",
"boardQuestion": "Should FinTech capital be held steady until reserve, KYC, and merchant-review pressures stop clustering together?",
"currentPosture": "The FinTech lane is visible, but multiple downside themes still pile onto the same investor-facing story.",
"allocationMove": "Hold FinTech allocation flat and resolve clustered reserve, KYC, and merchant backlog pressure before any increase.",
"concentrationScore": 63,
"downsideClusterScore": 72,
"savingsRecoveryScore": 44,
"investmentConvictionScore": 61,
"diversificationScore": 49,
"boardConfidenceScore": 69,
"urgencyScore": 71,
"allocationHeadline": "FinTech should hold for now because the downside is still clustered more tightly than the upside is diversified.",
"allocationNarrative": "The best near-term move is discipline, not expansion, until the investor story improves across reserve exposure, queue speed, and review posture.",
"nextCapitalDecision": "Hold FinTech allocation and clear clustered downside before approving new expansion capital.",
"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"
]
},
{
"id": "biotech-allocation-protect",
"owner": "Quality systems sponsor",
"audience": "Regulated growth committee",
"track": "BIOTECH_DIAGNOSTICS",
"direction": "PROTECT",
"allocationTheme": "Protect regulated-quality concentration that is working",
"boardQuestion": "Which regulated allocation should be protected because it already behaves like one coherent operating system?",
"currentPosture": "GxP, CAPA, specimen, safety, and narrative review now read as a coherent quality system rather than scattered tools.",
"allocationMove": "Protect the core regulated-quality allocation and only trim peripheral packaging work if needed.",
"concentrationScore": 47,
"downsideClusterScore": 31,
"savingsRecoveryScore": 36,
"investmentConvictionScore": 89,
"diversificationScore": 77,
"boardConfidenceScore": 91,
"urgencyScore": 48,
"allocationHeadline": "Biotech allocation should be protected because the downside is low and the flagship quality story is already coherent.",
"allocationNarrative": "The mistake would be cutting the one regulated lane that already reads as a mature operating system just to harvest short-term optics.",
"nextCapitalDecision": "Protect the flagship biotech allocation and only fund narrow follow-on proof gains around the existing system.",
"companyTags": [
"GxP",
"CAPA",
"Specimen",
"Safety"
],
"relatedSurfaces": [
"gxp.kineticgain.com",
"capa.kineticgain.com",
"specimen.kineticgain.com"
],
"requiredEvidence": [
"Change control board",
"CAPA ledger",
"Specimen custody console",
"Safety signal router"
]
},
{
"id": "procurement-allocation-trim",
"owner": "Procurement intelligence lead",
"audience": "Go-to-market committee",
"track": "PROCUREMENT_TRUST",
"direction": "TRIM",
"allocationTheme": "Trim procurement overlap and recover savings",
"boardQuestion": "Where are we funding too many buyer-proof surfaces before the reuse system is fully exploited?",
"currentPosture": "Questionnaires, trust evidence, RFP packaging, and proof-gap scoring are all live, but overlap still exists before reuse is maximized.",
"allocationMove": "Trim overlapping procurement allocation and move the savings into the highest-leverage reusable answer and proof paths.",
"concentrationScore": 74,
"downsideClusterScore": 64,
"savingsRecoveryScore": 86,
"investmentConvictionScore": 67,
"diversificationScore": 52,
"boardConfidenceScore": 77,
"urgencyScore": 79,
"allocationHeadline": "Procurement is over-allocated in overlapping proof paths and is ready for savings recovery through consolidation.",
"allocationNarrative": "The best move is not adding more surfaces; it is collapsing overlap and letting reuse compound through trust, questionnaire, and vendor-proof systems.",
"nextCapitalDecision": "Trim overlapping procurement allocation and recover savings into the highest-reuse trust and answer paths.",
"companyTags": [
"Procurement",
"Trust center",
"Questionnaires",
"RFP"
],
"relatedSurfaces": [
"procurement.kineticgain.com",
"questionnaire.kineticgain.com",
"proofgap.kineticgain.com"
],
"requiredEvidence": [
"Procurement ready OS",
"Questionnaire answer studio",
"Vendor proof gap monitor"
]
}
]
}