{"id":8525,"date":"2026-11-18T13:10:00","date_gmt":"2026-11-18T13:10:00","guid":{"rendered":"https:\/\/www.devopsconsulting.in\/blog\/?p=8525"},"modified":"2026-11-18T13:10:00","modified_gmt":"2026-11-18T13:10:00","slug":"seven-steps-review-failed-release-client-engagement","status":"publish","type":"post","link":"https:\/\/www.devopsconsulting.in\/blog\/seven-steps-review-failed-release-client-engagement\/","title":{"rendered":"How to Review a Failed Release With a Client, in Seven Steps"},"content":{"rendered":"<p>You are three weeks into a DevOps consulting engagement. A release that the client&#8217;s team and yours prepared together goes out on Tuesday and rolls back on Tuesday afternoon. Now there is a room full of people wondering whether this is the consultants&#8217; fault, the client&#8217;s fault or the tool&#8217;s. Handled badly, a rollback like this burns months of goodwill. Handled well, it becomes the most useful session of the engagement. This guide sets out seven steps for running a blameless review of a failed release, written for consultants and for the client leads who work with them.<\/p>\n<h2>Step 1: Agree the ground rules before anyone talks about causes<\/h2>\n<p>Open the review with two sentences everybody can hear: the goal is to find what in the delivery process allowed this, and the output is one change to the pipeline or the way we work. Say also what the review is not: it is not a performance discussion, a contract conversation or a hunt for an owner of fault. Consultants have a particular responsibility here, since the outsiders in a room tend to set the tone. If you treat your own team&#8217;s work with the same neutral curiosity as the client&#8217;s, others follow.<\/p>\n<h2>Step 2: Build the timeline from records<\/h2>\n<p>Before the meeting, collect the pipeline run history, deployment logs, change tickets, chat threads and monitoring graphs for the window. Lay the events out in order with timestamps, and mark where a person made a decision and what information they had then. Memory is unreliable under stress and tends to reorder events so the narrator looks sensible. Records do not.<\/p>\n<p>A typical example: a configuration value for a payment service was promoted from staging to production with the staging endpoint inside it. The timeline shows the value was copied in a hurry during a late change, the pipeline did not compare it to the production profile, and the smoke test checked only that the service started, not which backend it called.<\/p>\n<p>One practical tip for this stage: ask the client for read access to their pipeline history ahead of the session, and agree who will screen-share it. Nothing slows a review like twenty minutes spent hunting for the right run, and nothing sours it faster than a debate over which log is the authoritative one. If two sources disagree, note the disagreement as a finding of its own, because unclear records are a process gap that will bite again during the next incident.<\/p>\n<h2>Step 3: Walk the timeline and ask what each person could see<\/h2>\n<p>For each decision on the timeline, ask what was visible at that moment. The engineer who copied the value saw a diff of two files with two hundred lines. The reviewer saw only the changed lines and none of the surrounding settings. The smoke test returned green. Every one of those people acted sensibly given their view, and that is the finding: the process presented them with a picture that hid the problem.<\/p>\n<p>This step is where blame quietly dissolves. When the group sees that a thoughtful person would have made the same call from the same screen, the conversation moves naturally from &#8220;who&#8221; to &#8220;why was the screen like that&#8221;.<\/p>\n<h2>Step 4: Name the gap in plain words<\/h2>\n<p>State the cause as a condition of the system. In our example: &#8220;Environment-specific values live in the same file as shared values, and nothing checks that a promoted artefact points only at its target environment.&#8221; Avoid words like &#8220;forgot&#8221;, &#8220;missed&#8221; and &#8220;should have&#8221;. Keep it to one or two sentences. If the group produces five causes, look for the one that, if fixed, would have stopped the others from mattering.<\/p>\n<p>If security-related behaviour was part of the failure, it can help to refer back to a shared reference on how security fits into pipelines. The guide on <a href=\"https:\/\/www.devopsconsulting.in\/blog\/devsecops-consulting-guide-how-to-integrate-security-into-devops-pipelines\/\">building security into DevOps pipelines<\/a> offers a useful frame for deciding where a guard check should live, and clients often appreciate having a neutral document to point at.<\/p>\n<h2>Step 5: Choose one change and make it small<\/h2>\n<p>Resist the long list. Pick the change that closes the gap with the least effort, and phrase it as a pipeline step. For our example, that could be a policy check which fails any production deploy whose artefact contains a non-production hostname. It takes an afternoon to write, runs in seconds, and is independent of anybody&#8217;s attention on a busy day.<\/p>\n<ul>\n<li>It is specific: it names the check and where it runs.<\/li>\n<li>It is verifiable: a failing test proves it works.<\/li>\n<li>It does not rely on someone being more careful.<\/li>\n<li>It has an owner and a date.<\/li>\n<\/ul>\n<p>Park the remaining ideas in a backlog. They are useful, but a review that leaves with eight actions usually delivers none of them.<\/p>\n<h2>Step 6: Agree how the client hears about it<\/h2>\n<p>This step is easy to skip and costly to neglect. Decide together what the summary says, who sends it and to whom. Keep it short: what happened, what allowed it, what is changing, when. Use the same neutral wording you used in the room. A client&#8217;s leadership will read it for signals about how the engagement is run, and a calm, specific summary reassures them more than reassurance does.<\/p>\n<p>It also helps to connect the change to the engagement&#8217;s wider plan. If your statement of work follows a pattern like the one described in <a href=\"https:\/\/www.devopsconsulting.in\/blog\/the-blueprint-for-a-successful-devops-consulting-engagement-from-assessment-to-enablement\/\">a blueprint moving from assessment to enablement<\/a>, note where in that sequence the new check belongs, so the client sees it as part of the roadmap and not a patch.<\/p>\n<h2>Step 7: Close the loop<\/h2>\n<p>On the agreed date, check whether the change shipped, and say so in the next status update, whether or not it did. If it did not, ask what got in the way, as another process question. Then, a month later, glance back to see whether the same kind of failure has recurred. A review without a follow-up is a conversation; with one, it is a control.<\/p>\n<h2>A short word on other industries<\/h2>\n<p>Consultants sometimes feel this approach is specific to software. It is not. Any service with repeatable steps can use it. A restaurant reviewing a spoiled prep batch looks at storage temperatures and timing, not at the cook. If you are curious how a different industry packages its services online, <a href=\"https:\/\/findmyresto.com\/\">FindMyResto<\/a> is a restaurant discovery website where visitors search, see menus, get directions and book tables, and where owners can create listings. The reminder it offers is simple: wherever there are steps, there are places for a gap to hide.<\/p>\n<h2>Common traps to avoid<\/h2>\n<ul>\n<li>Letting the review become a vendor-versus-client negotiation.<\/li>\n<li>Allowing a senior voice to propose the cause in the first five minutes, which anchors everyone.<\/li>\n<li>Ending with a vague commitment such as &#8220;improve testing&#8221;.<\/li>\n<li>Skipping the review because the rollback was quick and nobody was hurt.<\/li>\n<\/ul>\n<p>That last trap deserves emphasis. A fast, painless rollback is exactly the occasion when a review is cheapest and the memories are freshest.<\/p>\n<h2>The practical takeaway<\/h2>\n<p>Seven steps, one change. Set the rules, build the timeline, trace what each person could see, name the gap, choose a small fix, tell the client plainly and follow up. Done consistently, this turns a failed Tuesday release into the moment the client&#8217;s team decides your engagement is worth extending, because they saw how problems get handled.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A failed release in the middle of a consulting engagement is awkward. Here are seven practical steps for a review that finds the cause and ends with one change.<\/p>\n","protected":false},"author":8,"featured_media":8526,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5838],"tags":[],"class_list":["post-8525","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devsecops"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.7 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>How to Review a Failed Release With a Client, in Seven Steps - DevOps Consulting<\/title>\n<meta name=\"description\" content=\"Seven practical steps for DevOps consultants to review a failed release with a client: gather facts, trace the gap, agree one pipeline change, and follow up.\" \/>\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.devopsconsulting.in\/blog\/seven-steps-review-failed-release-client-engagement\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How to Review a Failed Release With a Client, in Seven Steps - DevOps Consulting\" \/>\n<meta property=\"og:description\" content=\"Seven practical steps for DevOps consultants to review a failed release with a client: gather facts, trace the gap, agree one pipeline change, and follow up.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.devopsconsulting.in\/blog\/seven-steps-review-failed-release-client-engagement\/\" \/>\n<meta property=\"og:site_name\" content=\"DevOps Consulting\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-18T13:10:00+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.devopsconsulting.in\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-3222903-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=\"Kabir Malhotra\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Kabir Malhotra\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/seven-steps-review-failed-release-client-engagement\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/seven-steps-review-failed-release-client-engagement\\\/\"},\"author\":{\"name\":\"Kabir Malhotra\",\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/#\\\/schema\\\/person\\\/4cff11af81c93e658f55af13b267f093\"},\"headline\":\"How to Review a Failed Release With a Client, in Seven Steps\",\"datePublished\":\"2026-11-18T13:10:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/seven-steps-review-failed-release-client-engagement\\\/\"},\"wordCount\":1241,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/seven-steps-review-failed-release-client-engagement\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-3222903-banner.png\",\"articleSection\":[\"DevSecOps\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/seven-steps-review-failed-release-client-engagement\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/seven-steps-review-failed-release-client-engagement\\\/\",\"url\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/seven-steps-review-failed-release-client-engagement\\\/\",\"name\":\"How to Review a Failed Release With a Client, in Seven Steps - DevOps Consulting\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/seven-steps-review-failed-release-client-engagement\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/seven-steps-review-failed-release-client-engagement\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-3222903-banner.png\",\"datePublished\":\"2026-11-18T13:10:00+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/#\\\/schema\\\/person\\\/4cff11af81c93e658f55af13b267f093\"},\"description\":\"Seven practical steps for DevOps consultants to review a failed release with a client: gather facts, trace the gap, agree one pipeline change, and follow up.\",\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/seven-steps-review-failed-release-client-engagement\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/seven-steps-review-failed-release-client-engagement\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-3222903-banner.png\",\"contentUrl\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-3222903-banner.png\",\"width\":1200,\"height\":630},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/\",\"name\":\"DevOps Consulting\",\"description\":\"DevOps Consulting | SRE Consulting | DevSecOps Consulting | MLOps Consulting\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/#\\\/schema\\\/person\\\/4cff11af81c93e658f55af13b267f093\",\"name\":\"Kabir Malhotra\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/d77044c5c70611f0b6d1131a1758057dcb873aae1740ec1c40a13a6428461d0b?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/d77044c5c70611f0b6d1131a1758057dcb873aae1740ec1c40a13a6428461d0b?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/d77044c5c70611f0b6d1131a1758057dcb873aae1740ec1c40a13a6428461d0b?s=96&d=mm&r=g\",\"caption\":\"Kabir Malhotra\"},\"url\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/author\\\/kabir-malhotra\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"How to Review a Failed Release With a Client, in Seven Steps - DevOps Consulting","description":"Seven practical steps for DevOps consultants to review a failed release with a client: gather facts, trace the gap, agree one pipeline change, and follow up.","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.devopsconsulting.in\/blog\/seven-steps-review-failed-release-client-engagement\/","og_locale":"en_US","og_type":"article","og_title":"How to Review a Failed Release With a Client, in Seven Steps - DevOps Consulting","og_description":"Seven practical steps for DevOps consultants to review a failed release with a client: gather facts, trace the gap, agree one pipeline change, and follow up.","og_url":"https:\/\/www.devopsconsulting.in\/blog\/seven-steps-review-failed-release-client-engagement\/","og_site_name":"DevOps Consulting","article_published_time":"2026-11-18T13:10:00+00:00","og_image":[{"width":1200,"height":630,"url":"https:\/\/www.devopsconsulting.in\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-3222903-banner.png","type":"image\/png"}],"author":"Kabir Malhotra","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Kabir Malhotra","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.devopsconsulting.in\/blog\/seven-steps-review-failed-release-client-engagement\/#article","isPartOf":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/seven-steps-review-failed-release-client-engagement\/"},"author":{"name":"Kabir Malhotra","@id":"https:\/\/www.devopsconsulting.in\/blog\/#\/schema\/person\/4cff11af81c93e658f55af13b267f093"},"headline":"How to Review a Failed Release With a Client, in Seven Steps","datePublished":"2026-11-18T13:10:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/seven-steps-review-failed-release-client-engagement\/"},"wordCount":1241,"commentCount":0,"image":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/seven-steps-review-failed-release-client-engagement\/#primaryimage"},"thumbnailUrl":"https:\/\/www.devopsconsulting.in\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-3222903-banner.png","articleSection":["DevSecOps"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.devopsconsulting.in\/blog\/seven-steps-review-failed-release-client-engagement\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.devopsconsulting.in\/blog\/seven-steps-review-failed-release-client-engagement\/","url":"https:\/\/www.devopsconsulting.in\/blog\/seven-steps-review-failed-release-client-engagement\/","name":"How to Review a Failed Release With a Client, in Seven Steps - DevOps Consulting","isPartOf":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/seven-steps-review-failed-release-client-engagement\/#primaryimage"},"image":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/seven-steps-review-failed-release-client-engagement\/#primaryimage"},"thumbnailUrl":"https:\/\/www.devopsconsulting.in\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-3222903-banner.png","datePublished":"2026-11-18T13:10:00+00:00","author":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/#\/schema\/person\/4cff11af81c93e658f55af13b267f093"},"description":"Seven practical steps for DevOps consultants to review a failed release with a client: gather facts, trace the gap, agree one pipeline change, and follow up.","inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.devopsconsulting.in\/blog\/seven-steps-review-failed-release-client-engagement\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.devopsconsulting.in\/blog\/seven-steps-review-failed-release-client-engagement\/#primaryimage","url":"https:\/\/www.devopsconsulting.in\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-3222903-banner.png","contentUrl":"https:\/\/www.devopsconsulting.in\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-3222903-banner.png","width":1200,"height":630},{"@type":"WebSite","@id":"https:\/\/www.devopsconsulting.in\/blog\/#website","url":"https:\/\/www.devopsconsulting.in\/blog\/","name":"DevOps Consulting","description":"DevOps Consulting | SRE Consulting | DevSecOps Consulting | MLOps Consulting","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.devopsconsulting.in\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.devopsconsulting.in\/blog\/#\/schema\/person\/4cff11af81c93e658f55af13b267f093","name":"Kabir Malhotra","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/d77044c5c70611f0b6d1131a1758057dcb873aae1740ec1c40a13a6428461d0b?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/d77044c5c70611f0b6d1131a1758057dcb873aae1740ec1c40a13a6428461d0b?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/d77044c5c70611f0b6d1131a1758057dcb873aae1740ec1c40a13a6428461d0b?s=96&d=mm&r=g","caption":"Kabir Malhotra"},"url":"https:\/\/www.devopsconsulting.in\/blog\/author\/kabir-malhotra\/"}]}},"_links":{"self":[{"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/posts\/8525","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/comments?post=8525"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/posts\/8525\/revisions"}],"predecessor-version":[{"id":8643,"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/posts\/8525\/revisions\/8643"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/media\/8526"}],"wp:attachment":[{"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/media?parent=8525"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/categories?post=8525"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/tags?post=8525"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}