{"id":11801,"date":"2026-11-10T12:30:00","date_gmt":"2026-11-10T12:30:00","guid":{"rendered":"https:\/\/www.cotocus.com\/blog\/?p=11801"},"modified":"2026-11-10T12:30:00","modified_gmt":"2026-11-10T12:30:00","slug":"change-reversibility-checklist","status":"publish","type":"post","link":"https:\/\/www.cotocus.com\/blog\/change-reversibility-checklist\/","title":{"rendered":"Change Reversibility Checklist: Audit Before You Ship"},"content":{"rendered":"<p>Before any change goes near production, somebody should be able to answer one question in under a minute: &#8220;If this goes wrong, how do we get back?&#8221; This checklist helps you answer it. The audit below fits a pull request, a configuration change or a planned migration, and it sorts <strong>reversible changes<\/strong> from the permanent ones so each gets the right amount of care. Print it, paste it into your change template or run through it aloud in a stand-up. It should take five to ten minutes, and it will save you a lot more than that.<\/p>\n<h2>How to use this audit<\/h2>\n<p>Go down the sections top to bottom and give every line a yes, a no or a &#8220;not sure.&#8221; A &#8220;no&#8221; is not a failure; it is a flag that tells you where to slow down. A &#8220;not sure&#8221; is a task: find out before you proceed. At the end, count what you have. Mostly yes means the change is a two-way door and can move fast. Several no answers around data, keys or customer-facing promises mean it is closer to a one-way door and deserves evidence, a second reader and a calm window.<\/p>\n<h2>Section A: Can we go back?<\/h2>\n<ul>\n<li>Is the previous version of the code, configuration and infrastructure definition stored and tagged?<\/li>\n<li>Do we know the exact steps to return to it, and have we done it recently?<\/li>\n<li>Can the return be done by anyone on the rota, not only the author?<\/li>\n<li>Does the return take minutes rather than hours?<\/li>\n<li>If the change is behind a feature flag, can the flag be turned off without a deployment?<\/li>\n<\/ul>\n<h2>Section B: Is the blast radius small?<\/h2>\n<ul>\n<li>Can the change be released to a small share of users or a single region first?<\/li>\n<li>Is there a way to stop the rollout midway if early signs look wrong?<\/li>\n<li>Does the change touch only one service, or does it ripple through several?<\/li>\n<li>Are downstream teams aware, and can they tolerate a pause?<\/li>\n<\/ul>\n<h2>Section C: What about the data?<\/h2>\n<p>Data is where reversibility most often breaks, so give this section extra attention.<\/p>\n<ul>\n<li>Does the change alter, delete or reshape stored data?<\/li>\n<li>If yes, is there a recent, verified copy that has actually been restored at least once in a test?<\/li>\n<li>Is the schema change split into compatible stages, so old and new code can both work during the transition?<\/li>\n<li>Is the destructive step, such as dropping a column or purging a table, held back until later and approved separately?<\/li>\n<li>Will anything be sent outward, such as emails, notifications or payments, that cannot be recalled?<\/li>\n<\/ul>\n<h2>Section D: Secrets, keys and access<\/h2>\n<ul>\n<li>Does the change rotate or revoke a credential that other systems depend on?<\/li>\n<li>Are the old and new credentials both valid during a defined overlap?<\/li>\n<li>Do we know every consumer of the thing being changed?<\/li>\n<li>Is there a break-glass path if access is lost?<\/li>\n<\/ul>\n<h2>Section E: Will we notice if it goes wrong?<\/h2>\n<ul>\n<li>Have we decided in advance which signals we will watch after the change?<\/li>\n<li>Do we have a clear threshold at which we pull back, written down before the release?<\/li>\n<li>Is someone assigned to watch during the observation window?<\/li>\n<li>Are we releasing at a time when people are around to respond?<\/li>\n<\/ul>\n<p>The second and third items matter a great deal. Teams that decide on the retreat condition after the change is live tend to argue themselves out of retreating. Agreeing the rule in advance, when heads are cool, removes that temptation.<\/p>\n<h2>Section F: Classify and decide<\/h2>\n<p>Now tally up. Use these rough categories.<\/p>\n<ol>\n<li><strong>Two-way door:<\/strong> yes to nearly all of sections A and B, little or no data risk. Proceed with a light review and watch the results.<\/li>\n<li><strong>Staged door:<\/strong> some reversible parts, some not. Split the change so the reversible part ships first and the sticky part waits.<\/li>\n<li><strong>One-way door:<\/strong> data loss, outward messages or credential changes with no overlap. Require a second reviewer, a rehearsal on a copy and a named time window.<\/li>\n<\/ol>\n<p>If you are unsure which category applies, assume the more cautious one until you learn otherwise. That is a cheap rule that has saved many a late night.<\/p>\n<h2>Worked example: swapping a message queue setting<\/h2>\n<p>Suppose a team wants to change how many times a failed job is retried. Section A: the old setting is in version control, so a return is a one-line revert. Section B: it applies to one service. Section C: no data changes. Section D: no credentials. Section E: the team picks the queue depth and error count as signals and agrees to revert if either keeps climbing for ten minutes. Result: a two-way door, shipped within the hour with a light review. Compare that with dropping an old reporting table, where section C lights up and the change becomes a staged door at best.<\/p>\n<h2>Second worked example: retiring an old API version<\/h2>\n<p>Now take a heavier case. A team wants to switch off version one of an internal API. Section A: the code can be restored, but clients that already migrated away may not return, so reversal is partial. Section B: the blast radius depends on unknown callers, which is a red flag. Section C: no data is deleted, but cached responses may be relied upon. Section D: an old token type is also dropped, with no overlap. Section E: error rates by caller could be watched, but only if the logging identifies callers. Result: a one-way door dressed as a tidy-up. The better plan is staged. First log who still calls the old version. Then announce a date. Then return a warning header. Then switch it off for a small group. Only after all of that, remove it for everyone. Each stage is a gentler, more reversible step toward the same destination.<\/p>\n<h2>Common reasons the audit gets skipped<\/h2>\n<p>There are three excuses worth naming. &#8220;It is only a small change&#8221; is true often enough that people stop checking, and false often enough to hurt. &#8220;We are in a hurry&#8221; is exactly when the audit matters most, since hurry makes teams skip the rehearsal of the return. &#8220;We did this last week&#8221; ignores that the system, the load and the people around it have moved. The cure is to make the audit so short that skipping it saves nothing. Keep the questions brief, put them in the tool where people already write their change descriptions, and let the answers be one word each.<\/p>\n<h2>Where this fits in your wider practice<\/h2>\n<p>An audit like this works best when it is part of a broader operating rhythm. Incident handling is one place where reversibility pays back visibly: the piece on <a href=\"https:\/\/www.cotocus.com\/blog\/transforming-incident-management-through-sre-practices-and-automation\/\">handling production incidents through reliability engineering habits<\/a> shows how teams rehearse their way back out of trouble. Security work benefits as well, and the article on <a href=\"https:\/\/www.cotocus.com\/blog\/common-devsecops-mistakes-businesses-should-avoid-early\/\">early missteps in secure delivery programmes<\/a> highlights several errors that are costly precisely because they cannot be undone later. For pipeline-level thinking, see also the guide to <a href=\"https:\/\/www.cotocus.com\/blog\/mastering-devsecops-how-to-embed-security-directly-into-your-ci-cd-pipelines\/\">building security checks into automated build and release pipelines<\/a>.<\/p>\n<h2>Getting outside help<\/h2>\n<p>If your team wants a second pair of eyes on its release process, it can be worth talking to specialists. <a href=\"https:\/\/www.devopsschool.nl\/\">DevOpsSchool Netherlands<\/a> is an Amsterdam consultancy that covers DevOps, SRE and cloud work and also provides training, so it can be a handy contact for teams across Europe wanting a structured look at how they ship.<\/p>\n<h2>Keeping the checklist alive<\/h2>\n<p>A checklist that never changes goes stale. After each incident or near miss, ask which question would have caught the problem and add it. After a period of smooth releases, ask which questions never produce interesting answers and consider trimming them. Review the list as a team once a quarter, and keep it short enough that people actually use it. Fifteen well-chosen questions beat a hundred ignored ones.<\/p>\n<p>Finally, record the outcomes. A simple log with the change, its category and what happened teaches you whether your sorting is accurate. If &#8220;two-way doors&#8221; keep turning out painful, your criteria are too generous. If &#8220;one-way doors&#8221; keep turning out trivial, you may be over-guarding, and relaxing a little will speed everyone up. The goal is calibrated caution, not maximum caution.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A six-section audit that sorts two-way changes from one-way ones, covering rollback, blast radius, data, credentials and retreat rules.<\/p>\n","protected":false},"author":37,"featured_media":11802,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[147],"tags":[],"class_list":["post-11801","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.6 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Change Reversibility Checklist: Audit Before You Ship - Cotocus<\/title>\n<meta name=\"description\" content=\"Use this change reversibility checklist to audit rollbacks, blast radius, data and credentials, and tell two-way changes from one-way ones before shipping.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.cotocus.com\/blog\/change-reversibility-checklist\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Change Reversibility Checklist: Audit Before You Ship - Cotocus\" \/>\n<meta property=\"og:description\" content=\"Use this change reversibility checklist to audit rollbacks, blast radius, data and credentials, and tell two-way changes from one-way ones before shipping.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.cotocus.com\/blog\/change-reversibility-checklist\/\" \/>\n<meta property=\"og:site_name\" content=\"Cotocus\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-10T12:30:00+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1416533-banner.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"630\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Nikhil Farooqui\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Nikhil Farooqui\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/change-reversibility-checklist\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/change-reversibility-checklist\\\/\"},\"author\":{\"name\":\"Nikhil Farooqui\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/#\\\/schema\\\/person\\\/419007bef27e8d85890550d783b96c50\"},\"headline\":\"Change Reversibility Checklist: Audit Before You Ship\",\"datePublished\":\"2026-11-10T12:30:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/change-reversibility-checklist\\\/\"},\"wordCount\":1369,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/change-reversibility-checklist\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-1416533-banner.png\",\"articleSection\":[\"DevOps\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/change-reversibility-checklist\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/change-reversibility-checklist\\\/\",\"url\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/change-reversibility-checklist\\\/\",\"name\":\"Change Reversibility Checklist: Audit Before You Ship - Cotocus\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/change-reversibility-checklist\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/change-reversibility-checklist\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-1416533-banner.png\",\"datePublished\":\"2026-11-10T12:30:00+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/#\\\/schema\\\/person\\\/419007bef27e8d85890550d783b96c50\"},\"description\":\"Use this change reversibility checklist to audit rollbacks, blast radius, data and credentials, and tell two-way changes from one-way ones before shipping.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/change-reversibility-checklist\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/change-reversibility-checklist\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/change-reversibility-checklist\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-1416533-banner.png\",\"contentUrl\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-1416533-banner.png\",\"width\":1200,\"height\":630},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/change-reversibility-checklist\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Change Reversibility Checklist: Audit Before You Ship\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/\",\"name\":\"Cotocus\",\"description\":\"Shaping Tomorrow\u2019s Tech Today\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/#\\\/schema\\\/person\\\/419007bef27e8d85890550d783b96c50\",\"name\":\"Nikhil Farooqui\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/d855702dac00a5af0405bb329101be495718d611233e52c86fe360c8fca6f6dc?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/d855702dac00a5af0405bb329101be495718d611233e52c86fe360c8fca6f6dc?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/d855702dac00a5af0405bb329101be495718d611233e52c86fe360c8fca6f6dc?s=96&d=mm&r=g\",\"caption\":\"Nikhil Farooqui\"},\"url\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/author\\\/nikhil-farooqui\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Change Reversibility Checklist: Audit Before You Ship - Cotocus","description":"Use this change reversibility checklist to audit rollbacks, blast radius, data and credentials, and tell two-way changes from one-way ones before shipping.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.cotocus.com\/blog\/change-reversibility-checklist\/","og_locale":"en_US","og_type":"article","og_title":"Change Reversibility Checklist: Audit Before You Ship - Cotocus","og_description":"Use this change reversibility checklist to audit rollbacks, blast radius, data and credentials, and tell two-way changes from one-way ones before shipping.","og_url":"https:\/\/www.cotocus.com\/blog\/change-reversibility-checklist\/","og_site_name":"Cotocus","article_published_time":"2026-11-10T12:30:00+00:00","og_image":[{"width":1200,"height":630,"url":"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1416533-banner.png","type":"image\/png"}],"author":"Nikhil Farooqui","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Nikhil Farooqui","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.cotocus.com\/blog\/change-reversibility-checklist\/#article","isPartOf":{"@id":"https:\/\/www.cotocus.com\/blog\/change-reversibility-checklist\/"},"author":{"name":"Nikhil Farooqui","@id":"https:\/\/www.cotocus.com\/blog\/#\/schema\/person\/419007bef27e8d85890550d783b96c50"},"headline":"Change Reversibility Checklist: Audit Before You Ship","datePublished":"2026-11-10T12:30:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.cotocus.com\/blog\/change-reversibility-checklist\/"},"wordCount":1369,"commentCount":0,"image":{"@id":"https:\/\/www.cotocus.com\/blog\/change-reversibility-checklist\/#primaryimage"},"thumbnailUrl":"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1416533-banner.png","articleSection":["DevOps"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.cotocus.com\/blog\/change-reversibility-checklist\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.cotocus.com\/blog\/change-reversibility-checklist\/","url":"https:\/\/www.cotocus.com\/blog\/change-reversibility-checklist\/","name":"Change Reversibility Checklist: Audit Before You Ship - Cotocus","isPartOf":{"@id":"https:\/\/www.cotocus.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.cotocus.com\/blog\/change-reversibility-checklist\/#primaryimage"},"image":{"@id":"https:\/\/www.cotocus.com\/blog\/change-reversibility-checklist\/#primaryimage"},"thumbnailUrl":"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1416533-banner.png","datePublished":"2026-11-10T12:30:00+00:00","author":{"@id":"https:\/\/www.cotocus.com\/blog\/#\/schema\/person\/419007bef27e8d85890550d783b96c50"},"description":"Use this change reversibility checklist to audit rollbacks, blast radius, data and credentials, and tell two-way changes from one-way ones before shipping.","breadcrumb":{"@id":"https:\/\/www.cotocus.com\/blog\/change-reversibility-checklist\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.cotocus.com\/blog\/change-reversibility-checklist\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.cotocus.com\/blog\/change-reversibility-checklist\/#primaryimage","url":"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1416533-banner.png","contentUrl":"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1416533-banner.png","width":1200,"height":630},{"@type":"BreadcrumbList","@id":"https:\/\/www.cotocus.com\/blog\/change-reversibility-checklist\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.cotocus.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Change Reversibility Checklist: Audit Before You Ship"}]},{"@type":"WebSite","@id":"https:\/\/www.cotocus.com\/blog\/#website","url":"https:\/\/www.cotocus.com\/blog\/","name":"Cotocus","description":"Shaping Tomorrow\u2019s Tech Today","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.cotocus.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.cotocus.com\/blog\/#\/schema\/person\/419007bef27e8d85890550d783b96c50","name":"Nikhil Farooqui","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/d855702dac00a5af0405bb329101be495718d611233e52c86fe360c8fca6f6dc?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/d855702dac00a5af0405bb329101be495718d611233e52c86fe360c8fca6f6dc?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/d855702dac00a5af0405bb329101be495718d611233e52c86fe360c8fca6f6dc?s=96&d=mm&r=g","caption":"Nikhil Farooqui"},"url":"https:\/\/www.cotocus.com\/blog\/author\/nikhil-farooqui\/"}]}},"_links":{"self":[{"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/posts\/11801","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/users\/37"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/comments?post=11801"}],"version-history":[{"count":1,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/posts\/11801\/revisions"}],"predecessor-version":[{"id":11882,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/posts\/11801\/revisions\/11882"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/media\/11802"}],"wp:attachment":[{"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/media?parent=11801"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/categories?post=11801"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/tags?post=11801"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}