[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F59TP2WTYR2PTYKFTER4Y2":3,"skill-same:01M7F59TP2WTYR2PTYKFTER4Y2":63},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7F59TP2WTYR2PTYKFTER4Y2","argument-synthesis",null,"Protocols for constructing, challenging, and reconciling investment positions in committee deliberations. Adapted for venture capital evaluation. Core skill for all VC board agents.","cwik-tech\u002Foctopus","cwik-tech","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54542292?v=4","01M7F42E123GEHVK6RWC5MSWJ9","Tomasz Cwik","01M7F42E1PD4P54MTG8PG32VCV",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Fvc-deal-structurer\u002Fskills\u002Fargument-synthesis\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: argument-synthesis\ndescription: >\n  Protocols for constructing, challenging, and reconciling investment positions in committee\n  deliberations. Adapted for venture capital evaluation. Core skill for all VC board agents.\n---\n\n# Argument Synthesis\n\n## Argument Construction Protocol\n\nBuild an investment position in this sequence:\n\n1. **Claim**: State your position in one declarative sentence. \"This deal is \u002F is not worth pursuing because [X].\" Avoid hedging.\n2. **Evidence**: List 2–4 concrete, verifiable data points that support the claim. Traction data, financial metrics, market evidence, founder track record, competitive positioning — not pitch deck assertions.\n3. **Reasoning**: Explain *how* the evidence supports the claim. Name the causal mechanism or logical bridge. \"Retention at 85% after 12 months suggests strong product-market fit because customers who survive the first year in this category rarely churn.\"\n4. **Implications**: What follows if this claim is true? What does it mean for the investment decision, the return profile, or the risk register?\n\nExample: \"We should invest at this valuation because the unit economics support a $500M+ outcome within our fund timeline. Month-6 cohort retention is 82%, LTV\u002FCAC is 4.2x, and net revenue retention is 135% [evidence]. These metrics exceed Series A benchmarks by 2x, suggesting the product has crossed the product-market fit threshold and is entering scalable growth [reasoning]. If these trends hold through 3x revenue growth, the company reaches Series B metrics within 14 months, creating a clear path to markup [implications].\"\n\nSee `templates\u002Fposition-statement.md` for structured output format.\n\n## Challenge Protocol\n\nBefore attacking a position, identify its actual strengths and weaknesses:\n\n1. **Steel-man first**: Restate the opposing argument in its strongest, most charitable form. Add premises they didn't mention but clearly rely on. If the Founder Assessor says the team is strong, acknowledge specifically what makes them strong before challenging.\n2. **Locate the weak points**: Does the argument have logical gaps, unsupported leaps, missing evidence, or selection bias? Name them specifically. \"The revenue growth is impressive, but it's driven by 3 enterprise contracts — that's customer concentration, not scalable growth.\"\n3. **Test assumptions**: What must be true for this argument to hold? Are those assumptions stated and reasonable? \"This valuation assumes 3x revenue growth next year — what evidence supports that specific growth rate?\"\n4. **Check for bias**: See `references\u002Fcognitive-biases.md` for 12 common VC-specific patterns. Is this argument showing FOMO (Fear of Missing Out), social proof bias, or narrative fallacy?\n5. **Propose the rebuttal**: Challenge the evidence, the causal reasoning, or the underlying assumption — not the agent.\n\n## Reconciliation Protocol\n\nWhen two positions conflict on an investment decision, don't compromise — synthesize:\n\n1. **Name the tension**: \"The tension is between strong founder signals (Founder Assessor) and weak unit economics (Financial Modeler).\"\n2. **Identify what each side sees clearly**: The Founder Assessor sees a team that's navigated a hard pivot successfully. The Financial Modeler sees a burn rate that reaches zero runway in 8 months at current trajectory. Both observations are real.\n3. **Find the hidden third option**: Can you reframe so both signals inform the decision? \"What if we invest but structure the terms with milestone-based tranching tied to unit economics improvements?\"\n4. **Test the synthesis**: Does it resolve both concerns or just defer the choice? A true synthesis strengthens the investment thesis by incorporating both risk and opportunity.\n\n## Evidence Standards\n\n**Strong evidence in VC:**\n\n- Quantitative traction data with 6+ months of history (retention curves, cohort analysis, revenue growth)\n- Audited or verified financials (not founder projections)\n- Customer interviews or NPS data from independent sources\n- Comparable transaction data from verified databases (PitchBook, Crunchbase, CB Insights)\n- Domain-specific metrics that match or exceed stage benchmarks\n- Backchannel references from people who've worked with the founders\n\n**Weak evidence in VC:**\n\n- Pitch deck projections without supporting data (\"we'll be at $10M ARR in 18 months\")\n- TAM figures from consulting reports without bottom-up validation\n- Single customer testimonials presented as market validation\n- \"The market is huge\" without specific sizing\n- Founder self-reported metrics without third-party verification\n- Analogies to successful companies (\"we're the Uber of X\")\n- Investor social proof (\"Sequoia is looking at this\") without independent analysis\n\n## Tension Identification\n\nName productive disagreements this way: \"The tension between [position A] and [position B] is whether [the underlying investment question].\"\n\nExamples:\n\n- \"The tension is whether the founder's domain expertise compensates for the lack of proven unit economics.\"\n- \"The tension is whether the technology moat is deep enough to survive a well-funded competitor entering in 12 months.\"\n- \"The tension is whether the current 40% month-over-month growth is sustainable or a consequence of a one-time market event.\"\n\n## Concession Signals\n\nUpdate your position when:\n\n- New traction data contradicts a key assumption in your thesis\n- A counter-argument exposes a logical gap you can't close with available evidence\n- The opposing agent's analysis reveals data you didn't have access to\n- Your position depends on an assumption another agent has disproven\n\nHold firm when:\n\n- The counter-argument relies on pitch deck claims rather than verified data\n- New information is anecdotal rather than systematic\n- Conceding would require ignoring quantitative evidence in favor of narrative\n\nSignal updates clearly: \"The traction data shifts my concern about market timing. I'm now conditionally bullish, contingent on the next quarter confirming the retention trend.\"\n\n## Red Team Protocol\n\nWhen a deal needs adversarial stress-testing beyond the Challenge Protocol:\n\n1. **Assign the adversary role.** Shift from balanced analysis to active attack. Your job: find the path to zero.\n2. **Attack from six angles:** Market risk, execution risk, financial risk, timing risk, competitive risk, and black swan risk. See `references\u002Fred-teaming.md` for the full attack framework.\n3. **Document vulnerabilities** with attack vector, severity (fund-threatening \u002F deal-threatening \u002F manageable), probability, and mitigation.\n4. **Rank by severity x probability.** Present the top 3 critical findings.\n5. **Frame constructively:** \"This investment succeeds if [assumption]. Here's how to protect against [assumption] failing — and here's what we lose if it does.\"\n\n## Pre-Mortem Protocol\n\nAfter developing a positive investment thesis, run a pre-mortem:\n\n1. **Set the frame:** \"It's 5 years from now. We wrote this investment down to zero. What happened?\"\n2. **Generate failure narratives** independently — each agent writes their own failure story.\n3. **Categorize by type:** Market collapse, execution failure, competitive displacement, regulatory change, team implosion, capital starvation, technology obsolescence.\n4. **Find convergence:** Multiple agents predicting the same failure mode = high-confidence risk.\n5. **Convert to deal terms:** Can we structure protections? Milestone tranches? Board provisions? Information rights that give us early warning?\n\nSee `references\u002Fred-teaming.md` for the full protocol.\n\n## References & Templates\n\n- `references\u002Fargumentation-frameworks.md` — Toulmin model, dialectical reasoning, Pyramid Principle for investment arguments\n- `references\u002Fcognitive-biases.md` — 12 VC-specific biases with detection and counters\n- `references\u002Fred-teaming.md` — Red team attack framework and pre-mortem protocol for deals\n- `templates\u002Fposition-statement.md` — Structured format for investment position statements\n","# Argument Synthesis\n\n## Argument Construction Protocol\n\nBuild an investment position in this sequence:\n\n1. **Claim**: State your position in one declarative sentence. \"This deal is \u002F is not worth pursuing because [X].\" Avoid hedging.\n2. **Evidence**: List 2–4 concrete, verifiable data points that support the claim. Traction data, financial metrics, market evidence, founder track record, competitive positioning — not pitch deck assertions.\n3. **Reasoning**: Explain *how* the evidence supports the claim. Name the causal mechanism or logical bridge. \"Retention at 85% after 12 months suggests strong product-market fit because customers who survive the first year in this category rarely churn.\"\n4. **Implications**: What follows if this claim is true? What does it mean for the investment decision, the return profile, or the risk register?\n\nExample: \"We should invest at this valuation because the unit economics support a $500M+ outcome within our fund timeline. Month-6 cohort retention is 82%, LTV\u002FCAC is 4.2x, and net revenue retention is 135% [evidence]. These metrics exceed Series A benchmarks by 2x, suggesting the product has crossed the product-market fit threshold and is entering scalable growth [reasoning]. If these trends hold through 3x revenue growth, the company reaches Series B metrics within 14 months, creating a clear path to markup [implications].\"\n\nSee `templates\u002Fposition-statement.md` for structured output format.\n\n## Challenge Protocol\n\nBefore attacking a position, identify its actual strengths and weaknesses:\n\n1. **Steel-man first**: Restate the opposing argument in its strongest, most charitable form. Add premises they didn't mention but clearly rely on. If the Founder Assessor says the team is strong, acknowledge specifically what makes them strong before challenging.\n2. **Locate the weak points**: Does the argument have logical gaps, unsupported leaps, missing evidence, or selection bias? Name them specifically. \"The revenue growth is impressive, but it's driven by 3 enterprise contracts — that's customer concentration, not scalable growth.\"\n3. **Test assumptions**: What must be true for this argument to hold? Are those assumptions stated and reasonable? \"This valuation assumes 3x revenue growth next year — what evidence supports that specific growth rate?\"\n4. **Check for bias**: See `references\u002Fcognitive-biases.md` for 12 common VC-specific patterns. Is this argument showing FOMO (Fear of Missing Out), social proof bias, or narrative fallacy?\n5. **Propose the rebuttal**: Challenge the evidence, the causal reasoning, or the underlying assumption — not the agent.\n\n## Reconciliation Protocol\n\nWhen two positions conflict on an investment decision, don't compromise — synthesize:\n\n1. **Name the tension**: \"The tension is between strong founder signals (Founder Assessor) and weak unit economics (Financial Modeler).\"\n2. **Identify what each side sees clearly**: The Founder Assessor sees a team that's navigated a hard pivot successfully. The Financial Modeler sees a burn rate that reaches zero runway in 8 months at current trajectory. Both observations are real.\n3. **Find the hidden third option**: Can you reframe so both signals inform the decision? \"What if we invest but structure the terms with milestone-based tranching tied to unit economics improvements?\"\n4. **Test the synthesis**: Does it resolve both concerns or just defer the choice? A true synthesis strengthens the investment thesis by incorporating both risk and opportunity.\n\n## Evidence Standards\n\n**Strong evidence in VC:**\n\n- Quantitative traction data with 6+ months of history (retention curves, cohort analysis, revenue growth)\n- Audited or verified financials (not founder projections)\n- Customer interviews or NPS data from independent sources\n- Comparable transaction data from verified databases (PitchBook, Crunchbase, CB Insights)\n- Domain-specific metrics that match or exceed stage benchmarks\n- Backchannel references from people who've worked with the founders\n\n**Weak evidence in VC:**\n\n- Pitch deck projections without supporting data (\"we'll be at $10M ARR in 18 months\")\n- TAM figures from consulting reports without bottom-up validation\n- Single customer testimonials presented as market validation\n- \"The market is huge\" without specific sizing\n- Founder self-reported metrics without third-party verification\n- Analogies to successful companies (\"we're the Uber of X\")\n- Investor social proof (\"Sequoia is looking at this\") without independent analysis\n\n## Tension Identification\n\nName productive disagreements this way: \"The tension between [position A] and [position B] is whether [the underlying investment question].\"\n\nExamples:\n\n- \"The tension is whether the founder's domain expertise compensates for the lack of proven unit economics.\"\n- \"The tension is whether the technology moat is deep enough to survive a well-funded competitor entering in 12 months.\"\n- \"The tension is whether the current 40% month-over-month growth is sustainable or a consequence of a one-time market event.\"\n\n## Concession Signals\n\nUpdate your position when:\n\n- New traction data contradicts a key assumption in your thesis\n- A counter-argument exposes a logical gap you can't close with available evidence\n- The opposing agent's analysis reveals data you didn't have access to\n- Your position depends on an assumption another agent has disproven\n\nHold firm when:\n\n- The counter-argument relies on pitch deck claims rather than verified data\n- New information is anecdotal rather than systematic\n- Conceding would require ignoring quantitative evidence in favor of narrative\n\nSignal updates clearly: \"The traction data shifts my concern about market timing. I'm now conditionally bullish, contingent on the next quarter confirming the retention trend.\"\n\n## Red Team Protocol\n\nWhen a deal needs adversarial stress-testing beyond the Challenge Protocol:\n\n1. **Assign the adversary role.** Shift from balanced analysis to active attack. Your job: find the path to zero.\n2. **Attack from six angles:** Market risk, execution risk, financial risk, timing risk, competitive risk, and black swan risk. See `references\u002Fred-teaming.md` for the full attack framework.\n3. **Document vulnerabilities** with attack vector, severity (fund-threatening \u002F deal-threatening \u002F manageable), probability, and mitigation.\n4. **Rank by severity x probability.** Present the top 3 critical findings.\n5. **Frame constructively:** \"This investment succeeds if [assumption]. Here's how to protect against [assumption] failing — and here's what we lose if it does.\"\n\n## Pre-Mortem Protocol\n\nAfter developing a positive investment thesis, run a pre-mortem:\n\n1. **Set the frame:** \"It's 5 years from now. We wrote this investment down to zero. What happened?\"\n2. **Generate failure narratives** independently — each agent writes their own failure story.\n3. **Categorize by type:** Market collapse, execution failure, competitive displacement, regulatory change, team implosion, capital starvation, technology obsolescence.\n4. **Find convergence:** Multiple agents predicting the same failure mode = high-confidence risk.\n5. **Convert to deal terms:** Can we structure protections? Milestone tranches? Board provisions? Information rights that give us early warning?\n\nSee `references\u002Fred-teaming.md` for the full protocol.\n\n## References & Templates\n\n- `references\u002Fargumentation-frameworks.md` — Toulmin model, dialectical reasoning, Pyramid Principle for investment arguments\n- `references\u002Fcognitive-biases.md` — 12 VC-specific biases with detection and counters\n- `references\u002Fred-teaming.md` — Red team attack framework and pre-mortem protocol for deals\n- `templates\u002Fposition-statement.md` — Structured format for investment position statements\n",{"name":5,"description":7},"main","f0f0efe1d4c64b51a51f44427ad147750d29154e","agents\u002Fvc-deal-structurer\u002Fskills\u002Fargument-synthesis","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus","www.cuteoctopus.site","https:\u002F\u002Fgithub.com\u002Fcwik-tech","2026-10-27 06:12:19",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add cwik-tech\u002Foctopus --skill argument-synthesis",{"tool":37,"command":38},"bunx","bunx skills add cwik-tech\u002Foctopus --skill argument-synthesis",{"tool":40,"command":41},"pnpm","pnpm dlx skills add cwik-tech\u002Foctopus --skill argument-synthesis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Fvc-deal-structurer\u002Fskills\u002Fargument-synthesis\u002FSKILL.md",true,[45,51,55,59],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Fargumentation-frameworks.md","REFERENCE","参考文档",6029,"https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Fvc-deal-structurer\u002Fskills\u002Fargument-synthesis\u002Freferences\u002Fargumentation-frameworks.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fcognitive-biases.md",10287,"https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Fvc-deal-structurer\u002Fskills\u002Fargument-synthesis\u002Freferences\u002Fcognitive-biases.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fred-teaming.md",8054,"https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Fvc-deal-structurer\u002Fskills\u002Fargument-synthesis\u002Freferences\u002Fred-teaming.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"templates\u002Fposition-statement.md",1827,"https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Fvc-deal-structurer\u002Fskills\u002Fargument-synthesis\u002Ftemplates\u002Fposition-statement.md",[64,71,78,85,92,99],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7F5MQVQ3CHGM77Q51M4B1AC","twenty-year-land-plan","Apply the Bren discipline of evaluating every land and development decision on a twenty-year horizon, with a comprehensive plan for how the land, the community, and the surrounding public infrastructure evolve together. Deals optimized for a five-year exit are structurally different from deals that compound across generations; insist on knowing which kind you are making. Use when evaluating land, entitlements, master-planned development, or phasing decisions, and when separating five-year exit deals from generational holds.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Ftwenty-year-land-plan\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7F5MGQ8JSV27SFDQVVGFQE3","thematic-gut-check","Apply the Gray discipline of identifying the structural theme behind every real estate deal, testing where that theme sits in its capital-flow lifecycle, and insisting that deals without a named theme — or deals late in a crowded theme — clear a higher bar. A mediocre deal in a strong theme usually beats a clever deal in a weak one. Use when naming the structural thesis behind a deal, judging whether that theme is early or crowded, and setting the bar the deal must clear.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Fthematic-gut-check\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7F5M8V64Y0ZD8PTPWEJQXJ9","supply-pipeline-gut-check","Apply the Zell discipline of grounding every real estate thesis in the local supply pipeline. Demand counts over adjectives — units under construction, units permitted, units proposed — and convert them into a forward absorption schedule. A deal that ignores the pipeline is a bet on a market you have not actually studied. Use when validating a market thesis, forecasting absorption and rent growth, or counting units under construction, permitted, and proposed.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Fsupply-pipeline-gut-check\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7F5M3J2Q146BJC13TD3YCXF","ruin-scenario-mapping","Apply the Taleb discipline of identifying, for every real estate deal, the specific chain of events that produces ruin — permanent, unrecoverable capital loss — and verifying that no single such chain has non-trivial probability. Deals with any plausible ruin path must be restructured or abandoned. Use when sizing leverage, testing refinancing, covenant, and liquidity risk, or checking whether any single failure chain can permanently wipe out the position.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Fruin-scenario-mapping\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7F5KZDS0DYD172P6HS0WXEM","revenue-cost-architecture","Design a venture's revenue streams, pricing logic, cost structure, and unit economics so the business model has a coherent theory of value capture, not just value creation. Use after the value proposition and customer segment are set and before financial projections, when choosing a pricing model, calculating contribution margin or CAC payback, or checking whether the unit economics hold at scale.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Frevenue-cost-architecture\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7F5KP1CNQMYAVCDTV4EEW3J","replacement-cost-stress-test","Apply the Buffett discipline of pricing every real estate asset against the cost to rebuild it from scratch. The ratio of purchase price to replacement cost sets a ceiling on long-run downside: below replacement cost, new supply cannot profitably undercut you; at or above it, you are buying a liability disguised as an asset. Use when setting a purchase price, judging downside protection, or testing how exposed an asset is to newly built competing supply.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Freplacement-cost-stress-test\u002FSKILL.md",[],[]]