{"id":14531,"date":"2025-07-01T09:00:00","date_gmt":"2025-07-01T09:00:00","guid":{"rendered":"https:\/\/codeaura.ai\/?p=14531"},"modified":"2025-07-01T22:13:17","modified_gmt":"2025-07-01T22:13:17","slug":"legacy-risk-calculators-quantifying-the-cost-of-doing-nothing","status":"publish","type":"post","link":"https:\/\/codeaura.ai\/fr\/legacy-risk-calculators-quantifying-the-cost-of-doing-nothing\/","title":{"rendered":"Legacy Risk Calculators: Quantifying the Cost of Doing Nothing"},"content":{"rendered":"<div data-elementor-type=\"wp-post\" data-elementor-id=\"14531\" class=\"elementor elementor-14531\">\n\t\t\t\t\t\t\t<div class=\"elementor-element elementor-element-22169526 e-flex e-con-boxed e-con e-parent\" data-id=\"22169526\" data-element_type=\"container\" data-settings=\"{&quot;content_width&quot;:&quot;boxed&quot;}\" data-core-v316-plus=\"true\">\n\t\t\t\t\t<div class=\"e-con-inner\">\n\t\t\t\t<div class=\"elementor-element elementor-element-468c61de elementor-widget elementor-widget-text-editor\" data-id=\"468c61de\" data-element_type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t<style>\/*! elementor - v3.17.0 - 08-11-2023 *\/\n.elementor-widget-text-editor.elementor-drop-cap-view-stacked .elementor-drop-cap{background-color:#69727d;color:#fff}.elementor-widget-text-editor.elementor-drop-cap-view-framed .elementor-drop-cap{color:#69727d;border:3px solid;background-color:transparent}.elementor-widget-text-editor:not(.elementor-drop-cap-view-default) .elementor-drop-cap{margin-top:8px}.elementor-widget-text-editor:not(.elementor-drop-cap-view-default) .elementor-drop-cap-letter{width:1em;height:1em}.elementor-widget-text-editor .elementor-drop-cap{float:left;text-align:center;line-height:1;font-size:50px}.elementor-widget-text-editor .elementor-drop-cap-letter{display:inline-block}<\/style>\t\t\t\t<h4>The Quiet Cost of Inaction<\/h4><p>When it comes to legacy modernization, the loudest costs are often the ones in a proposal\u2014the new cloud licenses, the migration consultants, the refactor budget. But the most dangerous costs? They\u2019re the ones you don\u2019t see on a line item: the quiet, compounding liabilities of doing nothing.<\/p><p>Every day an enterprise continues operating on decades-old code and brittle architecture, it accrues invisible risk. These include:<\/p><ul><li>Security vulnerabilities that can\u2019t be patched due to unsupported platforms<\/li><li>Compliance drift as new regulations outpace static legacy workflows<\/li><li>Opportunity cost from delayed digital initiatives that can\u2019t integrate with outdated systems<\/li><li>Operational downtime from unplanned incidents or mainframe lockups<\/li><li>Talent drain, as modern engineers refuse to maintain code they can\u2019t understand<\/li><\/ul><p>Unlike capital expenses, these costs don\u2019t show up in budget requests. They show up in audit findings, customer churn, missed KPIs, and long-tail technical debt that gets more expensive to unwind the longer it lingers.<\/p><p>This creates a dangerous illusion: that staying still is \u201cfree,\u201d while change is expensive. In reality, inaction is a strategy\u2014with a cost profile most organizations can\u2019t afford.<\/p><h4>Why Traditional ROI Models Fall Short<\/h4><p>Conventional ROI models treat modernization as a cost-benefit equation: upfront investment versus long-term savings. But in reality, this model breaks down\u2014because it often ignores the risk-adjusted cost of delay.<\/p><p>Here\u2019s why that matters:<\/p><p><strong>1. They Focus on Savings, Not Risk Avoidance<\/strong><\/p><p>Traditional ROI frameworks measure projected savings from reduced licensing or improved productivity. But they often leave out risk-driven costs\u2014like a $3M regulatory fine for a compliance violation that legacy systems can\u2019t prevent.<\/p><p><strong>2. They Don\u2019t Factor Technical Debt Growth<\/strong><\/p><p>Technical debt doesn\u2019t just sit idle\u2014it compounds. The longer systems go without modernization, the more brittle and complex they become. Code quality deteriorates, dependency chains deepen, and the cost of future fixes multiplies.<\/p><p><strong>3. They Underestimate Downtime Probability<\/strong><\/p><p>Many ROI models treat downtime or incidents as outliers. In reality, aging systems experience more frequent outages\u2014and each one carries operational, financial, and reputational impact. Traditional models rarely capture the full cost of a five-hour disruption in transaction processing or patient record access.<\/p><p><strong>4. They Ignore Talent Attrition and Resourcing Gaps<\/strong><\/p><p>Replacing COBOL SMEs or training new hires to maintain legacy stacks is increasingly difficult\u2014and expensive. Yet most ROI calculations don\u2019t account for the escalating cost of retaining niche skills or the impact of unplanned knowledge loss.<\/p><p><strong>5. They Miss Strategic Opportunity Cost<\/strong><\/p><p>What\u2019s the cost of a digital product delayed six months because it can\u2019t integrate with the legacy core? That lost market share or customer satisfaction hit often dwarfs the cost of the modernization itself\u2014but it\u2019s almost never modeled.<\/p><p>As a result, executives make \u201crational\u201d decisions based on incomplete models\u2014unknowingly approving delay that leads to greater financial and compliance risk down the line. This is also why organizations need a new approach: a Legacy Risk Calculator that makes the cost of inaction measurable, defensible, and actionable<\/p><h4>Introducing the Legacy Risk Calculator<\/h4><p>To make informed decisions about modernization, executives need more than ROI\u2014they need RRI: Return on Risk Investment. That\u2019s where the Legacy Risk Calculator comes in.<\/p><p>Think of it as a strategic tool that reframes modernization not as a project proposal, but as a risk-mitigation investment\u2014quantifying the financial exposure of maintaining outdated systems.<\/p><p>Here\u2019s what it does:<\/p><p><strong>1. Maps Risk Domains to Cost Metrics<\/strong><\/p><p>The calculator categorizes legacy risks across areas like:<\/p><ul><li>Compliance exposure (e.g., HIPAA, FedNow, GDPR)<\/li><li>Operational downtime likelihood<\/li><li>Security vulnerabilities<\/li><li>SME attrition and resourcing costs<\/li><li>Opportunity cost from delayed innovation<\/li><\/ul><p>Each is assigned cost weightings based on incident history, industry benchmarks, or internal data.<\/p><p><strong>2. Forecasts Risk Trajectory Over Time<\/strong><\/p><p>Risk exposure doesn\u2019t stand still. The calculator models how risks grow over 12\u201324 months if no modernization action is taken\u2014factoring in compounding factors like regulatory tightening or infrastructure aging.<\/p><p><strong>3. Ties Risk to Business Outcomes<\/strong><\/p><p>Instead of abstract percentages, outputs are shown in concrete terms: \u201cThis delay increases your 12-month exposure by $7.4M in lost productivity and compliance fines.\u201d<\/p><p><strong>4. Allows Scenario Planning<\/strong><\/p><p>Executives can model different modernization paths\u2014refactor vs. replatform vs. do nothing\u2014and compare cost curves under each scenario.<\/p><p><strong>5. Enables Board-Level Communication<\/strong><\/p><p>By turning risk into financial language, the calculator makes it easier for CIOs, CFOs, and compliance leaders to align on urgency and investment prioritization.<\/p><p>This isn\u2019t just a dashboard. It\u2019s a modernization alignment engine\u2014one that turns legacy risk into a quantified argument for action.<\/p><h4>Sector-Specific Risk Multipliers<\/h4><p>Legacy risk isn\u2019t one-size-fits-all. Different industries carry different regulatory, operational, and reputational burdens\u2014and when modernization is delayed, the cost of inaction scales differently for each.<\/p><p>Let\u2019s look at how risk compounds across key sectors:<\/p><p><strong>Banking and Financial Services<\/strong><\/p><ul><li>FedNow compliance, anti-money laundering (AML), and Basel IV updates require systems with real-time auditability and explainable logic.<\/li><li>Legacy batch systems can\u2019t meet these demands, creating exposure to fines, transaction bottlenecks, and reputational loss.<\/li><li>Multiplier: High\u2014because every delayed transaction, failed integration, or missed reporting deadline can have regulatory consequences and high-frequency financial impact.<\/li><\/ul><p><strong>Healthcare and Insurance<\/strong><\/p><ul><li>HIPAA Stage 3, CMS interoperability rules, and claims digitization require secure, shareable patient data and dynamic authorization logic.<\/li><li>COBOL-based claims engines or EMRs often lack audit trails or FHIR interoperability.<\/li><li>Multiplier: Very high\u2014since compliance violations can lead to data breach lawsuits, care delays, or license suspensions.<\/li><\/ul><p><strong>Manufacturing and Logistics<\/strong><\/p><ul><li>Legacy ERP and SCADA systems may inhibit just-in-time manufacturing, product traceability, or integration with cloud logistics platforms.<\/li><li>The cost of downtime\u2014especially in production environments\u2014can reach millions per hour.<\/li><li>Multiplier: Moderate to high\u2014especially where real-time inventory or compliance with ISO 9001\/14001 is required.<\/li><\/ul><p><strong>Public Sector and Defense<\/strong><\/p><ul><li>Legacy systems often run on unsupported hardware, expose vulnerabilities, and can\u2019t comply with zero-trust or FedRAMP security mandates.<\/li><li>Multiplier: High\u2014due to national security and data integrity concerns, especially in classified or critical infrastructure programs.<\/li><\/ul><p>These multipliers help prioritize modernization sequencing\u2014not just based on technical readiness, but based on risk-weighted urgency.<\/p><h4>Case Simulation: The $12M Risk of Waiting<\/h4><p>Let\u2019s simulate a real-world scenario using the Legacy Risk Calculator\u2014a composite example drawn from multiple financial institutions.<\/p><p><strong>Organization Profile:<\/strong><\/p><ul><li>A U.S.-based regional bank<\/li><li>28 million lines of COBOL code<\/li><li>Core systems still run on z\/OS mainframes<\/li><li>Regulatory demands include FedNow compliance, OCC audit readiness, and internal digitization initiatives<\/li><\/ul><p><strong>Current Challenge:<\/strong><\/p><p>The bank has delayed modernization for two years, opting to patch instead of replatform. Their leadership is evaluating whether to defer again, citing budget constraints.<\/p><p>Legacy Risk Calculator Output:<\/p><ul><li><strong>FedNow Noncompliance<\/strong>: $1.2M (delayed settlement, SLA breaches)<\/li><li><strong>SME Attrition &amp; Backfill<\/strong>: $950K (contractor overage, training delays)<\/li><li><strong>Security Vulnerabilities<\/strong>: $2.5M (ransomware insurance spike, patch gaps)<\/li><li><strong>Compliance Audit Findings<\/strong>: $1.7M (remediation + fines)<\/li><li><strong>Lost Productivity (DevOps)<\/strong>: $3.1M (change request lead time, manual testing)<\/li><li><strong>Opportunity Cost (Feature Lag)<\/strong>: $2.6M (digital product delays)<\/li><\/ul><p><strong>Total Annual Risk Exposure: $12.05M<\/strong><\/p><p>This figure doesn\u2019t include reputational risk, increased customer churn, or staff burnout\u2014all of which are harder to quantify but very real.<\/p><p>The takeaway is that doing nothing costs more than doing something. But because these costs are distributed across departments and budget lines, they\u2019re often missed in traditional planning.<\/p><h4>From Insight to Action: Operationalizing Risk Metrics<\/h4><p>Understanding legacy risk is only half the battle. The next step is embedding that awareness into how your organization prioritizes, funds, and governs modernization initiatives.<\/p><p>This is how enterprises can turn risk insight into modernization action:<\/p><p><strong>1. Integrate Risk Into Strategic Planning<\/strong><\/p><p>Most IT roadmaps focus on feature delivery and infrastructure cycles. Risk metrics\u2014like expected compliance penalties or tech debt growth\u2014must be built into the same models. This makes the cost of delay visible at the portfolio level.<\/p><p><strong>2. Anchor Modernization Business Cases to Risk Avoidance<\/strong><\/p><p>Instead of just promising efficiency, make the case for modernization by modeling:<\/p><ul><li>What\u2019s the financial risk if we delay?<\/li><li>What audit exposures do we mitigate with this investment?<\/li><li>How does this reduce our reliance on unscalable resources?<\/li><\/ul><p>This language resonates with CFOs and risk officers who control the budget.<\/p><p><strong>3. Link Risk to KPIs Across Departments<\/strong><\/p><p>Translate legacy risk into departmental metrics:<\/p><ul><li>For Security: \u201cPercent of high-risk systems without patch automation\u201d<\/li><li>For DevOps: \u201cChange failure rate due to undocumented legacy code\u201d<\/li><li>For Compliance: \u201cNumber of audit exceptions due to legacy constraints\u201d<\/li><\/ul><p>Now, risk becomes everyone\u2019s responsibility, not just IT\u2019s.<\/p><p><strong>4. Use AI to Keep Risk Assessments Current<\/strong><\/p><p>Legacy risk is dynamic. AI tools like Elliot can continuously scan for logic gaps, compliance drift, and architecture vulnerabilities\u2014keeping your risk model accurate even as systems evolve.<\/p><p><strong>5. Report Risk as a Metric, Not a Narrative<\/strong><\/p><p>Dashboards beat documents. Present risk exposure in executive scorecards, with trendlines, benchmarks, and \u201crisk spend\u201d curves over time. Treat it like technical debt with a dollar value and a decay curve.<\/p><p>The result: modernization no longer competes with other priorities\u2014it becomes one, backed by quantifiable risk data.<\/p><h4>Why AI-Powered Analytics Make the Difference<\/h4><p>Legacy systems aren\u2019t just complex\u2014they\u2019re opaque. Years of undocumented changes, nested dependencies, and institutional shortcuts make it nearly impossible to assess modernization risk manually. This is where AI changes the game. Platforms like CodeAura turn technical debt into measurable, navigable risk landscapes, helping enterprises take smarter, faster action. Here\u2019s how:<\/p><p><strong>1. Automated Code Comprehension<\/strong><\/p><p>AI parses COBOL, PL\/I, and mainframe systems to generate human-readable summaries of program logic, data flows, and decision conditions. This removes the bottleneck of SME reliance and surfaces hidden risks buried in unmaintained code.<\/p><p><strong>2. Continuous Risk Scanning<\/strong><\/p><p>AI monitors legacy environments in real time, flagging:<\/p><ul><li>Deprecated logic used in regulated workflows<\/li><li>Security vulnerabilities tied to outdated components<\/li><li>Modules with high change failure rates or test gaps<\/li><\/ul><p>Think of it as continuous compliance auditing for your codebase.<\/p><p><strong>3. Risk-Based Prioritization<\/strong><\/p><p>Not all legacy systems pose the same threat. AI can rank modules based on:<\/p><ul><li>Business criticality<\/li><li>Audit exposure<\/li><li>SME dependency<\/li><li>Change frequency<\/li><\/ul><p>This lets teams target the highest-risk areas first and avoid overinvesting in low-risk components.<\/p><p><strong>4. Predictive Modeling<\/strong><\/p><p>By analyzing historical outages, regulatory trends, and team performance, AI can forecast future risk curves\u2014telling you when delay becomes exponentially more costly.<\/p><p><strong>5. Board-Ready Visualization<\/strong><\/p><p>Executives don\u2019t need code. They need clarity. AI platforms provide visual dashboards that show risk exposure, modernization ROI, and regulatory gaps\u2014turning arcane systems into executive-level insights.<\/p><p>In short, AI makes it possible to quantify and manage risk across millions of lines of legacy code\u2014something no human team could do at scale or speed.<\/p><h4>The Executive Mandate: Quantify Before You Modernize<\/h4><p>For decades, modernization conversations started with ambition: \u201cLet\u2019s get to the cloud,\u201d \u201cLet\u2019s retire the mainframe,\u201d or \u201cLet\u2019s become a digital-first bank.\u201d But today, the most credible\u2014and actionable\u2014modernization strategies begin with a different principle: <strong>Quantify the risk first<\/strong>.<\/p><p>Without a clear understanding of what legacy systems are costing you\u2014financially, operationally, and reputationally\u2014building a roadmap is not possible. This is a list of actions that\u00a0top executives must do now:<\/p><p><strong>1. Mandate Risk Quantification Before Funding<\/strong><\/p><p>No major modernization effort should begin without a full risk baseline:<\/p><ul><li>What\u2019s our current cost of doing nothing?<\/li><li>Where are our top exposures?<\/li><li>What\u2019s the cost curve over 12\u201324 months if we delay?<\/li><\/ul><p>Use tools like the Legacy Risk Calculator to drive this analysis\u2014and make it a non-negotiable input for funding decisions.<\/p><p><strong>2. Align Risk Language Across the C-Suite<\/strong><\/p><p>CIOs speak in architectures. CFOs speak in costs. CROs speak in exposures. Use quantified legacy risk to align everyone around a common story: why delay is expensive, and why targeted action delivers measurable value.<\/p><p><strong>3. Communicate Modernization as Risk Mitigation<\/strong><\/p><p>Stop selling modernization as a \u201cdigital transformation journey.\u201d Start presenting it as an insurance policy against noncompliance, outage, and talent loss. You\u2019re not just building the future\u2014you\u2019re protecting the present.<\/p><p><strong>4. Track Risk as a KPI<\/strong><\/p><p>Modernization should reduce exposure. That reduction should be measurable\u2014and reported quarterly, just like revenue or uptime. Make legacy risk a tracked performance indicator.<\/p><p><strong>5. Use AI as Your Executive Lens<\/strong><\/p><p>Leverage platforms like Elliot to keep risk visible, documented, and constantly updated. You can\u2019t manage what you can\u2019t see\u2014and AI ensures you\u2019re never flying blind.<\/p><p>The mandate is clear: if you want your organization to modernize with purpose\u2014not just activity\u2014you need to ground the process in risk intelligence. Because the cost of doing nothing is no longer invisible. And now, it\u2019s no longer defensible.<\/p><p>\u00a0<\/p><p><strong>Let\u2019s Talk About Your COBOL Documentation and Modernization Needs<\/strong>\u00a0\u2014 <a href=\"https:\/\/calendly.com\/suyash-codeaura\/30min\" target=\"_blank\" rel=\"noopener\">Schedule a session with CodeAura today<\/a>.<\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t<\/div>","protected":false},"excerpt":{"rendered":"<p>Delaying modernization has a price. Learn how to quantify hidden legacy risks using AI and risk calculators to build a smarter, data-driven business case.<\/p>","protected":false},"author":1,"featured_media":14539,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_mo_disable_npp":"","footnotes":""},"categories":[61],"tags":[60],"class_list":["post-14531","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-general","tag-general","entry"],"rttpg_featured_image_url":{"full":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/07\/Legacy-Risk-Calculators-Quantifying-the-Cost-of-Doing-Nothing.jpg",1200,800,false],"landscape":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/07\/Legacy-Risk-Calculators-Quantifying-the-Cost-of-Doing-Nothing.jpg",1200,800,false],"portraits":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/07\/Legacy-Risk-Calculators-Quantifying-the-Cost-of-Doing-Nothing.jpg",1200,800,false],"thumbnail":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/07\/Legacy-Risk-Calculators-Quantifying-the-Cost-of-Doing-Nothing-150x150.jpg",150,150,true],"medium":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/07\/Legacy-Risk-Calculators-Quantifying-the-Cost-of-Doing-Nothing-300x200.jpg",300,200,true],"large":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/07\/Legacy-Risk-Calculators-Quantifying-the-Cost-of-Doing-Nothing-1024x683.jpg",1024,683,true],"1536x1536":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/07\/Legacy-Risk-Calculators-Quantifying-the-Cost-of-Doing-Nothing.jpg",1200,800,false],"2048x2048":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/07\/Legacy-Risk-Calculators-Quantifying-the-Cost-of-Doing-Nothing.jpg",1200,800,false],"trp-custom-language-flag":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/07\/Legacy-Risk-Calculators-Quantifying-the-Cost-of-Doing-Nothing-18x12.jpg",18,12,true],"post-thumbnail":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/07\/Legacy-Risk-Calculators-Quantifying-the-Cost-of-Doing-Nothing.jpg",1200,800,false],"martex-360x234-cropped":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/07\/Legacy-Risk-Calculators-Quantifying-the-Cost-of-Doing-Nothing-360x234.jpg",360,234,true],"martex-390x300-cropped":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/07\/Legacy-Risk-Calculators-Quantifying-the-Cost-of-Doing-Nothing-390x300.jpg",390,300,true],"martex-400x400-cropped":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/07\/Legacy-Risk-Calculators-Quantifying-the-Cost-of-Doing-Nothing-400x400.jpg",400,400,true],"martex-450x350-cropped":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/07\/Legacy-Risk-Calculators-Quantifying-the-Cost-of-Doing-Nothing-450x350.jpg",450,350,true],"martex-750x320-cropped":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/07\/Legacy-Risk-Calculators-Quantifying-the-Cost-of-Doing-Nothing-750x320.jpg",750,320,true],"martex-700x500-cropped":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/07\/Legacy-Risk-Calculators-Quantifying-the-Cost-of-Doing-Nothing-700x500.jpg",700,500,true],"martex-1000x600-cropped":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/07\/Legacy-Risk-Calculators-Quantifying-the-Cost-of-Doing-Nothing-1000x600.jpg",1000,600,true]},"rttpg_author":{"display_name":"suyash@codevigor.com","author_link":"https:\/\/codeaura.ai\/fr\/author\/suyashcodevigor-com\/"},"rttpg_comment":0,"rttpg_category":"<a href=\"https:\/\/codeaura.ai\/fr\/category\/general\/\" rel=\"category tag\">General<\/a>","rttpg_excerpt":"Delaying modernization has a price. Learn how to quantify hidden legacy risks using AI and risk calculators to build a smarter, data-driven business case.","_links":{"self":[{"href":"https:\/\/codeaura.ai\/fr\/wp-json\/wp\/v2\/posts\/14531","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/codeaura.ai\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/codeaura.ai\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/codeaura.ai\/fr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/codeaura.ai\/fr\/wp-json\/wp\/v2\/comments?post=14531"}],"version-history":[{"count":14,"href":"https:\/\/codeaura.ai\/fr\/wp-json\/wp\/v2\/posts\/14531\/revisions"}],"predecessor-version":[{"id":14572,"href":"https:\/\/codeaura.ai\/fr\/wp-json\/wp\/v2\/posts\/14531\/revisions\/14572"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/codeaura.ai\/fr\/wp-json\/wp\/v2\/media\/14539"}],"wp:attachment":[{"href":"https:\/\/codeaura.ai\/fr\/wp-json\/wp\/v2\/media?parent=14531"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/codeaura.ai\/fr\/wp-json\/wp\/v2\/categories?post=14531"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/codeaura.ai\/fr\/wp-json\/wp\/v2\/tags?post=14531"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}