{"id":109019,"date":"2026-11-10T01:11:59","date_gmt":"2026-11-10T01:11:59","guid":{"rendered":"https:\/\/relaxingstory.com\/?p=109019"},"modified":"2026-11-10T01:11:59","modified_gmt":"2026-11-10T01:11:59","slug":"after-twelve-years-of-keeping-my-companys-billion-dollar-operations-from-collapsing-the-new-vice-president-threatened-to-take-away-my-200000-bonus-so-i-answered-with-one-word-that-brought-6","status":"publish","type":"post","link":"https:\/\/relaxingstory.com\/?p=109019","title":{"rendered":"After Twelve Years of Keeping My Company’s Billion-Dollar Operations From Collapsing, the New Vice President Threatened to Take Away My $200,000 Bonus\u2014So I Answered With One Word That Brought the Entire Executive Team to My Office Before Sunrise"},"content":{"rendered":"
\n
At 5:37 a.m., I was staring at a red deployment failure on three monitors while my phone vibrated for the third time.<\/span><\/div>\n
\n

Infrastructure was calling again.<\/p>\n

I hadn’t slept properly in four days.<\/p>\n

The company’s payment platform was experiencing intermittent failures, a database migration was approaching its deadline, and two engineering teams were waiting for my approval before proceeding with a recovery plan.<\/p>\n

I was forty-six years old, had worked at Northstar Commerce for twelve years, and had become the person everyone called when something important broke.<\/p>\n

When payments stopped processing, they called me.<\/p>\n

When a deployment threatened to corrupt customer data, they called me.<\/p>\n

When a vendor’s software update unexpectedly overloaded our servers, they called me.<\/p>\n

And when the company’s executives wanted to announce another record-breaking quarter, they rarely mentioned my name.<\/p>\n

I was Martin Hayes, Director of Platform Reliability.<\/p>\n

My department maintained the infrastructure that supported Northstar’s entire online business. At peak periods, our systems processed billions of dollars in annual transactions across multiple markets.<\/p>\n

The company had grown from a relatively small digital retailer into a major international commerce platform.<\/p>\n

I had been there through almost every stage.<\/p>\n

I helped build the original infrastructure, designed the systems that supported our expansion, and led the engineering response during three major outages.<\/p>\n

I had missed birthdays, canceled vacations, and spent more weekends in the office than I cared to count.<\/p>\n

I never expected executives to applaud me every time something worked.<\/p>\n

In infrastructure engineering, success is often invisible.<\/p>\n

If customers can place orders, payments clear, and the website remains online, nobody asks who spent the night making sure it happened.<\/p>\n

But I did expect the company to respect the people responsible for keeping its most important systems operational.<\/p>\n

That expectation began to disappear when Todd Mercer became our new Vice President of Product.<\/p>\n

Todd was thirty-nine, ambitious, and exceptionally skilled at presenting simple solutions to complicated problems.<\/p>\n

He had arrived six months earlier with an impressive r\u00e9sum\u00e9 and a promise to make Northstar more efficient.<\/p>\n

During his first company-wide meeting, he announced that our engineering organization had become too expensive.<\/p>\n

“We’re spending too much money maintaining systems that customers never see,” he said. “We need to stop treating infrastructure as an untouchable department.”<\/p>\n

The executives applauded.<\/p>\n

I sat near the back of the conference room and looked at the presentation.<\/p>\n

Todd’s proposal included consolidating several production environments, reducing redundant capacity, replacing experienced support engineers with cheaper outsourced teams, and moving critical services onto a less expensive hosting configuration.<\/p>\n

Some of the ideas were reasonable.<\/p>\n

Others were dangerous.<\/p>\n

The problem wasn’t that Todd wanted to reduce costs.<\/p>\n

The problem was that he wanted to reduce costs without understanding what those expenses protected.<\/p>\n

Our payment infrastructure wasn’t an ordinary application that could simply be restarted if something went wrong.<\/p>\n

It supported transactions across different markets, financial institutions, inventory systems, fraud detection services, and customer accounts.<\/p>\n

Redundant systems weren’t unnecessary luxuries.<\/p>\n

They were the reason a single hardware failure didn’t become a company-wide disaster.<\/p>\n

I requested a technical review.<\/p>\n

Todd rejected it.<\/p>\n

“We don’t need another six-week engineering study,” he said. “We need results.”<\/p>\n

I explained that the proposed consolidation would eliminate several independent recovery paths.<\/p>\n

He smiled.<\/p>\n

“Martin, I appreciate your experience, but we can’t let people who built the old system prevent us from building the next one.”<\/p>\n

That sentence told me everything I needed to know.<\/p>\n

He didn’t see me as the person responsible for protecting the company’s infrastructure.<\/p>\n

He saw me as an obstacle to his transformation plan.<\/p>\n

Still, I tried to work with him.<\/p>\n

I prepared a technical assessment showing the likely consequences of his proposed changes.<\/p>\n

It included estimated recovery times, capacity limits, dependency diagrams, and historical incident data.<\/p>\n

I also presented three alternatives that would reduce operating expenses without eliminating critical protections.<\/p>\n

Todd barely looked at the document.<\/p>\n

“This is exactly what I’m talking about,” he said during the next review. “Every solution from your department involves spending more money.”<\/p>\n

“Not every solution,” I replied. “But every safe solution needs to account for the actual failure scenarios.”<\/p>\n

He leaned forward.<\/p>\n

“You’re making this personal.”<\/p>\n

“I’m making it technical.”<\/p>\n

He closed his laptop.<\/p>\n

“Then perhaps you should remember that product strategy isn’t your responsibility.”<\/p>\n

I returned to my office without responding.<\/p>\n

For the next several weeks, Todd pushed the plan forward.<\/p>\n

He began asking for weekly savings reports and instructed managers to identify positions that could be eliminated.<\/p>\n

He also started questioning the performance bonuses of employees who challenged his decisions.<\/p>\n

My own bonus was worth $200,000.<\/p>\n

It wasn’t guaranteed simply because I wanted it. It was tied to documented performance objectives, operational reliability, and the terms of my compensation agreement.<\/p>\n

I had earned it through twelve years of difficult work.<\/p>\n

Todd knew that.<\/p>\n

He also knew I had raised concerns about his plan.<\/p>\n

One Thursday evening, I received an invitation to a meeting titled “Operational Efficiency Alignment.”<\/p>\n

The attendees included Todd, two finance executives, the head of infrastructure, and me.<\/p>\n

Todd opened the meeting by displaying a spreadsheet.<\/p>\n

He had identified several systems that he believed could be consolidated within thirty days.<\/p>\n

One of them handled payment authorization recovery.<\/p>\n

I immediately recognized the problem.<\/p>\n

“That service can’t be consolidated in the way you’ve described,” I said.<\/p>\n

Todd looked at me.<\/p>\n

“Why not?”<\/p>\n

“Because the two environments are designed to operate independently. If we merge them without redesigning the recovery process, a failure in one shared dependency could affect both.”<\/p>\n

He pointed at the projected savings.<\/p>\n

“You’re telling me we should spend another four million dollars maintaining duplication?”<\/p>\n

“I’m telling you that the proposed savings don’t account for the potential cost of an extended payment outage.”<\/p>\n

“How likely is that?”<\/p>\n

I opened the incident history.<\/p>\n

“We’ve had three events in the last eighteen months where independent recovery prevented a wider outage. If this design had been in place, at least one of those incidents could have affected every payment region.”<\/p>\n

Todd shook his head.<\/p>\n

“That’s hypothetical.”<\/p>\n

“No. The incidents are documented. The failure paths are documented. The difference is that you’re choosing to ignore them.”<\/p>\n

The room became quiet.<\/p>\n

Todd closed the spreadsheet.<\/p>\n

“Martin, I don’t think you understand how this company makes decisions.”<\/p>\n

I looked at him.<\/p>\n

“I understand exactly how it makes decisions. That’s why I’m documenting my objections.”<\/p>\n

He ended the meeting early.<\/p>\n

Two days later, my manager told me Todd had complained about my attitude.<\/p>\n

I asked whether the technical concerns were being reviewed.<\/p>\n

He hesitated.<\/p>\n

“Martin, I agree with you. But Todd has executive support. Be careful about how you approach this.”<\/p>\n

I nodded.<\/p>\n

I had spent twelve years learning how to keep systems alive.<\/p>\n

I knew how to monitor failures, isolate dependencies, and prevent cascading incidents.<\/p>\n

But I was beginning to understand that protecting a company from its own decisions could be more difficult than protecting it from a technical failure.<\/p>\n

Then came the message.<\/p>\n

At 12:08 a.m. on Monday, my phone vibrated beside my keyboard.<\/p>\n

I had been reviewing a deployment failure when Todd’s name appeared.<\/p>\n

His message read:<\/p>\n

“Lose the attitude or lose your $200K bonus.”<\/p>\n

I read it once.<\/p>\n

Then again.<\/p>\n

I didn’t respond.<\/p>\n

I opened my compensation agreement and reviewed the bonus conditions.<\/p>\n

I opened the company’s change-management policy.<\/p>\n

Then I opened the internal deployment governance system.<\/p>\n

There was a formal process for approving production changes that could materially affect critical infrastructure.<\/p>\n

It required a technical owner, a documented risk assessment, an identified rollback procedure, and approval from the designated reliability authority.<\/p>\n

I was that authority for the payment platform.<\/p>\n

Todd’s proposed consolidation had been scheduled for a production change window the following morning.<\/p>\n

The technical review was incomplete.<\/p>\n

The rollback procedure had not been tested.<\/p>\n

The independent recovery environment was scheduled for decommissioning before the replacement system had passed its validation requirements.<\/p>\n

The deployment request was still marked as pending.<\/p>\n

I had warned Todd about these problems in writing.<\/p>\n

I had submitted the risk assessment.<\/p>\n

I had requested additional testing.<\/p>\n

The requests had been ignored.<\/p>\n

I opened the change record.<\/p>\n

There was a large text field asking for the final authorization status.<\/p>\n

I typed one word.<\/p>\n

REJECTED.<\/p>\n

Then I selected the documented reasons:<\/p>\n

    \n
  • \n
    \n
    \n

    Unverified recovery architecture.<\/p>\n<\/div>\n<\/div>\n<\/li>\n

  • \n
    \n
    \n

    Incomplete failure-isolation testing.<\/p>\n<\/div>\n<\/div>\n<\/li>\n

  • \n
    \n
    \n

    No validated rollback procedure.<\/p>\n<\/div>\n<\/div>\n<\/li>\n

  • \n
    \n
    \n

    Critical dependency consolidation without approved risk acceptance.<\/p>\n<\/div>\n<\/div>\n<\/li>\n

  • \n
    \n
    \n

    Failure to satisfy production readiness requirements.<\/p>\n<\/div>\n<\/div>\n<\/li>\n<\/ul>\n

    I attached the technical assessment and the incident references.<\/p>\n

    Then I submitted the decision.<\/p>\n

    The system automatically notified the relevant engineering managers, infrastructure leadership, security, and the executive change-approval group.<\/p>\n

    I closed my laptop.<\/p>\n

    For the first time that night, I allowed myself to stop working.<\/p>\n

    I went home and slept for three hours.<\/p>\n

    At 6:14 a.m., my phone began ringing.<\/p>\n

    It was my manager.<\/p>\n

    “Martin, are you awake?”<\/p>\n

    “Yes.”<\/p>\n

    “Did you reject the production change?”<\/p>\n

    “Yes.”<\/p>\n

    He exhaled.<\/p>\n

    “Todd is furious.”<\/p>\n

    “That’s unfortunate.”<\/p>\n

    “The executive team wants an emergency meeting. They’re asking why the deployment is blocked.”<\/p>\n

    I sat up.<\/p>\n

    “Because it isn’t ready.”<\/p>\n

    “Can you come in?”<\/p>\n

    “I’ll be there.”<\/p>\n

    By the time I reached the office, the atmosphere had changed.<\/p>\n

    People were moving between conference rooms. Engineers were checking their phones. Several managers were standing near the operations dashboard.<\/p>\n

    The production deployment had been scheduled for 7:00 a.m.<\/p>\n

    Without my approval, it couldn’t proceed through the established process.<\/p>\n

    Todd was already in the executive conference room.<\/p>\n

    He looked as though he hadn’t slept.<\/p>\n

    The moment I entered, he stood.<\/p>\n

    “What exactly do you think you’re doing?”<\/p>\n

    I placed my laptop on the table.<\/p>\n

    “Following the change-management policy.”<\/p>\n

    “You blocked my deployment.”<\/p>\n

    “I rejected a production change that doesn’t meet the required readiness standards.”<\/p>\n

    “You don’t have the authority to stop a company initiative.”<\/p>\n

    I opened the approval matrix.<\/p>\n

    “I have the authority to reject an unsafe production change within my assigned reliability scope. The policy is available to everyone in this room.”<\/p>\n

    Todd turned toward the chief operating officer, Helen Brooks.<\/p>\n

    “He’s refusing to cooperate with the product organization.”<\/p>\n

    Helen looked at the documents.<\/p>\n

    “Martin, is the change technically unsafe?”<\/p>\n

    “Yes.”<\/p>\n

    “Explain.”<\/p>\n

    I connected my laptop to the conference display.<\/p>\n

    For the next twenty minutes, I walked the room through the architecture.<\/p>\n

    I showed how the proposed consolidation would create a shared dependency between two systems designed to fail independently.<\/p>\n

    I explained that the recovery environment Todd wanted to remove was not simply a duplicate server.<\/p>\n

    It was a separate operational path.<\/p>\n

    If the primary environment experienced a failure involving the shared authentication or routing layer, the proposed configuration could prevent the backup environment from taking over.<\/p>\n

    I showed the incident history.<\/p>\n

    I showed the missing test results.<\/p>\n

    I showed the incomplete rollback plan.<\/p>\n

    And then I showed the written warnings I had sent over the previous three weeks.<\/p>\n

    Nobody interrupted.<\/p>\n

    When I finished, Helen looked toward Todd.<\/p>\n

    “Did you review this assessment?”<\/p>\n

    Todd shifted in his chair.<\/p>\n

    “We reviewed the general direction. Engineering is always going to identify reasons not to move forward.”<\/p>\n

    “That wasn’t my question,” Helen said.<\/p>\n

    He didn’t answer.<\/p>\n

    The chief financial officer, Robert Klein, opened the risk report.<\/p>\n

    “Who approved removing the independent recovery environment?”<\/p>\n

    Todd replied that the decision had been included in the efficiency plan.<\/p>\n

    Robert looked at the document.<\/p>\n

    “This is a proposed savings target. It’s not an engineering approval.”<\/p>\n

    Todd’s face tightened.<\/p>\n

    Helen turned back to me.<\/p>\n

    “What would it take to make this deployment safe?”<\/p>\n

    I had prepared the answer weeks earlier.<\/p>\n

    “Keep the independent recovery environment active. Complete the failure-isolation tests. Validate the rollback procedure. Run the new configuration in parallel before moving payment traffic. Then we can review the results and approve a controlled rollout.”<\/p>\n

    Robert looked at the estimated savings.<\/p>\n

    “How much of the planned reduction would that eliminate?”<\/p>\n

    “Approximately thirty percent of the original target, depending on the final hosting configuration.”<\/p>\n

    Todd immediately interrupted.<\/p>\n

    “Which defeats the entire point.”<\/p>\n

    I looked at him.<\/p>\n

    “No. It prevents the company from saving money by removing the systems that keep its payments running.”<\/p>\n

    Nobody laughed.<\/p>\n

    Helen asked for a short recess.<\/p>\n

    When the executives returned, they announced that the deployment would remain blocked pending an independent technical review.<\/p>\n

    Todd looked directly at me.<\/p>\n

    “This isn’t over.”<\/p>\n

    I nodded.<\/p>\n

    “I understand.”<\/p>\n

    I returned to my office and resumed monitoring the production environment.<\/p>\n

    I thought the matter would end with the deployment being delayed.<\/p>\n

    I was wrong.<\/p>\n

    At 9:42 a.m., the chief technology officer called me.<\/p>\n

    His name was David Chen. He had joined Northstar two years earlier and generally stayed out of operational disputes unless something serious happened.<\/p>\n

    “Martin, I need you in my office.”<\/p>\n

    When I arrived, he closed the door.<\/p>\n

    “Have you heard anything about your bonus?”<\/p>\n

    “No.”<\/p>\n

    “Finance has received a request to remove it.”<\/p>\n

    I felt my stomach tighten.<\/p>\n

    “From whom?”<\/p>\n

    “Todd.”<\/p>\n

    David turned his monitor toward me.<\/p>\n

    There was a compensation adjustment request with my name on it.<\/p>\n

    The justification read:<\/p>\n

    Failure to demonstrate collaborative leadership during strategic transformation.<\/p>\n

    I stared at the screen.<\/p>\n

    “Is this connected to the deployment rejection?”<\/p>\n

    “That’s what I’m trying to establish.”<\/p>\n

    I explained the midnight message.<\/p>\n

    David asked me to forward it.<\/p>\n

    I did.<\/p>\n

    He read it silently.<\/p>\n

    Then he looked up.<\/p>\n

    “Did Todd have any authority to unilaterally cancel your bonus?”<\/p>\n

    “Not according to my agreement.”<\/p>\n

    David opened the compensation policy.<\/p>\n

    The bonus required performance evaluation and approval through a defined executive process. A vice president could submit feedback, but could not simply remove an earned award because an employee disagreed with a technical proposal.<\/p>\n

    David shook his head.<\/p>\n

    “Then this needs to be reviewed.”<\/p>\n

    He also asked me to provide the full record of the deployment warnings and my rejection.<\/p>\n

    I sent everything.<\/p>\n

    By lunchtime, the issue had reached the company’s general counsel.<\/p>\n

    I didn’t know what would happen next.<\/p>\n

    I had no desire to turn the situation into a personal battle. I wanted the company to follow its own policies and make decisions based on evidence.<\/p>\n

    But the following morning, the internal review uncovered something that made the situation considerably more serious.<\/p>\n

    The proposed consolidation had been included in Todd’s quarterly cost-reduction presentation.<\/p>\n

    He had already reported projected savings to the board as though the project were substantially approved.<\/p>\n

    The presentation listed the retirement of the independent recovery environment as a completed milestone.<\/p>\n

    It wasn’t completed.<\/p>\n

    It hadn’t even passed testing.<\/p>\n

    The projected savings also assumed that several senior infrastructure roles would be eliminated after the migration.<\/p>\n

    Those positions included the engineers responsible for the recovery systems Todd wanted to remove.<\/p>\n

    In other words, his financial plan depended on eliminating the people who understood how the replacement architecture was supposed to work.<\/p>\n

    The board had been given a picture of a transformation that didn’t yet exist.<\/p>\n

    The chief financial officer requested a reconciliation of the reported savings against approved projects.<\/p>\n

    The general counsel requested the change-management records.<\/p>\n

    The chief technology officer ordered an independent review of the proposed architecture.<\/p>\n

    Todd was placed on administrative leave from the production decision process while the review was conducted.<\/p>\n

    He was not fired immediately.<\/p>\n

    The company needed to establish what had happened and who had approved the financial reporting.<\/p>\n

    During the following two weeks, I worked with an independent engineering team.<\/p>\n

    We reviewed the architecture, the cost assumptions, the proposed staffing changes, and the historical incident data.<\/p>\n

    The review confirmed that several parts of Todd’s plan could be implemented safely.<\/p>\n

    However, the payment recovery consolidation was not ready.<\/p>\n

    The proposed schedule was unrealistic, and the risk assessment had been materially incomplete.<\/p>\n

    The review also found that the cost-reduction presentation had treated unapproved savings as committed results.<\/p>\n

    That discovery changed the tone of the entire investigation.<\/p>\n

    Todd was eventually removed from his position.<\/p>\n

    The company announced that he was leaving following an internal leadership review. I wasn’t involved in the employment decision, and I never learned every detail of the discussions between him and the board.<\/p>\n

    What I did know was that the deployment had been redesigned.<\/p>\n

    The new plan retained the independent recovery environment while allowing several other cost reductions to proceed.<\/p>\n

    We completed the required tests, ran the new configuration in parallel, and performed a controlled migration several months later.<\/p>\n

    The result was a measurable reduction in infrastructure costs without compromising the recovery architecture.<\/p>\n

    My bonus was also reviewed.<\/p>\n

    The company confirmed that Todd’s request had not followed the required compensation process.<\/p>\n

    After evaluating my performance records, operational results, and the terms of my agreement, the compensation committee approved the full $200,000 bonus.<\/p>\n

    When the payment appeared in my account, I didn’t celebrate.<\/p>\n

    I felt relieved.<\/p>\n

    But something had changed.<\/p>\n

    For twelve years, I had believed that being indispensable was the same as being valued.<\/p>\n

    I had believed that if I worked hard enough, solved enough problems, and stayed available long enough, the company would naturally recognize what I contributed.<\/p>\n

    Todd had shown me how fragile that assumption was.<\/p>\n

    A person could spend twelve years protecting an organization and still be treated as an inconvenience by someone who had arrived six months earlier.<\/p>\n

    The following quarter, Northstar created a formal production risk review process.<\/p>\n

    Critical infrastructure changes required documented technical approval, independent risk acceptance, and a verified rollback plan.<\/p>\n

    The company also introduced a policy requiring financial savings to be classified accurately as proposed, approved, or realized.<\/p>\n

    I was asked to lead the reliability governance group.<\/p>\n

    The position gave me authority to review major infrastructure changes across the company and to work directly with the CTO and finance leadership.<\/p>\n

    I accepted.<\/p>\n

    But I also made a personal decision.<\/p>\n

    I stopped answering every late-night call simply because someone expected me to.<\/p>\n

    I helped establish a proper on-call rotation, trained additional engineers, and documented the systems that had previously existed mostly in my head.<\/p>\n

    For the first time, I began building an organization that could function without depending on one exhausted person.<\/p>\n

    A few months later, David stopped by my office.<\/p>\n

    He looked at the new reliability dashboard and smiled.<\/p>\n

    “Things seem quieter around here.”<\/p>\n

    “They should be.”<\/p>\n

    “How does it feel?”<\/p>\n

    I thought about it.<\/p>\n

    “Different.”<\/p>\n

    He pulled up a chair.<\/p>\n

    “You know, when you typed that rejection, the executive team thought you were making a statement.”<\/p>\n

    “I was.”<\/p>\n

    He laughed.<\/p>\n

    “What statement?”<\/p>\n

    I turned toward the monitor.<\/p>\n

    “That production readiness isn’t negotiable.”<\/p>\n

    David nodded.<\/p>\n

    Then he asked, “Do you regret it?”<\/p>\n

    I looked at the systems dashboard.<\/p>\n

    Every critical service was operating normally. The recovery environments were healthy. The deployment process was documented. The engineers who had spent years working behind the scenes finally had a voice in decisions that affected their responsibilities.<\/p>\n

    “No,” I said. “I regret waiting so long to make the decision.”<\/p>\n

    That afternoon, I received a message from an engineer who had been working on my team for only eight months.<\/p>\n

    He wrote:<\/p>\n

    I used to think the most important person in engineering was the person who could fix the biggest outage. Now I think it’s the person willing to stop an outage before it happens.<\/p>\n

    I read it twice.<\/p>\n

    Then I saved it.<\/p>\n

    Because that was the part of the story I wanted to remember.<\/p>\n

    Todd had threatened my bonus because I refused to approve a dangerous shortcut.<\/p>\n

    He thought the number on my compensation statement would make me hesitate.<\/p>\n

    He thought twelve years of loyalty would make me ignore what I knew was wrong.<\/p>\n

    But the company didn’t need another executive presentation promising efficiency.<\/p>\n

    It needed someone willing to say no when the evidence demanded it.<\/p>\n

    And sometimes, protecting everything you’ve spent twelve years building begins with a single word.<\/p>\n

    REJECTED.<\/p>\n

    THE END.<\/p>\n<\/div>\n<\/div>\n

    <\/div>\n","protected":false},"excerpt":{"rendered":"

    At 5:37 a.m., I was staring at a red deployment failure on three monitors while my phone vibrated for the third time. Infrastructure was calling again. I hadn’t slept properly … <\/p>\n","protected":false},"author":1,"featured_media":109007,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10],"tags":[],"class_list":["post-109019","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-relaxing-story"],"_links":{"self":[{"href":"https:\/\/relaxingstory.com\/index.php?rest_route=\/wp\/v2\/posts\/109019","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/relaxingstory.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/relaxingstory.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/relaxingstory.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/relaxingstory.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=109019"}],"version-history":[{"count":1,"href":"https:\/\/relaxingstory.com\/index.php?rest_route=\/wp\/v2\/posts\/109019\/revisions"}],"predecessor-version":[{"id":109020,"href":"https:\/\/relaxingstory.com\/index.php?rest_route=\/wp\/v2\/posts\/109019\/revisions\/109020"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/relaxingstory.com\/index.php?rest_route=\/wp\/v2\/media\/109007"}],"wp:attachment":[{"href":"https:\/\/relaxingstory.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=109019"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/relaxingstory.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=109019"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/relaxingstory.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=109019"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}