The palletizing incident occurred at a consumer-goods distribution plant outside Nashville.<\/p>\n
A robotic arm transferred stacked cases from a conveyor onto pallets.<\/p>\n
During a maintenance-clearing sequence, the arm moved unexpectedly while an operator stood near the edge of the safeguarded area.<\/p>\n
The operator stepped back in time.<\/p>\n
No injury.<\/p>\n
The plant shut down the cell immediately.<\/p>\n
That fact mattered.<\/p>\n
Nobody tried to restart.<\/p>\n
Nobody told the operator to continue.<\/p>\n
The customer\u2019s supervisor followed procedure.<\/p>\n
Hartwell\u2019s remote support instructed them to preserve logs.<\/p>\n
By the time the independent safety team arrived, the evidence remained intact.<\/p>\n
Already better than Blue River.<\/p>\n
Priya\u2019s recusal transferred technical oversight to an external safety engineer and an internal committee excluding everyone who had participated in the original release decision.<\/p>\n
That excluded Priya.<\/p>\n
Several Engineering leaders.<\/p>\n
Two product managers.<\/p>\n
Maya served as field representative.<\/p>\n
I stayed involved only through Field Operations response.<\/p>\n
The structure felt excessive.<\/p>\n
Good.<\/p>\n
High stakes justified inconvenience.<\/p>\n
Initial logs showed the robot received a valid motion command during a sequence where motion should have remained inhibited.<\/p>\n
Software timing looked likely.<\/p>\n
Then the review uncovered something uncomfortable.<\/p>\n
The relevant logic change had been introduced three months before product release.<\/p>\n
Engineering identified an intermittent test failure.<\/p>\n
The test team recommended a longer validation cycle.<\/p>\n
The program was already behind schedule.<\/p>\n
A major customer launch depended on delivery.<\/p>\n
Priya, then head of Engineering, approved conditional release.<\/p>\n
The condition required additional monitoring and a software patch before full-scale deployment.<\/p>\n
The patch was completed.<\/p>\n
But not before the Nashville system shipped.<\/p>\n
That meant Priya\u2019s decision was relevant.<\/p>\n
Very relevant.<\/p>\n
The board received notice.<\/p>\n
Employees learned quickly.<\/p>\n
Rumors came faster.<\/p>\n
Priya had rushed unsafe software.<\/p>\n
Priya covered up test failures.<\/p>\n
The new CEO was just like Grant.<\/p>\n
That last comparison was unfair.<\/p>\n
It was also inevitable.<\/p>\n
Hartwell had become sensitized to executive overrides.<\/p>\n
Any deviation from technical recommendation now carried historical weight.<\/p>\n
Rachel warned everyone not to react by overcorrecting.<\/p>\n
\u201cNot every override is misconduct.\u201d<\/p>\n
Maya nodded.<\/p>\n
\u201cSometimes technical teams are conservative.\u201d<\/p>\n
\u201cSometimes executives see constraints they don\u2019t.\u201d<\/p>\n
\u201cYes.\u201d<\/p>\n
\u201cThe question is whether Priya\u2019s decision had a defensible basis.\u201d<\/p>\n
\u201cAnd whether the risk was communicated.\u201d<\/p>\n
\u201cExactly.\u201d<\/p>\n
The review reconstructed the release decision.<\/p>\n
Priya had not hidden the test failure.<\/p>\n
It appeared in the project record.<\/p>\n
She documented schedule pressure.<\/p>\n
She required mitigation.<\/p>\n
She asked software leadership whether the temporary configuration met minimum safety requirements.<\/p>\n
They answered yes.<\/p>\n
That looked better.<\/p>\n
Then came the problem.<\/p>\n
The software lead\u2019s approval had been conditional too.<\/p>\n
He wrote:<\/p>\n
Acceptable for limited pilot deployment with enhanced monitoring. Not recommended for broad release until timing patch validated.<\/p>\n
Nashville was not limited pilot deployment.<\/p>\n
It was commercial production.<\/p>\n
Who changed the classification?<\/p>\n
The product manager.<\/p>\n
Why?<\/p>\n
Customer deadline.<\/p>\n
Who approved commercial release?<\/p>\n
Priya.<\/p>\n
Her signature sat at the bottom.<\/p>\n
The review interviewed her.<\/p>\n
She did not remember noticing that the software approval was limited to pilot deployment.<\/p>\n
That sounded painfully familiar.<\/p>\n
Evelyn and the Blue River warning.<\/p>\n
Different event.<\/p>\n
Same governance question.<\/p>\n
What does responsibility mean when an executive signs something without fully absorbing a condition embedded inside it?<\/p>\n
Priya\u2019s critics had an easy answer.<\/p>\n
Fire her.<\/p>\n
Her defenders had another.<\/p>\n
Honest mistake.<\/p>\n
Neither was sufficient.<\/p>\n
We needed mechanism.<\/p>\n
The external safety engineer tested the failure.<\/p>\n
After nine days, the team reproduced it.<\/p>\n
Under a narrow timing condition, an operator command could remain queued during a transition into maintenance-clearing mode.<\/p>\n
The safeguard stopped most motion.<\/p>\n
But a later state change allowed the queued command to execute after reset.<\/p>\n
The architecture should have cleared the command.<\/p>\n
It did not.<\/p>\n
That was a real software defect.<\/p>\n
The timing patch fixed it.<\/p>\n
If Nashville had received the validated patch before operation, the near miss probably would not have occurred.<\/p>\n
Probably.<\/p>\n
Safety reports avoided absolute certainty where evidence could not support it.<\/p>\n
Next question.<\/p>\n
Did Priya\u2019s release decision cause the system to ship without the patch?<\/p>\n
Yes.<\/p>\n
At least partly.<\/p>\n
Commercial release made deployment possible.<\/p>\n
Other approvals existed.<\/p>\n
But her authority mattered.<\/p>\n
Next.<\/p>\n
Did she know she was violating a safety restriction?<\/p>\n
The evidence said no.<\/p>\n
She believed Engineering had approved release with monitoring.<\/p>\n
She failed to recognize that the approval applied only to pilot deployment.<\/p>\n
That was negligence in review.<\/p>\n
Not concealment.<\/p>\n
Not fraud.<\/p>\n
Not retaliation.<\/p>\n
Not Grant.<\/p>\n
But still serious.<\/p>\n
The board convened without Priya.<\/p>\n
I attended only for operational impact.<\/p>\n
Harold chaired.<\/p>\n
The external safety engineer presented.<\/p>\n
Nobody minimized.<\/p>\n
The incident could have caused severe injury.<\/p>\n
The operator escaped because he stepped back quickly and the safeguarded area limited motion.<\/p>\n
One director asked the question everyone had avoided.<\/p>\n
\u201cWould we terminate a lower-level manager for this?\u201d<\/p>\n
Rachel answered carefully.<\/p>\n
\u201cDepends on role, history, process adherence, and whether the mistake reflected gross negligence.\u201d<\/p>\n
\u201cThat sounds evasive.\u201d<\/p>\n
\u201cIt\u2019s accurate.\u201d<\/p>\n
Another director asked:<\/p>\n
\u201cWhat would happen to a product manager who signed a release without recognizing a conditional safety limitation?\u201d<\/p>\n
Engineering HR answered.<\/p>\n
\u201cAt minimum, serious corrective action.\u201d<\/p>\n
\u201cDemotion?\u201d<\/p>\n
\u201cPossible.\u201d<\/p>\n
\u201cTermination?\u201d<\/p>\n
\u201cPossible.\u201d<\/p>\n
Harold looked toward me.<\/p>\n
\u201cYou\u2019re quiet.\u201d<\/p>\n
\u201cI don\u2019t decide this.\u201d<\/p>\n
\u201cOperational view.\u201d<\/p>\n
I thought.<\/p>\n
\u201cIf you remove Priya because the outcome was dangerous, you teach executives to hide dangerous outcomes.\u201d<\/p>\n
One director frowned.<\/p>\n
\u201cThat sounds like protection.\u201d<\/p>\n
\u201cIt isn\u2019t.\u201d<\/p>\n
\u201cWhat are you saying?\u201d<\/p>\n
\u201cSeparate the failure from the response.\u201d<\/p>\n
I looked around the table.<\/p>\n
\u201cThe release decision was bad.\u201d<\/p>\n
No qualification.<\/p>\n
\u201cThe review process asks why, whether it was reckless, whether there\u2019s a pattern, and whether confidence can be restored.\u201d<\/p>\n
\u201cCan it?\u201d<\/p>\n
\u201cNot my call.\u201d<\/p>\n
Harold nodded.<\/p>\n
Rachel added another point.<\/p>\n
\u201cAccountability should not become automatic maximum punishment.\u201d<\/p>\n
Exactly.<\/p>\n
Grant\u2019s system had trained everyone to think mistake equals penalty.<\/p>\n
A reformed system could not simply reverse direction and punish executives reflexively.<\/p>\n
That would produce the same hiding behavior at a higher salary.<\/p>\n
Still, consequence had to be meaningful.<\/p>\n
Otherwise, employees would see double standards.<\/p>\n
The board reviewed Priya\u2019s record.<\/p>\n
The old retaliation complaint from five years earlier.<\/p>\n
Her later process improvements.<\/p>\n
Her response to the Louisville safety appeal.<\/p>\n
Her handling of the remote-response pilot.<\/p>\n
Her willingness to disclose the Nashville incident immediately.<\/p>\n
Her recusal.<\/p>\n
No record of concealment.<\/p>\n
No pattern of pressuring people to suppress technical concerns.<\/p>\n
That distinguished her from Grant.<\/p>\n
But distinction did not erase responsibility.<\/p>\n
The board reached a decision.<\/p>\n
Priya would remain CEO.<\/p>\n
Her authority over product safety release would be permanently separated from executive commercial authority.<\/p>\n
That control applied to all future CEOs, not only her.<\/p>\n
She would forfeit a substantial portion of current-year incentive compensation.<\/p>\n
Not because Hartwell needed the money.<\/p>\n
Because executive compensation included safety performance.<\/p>\n
She would undergo external safety-governance training.<\/p>\n
Engineering release procedures would be redesigned.<\/p>\n
Most importantly, the board issued a formal finding.<\/p>\n
Priya exercised inadequate diligence in approving commercial release of a system subject to a limited-deployment safety condition.<\/p>\n
Direct.<\/p>\n
Public internally.<\/p>\n
No euphemism.<\/p>\n
Priya received the decision in the same conference room where Grant once defended accountability adjustments.<\/p>\n
She read it.<\/p>\n
Then asked one question.<\/p>\n
\u201cWas keeping me a close decision?\u201d<\/p>\n
Harold answered.<\/p>\n
\u201cYes.\u201d<\/p>\n
\u201cHow close?\u201d<\/p>\n
\u201cWe\u2019re not disclosing individual votes beyond governance policy.\u201d<\/p>\n
She nodded.<\/p>\n
Another good answer.<\/p>\n
Then she looked at me.<\/p>\n
I said nothing.<\/p>\n
Afterward, she asked me privately.<\/p>\n
\u201cDo you think I should resign?\u201d<\/p>\n
I hated the question.<\/p>\n
\u201cDo you?\u201d<\/p>\n
\u201cI don\u2019t know.\u201d<\/p>\n
\u201cThen don\u2019t ask me to decide your identity.\u201d<\/p>\n
She looked irritated.<\/p>\n
\u201cI\u2019m asking for advice.\u201d<\/p>\n
\u201cMy advice is separate shame from responsibility.\u201d<\/p>\n
\u201cThat sounds like therapy.\u201d<\/p>\n
\u201cProbably stolen from Laura.\u201d<\/p>\n
Priya sat down.<\/p>\n
\u201cI approved the release.\u201d<\/p>\n
\u201cYes.\u201d<\/p>\n
\u201cSomeone could have been crushed.\u201d<\/p>\n
\u201cYes.\u201d<\/p>\n
Her eyes filled.<\/p>\n
She looked away.<\/p>\n
\u201cI keep thinking about that operator.\u201d<\/p>\n
\u201cGood.\u201d<\/p>\n
She gave me a sharp look.<\/p>\n
\u201cGood?\u201d<\/p>\n
\u201cIf you stopped thinking about him, I\u2019d worry.\u201d<\/p>\n
\u201cThat doesn\u2019t help.\u201d<\/p>\n
\u201cIt\u2019s not supposed to.\u201d<\/p>\n
She breathed slowly.<\/p>\n
\u201cWhat if staying looks like arrogance?\u201d<\/p>\n
\u201cIt might.\u201d<\/p>\n
\u201cWhat if leaving looks like accountability?\u201d<\/p>\n
\u201cIt might.\u201d<\/p>\n
\u201cHelpful.\u201d<\/p>\n
\u201cYou have to decide whether you can still do the job under the board\u2019s restrictions and after understanding what you missed.\u201d<\/p>\n
She looked down.<\/p>\n
\u201cAnd employees decide whether to trust me.\u201d<\/p>\n
\u201cYes.\u201d<\/p>\n
\u201cBoard too.\u201d<\/p>\n
\u201cYes.\u201d<\/p>\n
\u201cCustomers.\u201d<\/p>\n
\u201cYes.\u201d<\/p>\n
\u201cNo pressure.\u201d<\/p>\n
I smiled faintly.<\/p>\n
\u201cLeadership is outcomes, remember?\u201d<\/p>\n
\u201cDon\u2019t quote Grant at me.\u201d<\/p>\n
\u201cFair.\u201d<\/p>\n
Priya stayed.<\/p>\n
Not because the board ordered her to.<\/p>\n
Because she concluded resignation would turn one failure into a symbolic ending instead of forcing her to lead through the consequences.<\/p>\n
Some employees supported that.<\/p>\n
Others did not.<\/p>\n
The reaction was sharp.<\/p>\n
At one employee forum, a technician stood and asked:<\/p>\n
\u201cIf I made a mistake that nearly killed someone, would I still have my job?\u201d<\/p>\n
Priya answered personally.<\/p>\n
\u201cPossibly.\u201d<\/p>\n
The technician looked surprised.<\/p>\n
\u201cPossibly?\u201d<\/p>\n
\u201cYes.\u201d<\/p>\n
\u201cIf you concealed it, lied about it, ignored procedure recklessly, or showed a pattern of unsafe behavior, perhaps not.\u201d<\/p>\n
She continued.<\/p>\n
\u201cIf you made a serious good-faith error, reported it, cooperated, and could still safely perform your role, termination would not automatically be the right answer.\u201d<\/p>\n
The technician folded his arms.<\/p>\n
\u201cSo CEOs get second chances.\u201d<\/p>\n
\u201cSo should technicians.\u201d<\/p>\n
That changed the room.<\/p>\n
Another employee asked:<\/p>\n
\u201cDid you deserve your bonus cut?\u201d<\/p>\n
\u201cYes.\u201d<\/p>\n
No hesitation.<\/p>\n
\u201cWhy?\u201d<\/p>\n
\u201cBecause part of my compensation depends on safety outcomes and leadership diligence.\u201d<\/p>\n
\u201cIsn\u2019t that like the old deductions?\u201d<\/p>\n
Priya paused.<\/p>\n
Important question.<\/p>\n
\u201cNo.\u201d<\/p>\n
\u201cWhy?\u201d<\/p>\n
\u201cBecause the incentive terms were defined before the work.\u201d<\/p>\n
She looked toward me briefly.<\/p>\n
Then back to the employee.<\/p>\n
\u201cAnd because Hartwell is not taking base compensation I already earned to pressure me into agreeing with management.\u201d<\/p>\n
That distinction had become cultural knowledge.<\/p>\n
People understood it now.<\/p>\n
The Nashville incident forced Hartwell to examine every conditional release process.<\/p>\n
We found three others where pilot limitations could be misunderstood.<\/p>\n
No incidents.<\/p>\n
All corrected.<\/p>\n
Product documentation changed.<\/p>\n
Conditional approvals received bold system flags.<\/p>\n
Commercial release could not proceed while any safety condition remained unresolved.<\/p>\n
No executive override.<\/p>\n
Not Priya.<\/p>\n
Not anyone.<\/p>\n
Again, her mistake became structure.<\/p>\n
That was the standard.<\/p>\n
Not perfection.<\/p>\n
Learning durable enough to outlast the person.<\/p>\n
The Nashville customer received full disclosure.<\/p>\n
Hartwell paid for corrective work.<\/p>\n
No attempt to shift cost onto field staff.<\/p>\n
No mysterious vendor invoices.<\/p>\n
No altered report.<\/p>\n
No billing dispute over the safety correction.<\/p>\n
The financial impact was substantial.<\/p>\n
Martin presented it without complaint.<\/p>\n
I teased him.<\/p>\n
\u201cYou\u2019ve changed.\u201d<\/p>\n
\u201cNo.\u201d<\/p>\n
He pointed at the spreadsheet.<\/p>\n
\u201cI just learned hidden costs are more expensive than visible ones.\u201d<\/p>\n
That might have been Finance\u2019s entire character arc.<\/p>\n
Maya led the field retrofit.<\/p>\n
When she returned, she brought back a photograph.<\/p>\n
The operator involved in the near miss stood beside the corrected cell.<\/p>\n
Alive.<\/p>\n
Uninjured.<\/p>\n
Uncomfortable with being photographed.<\/p>\n
Priya kept the picture in the safety-review file.<\/p>\n
Not on her office wall.<\/p>\n
Good.<\/p>\n
No hero mythology.<\/p>\n
Evidence.<\/p>\n
Months later, the operator sent Hartwell a short note.<\/p>\n
Thanks for taking it seriously.<\/p>\n
That sentence mattered more than praise.<\/p>\n
Taking something seriously did not mean pretending it should never have happened.<\/p>\n
It meant allowing the facts to change decisions afterward.<\/p>\n
Priya\u2019s standing inside Hartwell slowly recovered.<\/p>\n
Not fully.<\/p>\n
Some employees never trusted her the same way.<\/p>\n
That was allowed.<\/p>\n
Trust was not owed.<\/p>\n
Performance continued.<\/p>\n
The controls operated.<\/p>\n
The company moved forward.<\/p>\n
Evelyn remained outside management.<\/p>\n
When the Nashville incident became public through customer reporting, reporters contacted her for comment.<\/p>\n
She declined.<\/p>\n
That was harder than it looked.<\/p>\n
A former CEO defending Priya could have helped.<\/p>\n
Or hurt.<\/p>\n
Either way, it would have pulled authority backward.<\/p>\n
She stayed out.<\/p>\n
Priya noticed.<\/p>\n
So did the board.<\/p>\n
One evening, I called Evelyn.<\/p>\n
\u201cYou heard?\u201d<\/p>\n
\u201cEverything.\u201d<\/p>\n
\u201cWhat do you think?\u201d<\/p>\n
She paused.<\/p>\n
\u201cI think I would have defended myself too quickly.\u201d<\/p>\n
\u201cPriya didn\u2019t.\u201d<\/p>\n
\u201cNo.\u201d<\/p>\n
\u201cProud?\u201d<\/p>\n
\u201cVery.\u201d<\/p>\n
She laughed softly.<\/p>\n
\u201cAnd relieved I\u2019m not responsible.\u201d<\/p>\n
\u201cGrowth.\u201d<\/p>\n
\u201cDon\u2019t.\u201d<\/p>\n
I smiled.<\/p>\n
After the call, I looked at the latest governance dashboard.<\/p>\n
Appeals up slightly.<\/p>\n
Retaliation findings down.<\/p>\n
Safety stops stable.<\/p>\n
Turnover normalizing.<\/p>\n
Vendor exceptions lower.<\/p>\n
No metric proved culture.<\/p>\n
Together, they showed movement.<\/p>\n
Then Rachel came into my office holding a sealed envelope.<\/p>\n
\u201cWhat now?\u201d<\/p>\n
\u201cFormer employee claim.\u201d<\/p>\n
\u201cCompensation?\u201d<\/p>\n
\u201cNo.\u201d<\/p>\n
\u201cSafety?\u201d<\/p>\n
\u201cNo.\u201d<\/p>\n
She sat.<\/p>\n
\u201cThis one is about you.\u201d<\/p>\n
I stared.<\/p>\n
\u201cMe?\u201d<\/p>\n
\u201cYes.\u201d<\/p>\n
\u201cFrom when?\u201d<\/p>\n
\u201cTwo years ago.\u201d<\/p>\n
\u201cWho?\u201d<\/p>\n
\u201cA supervisor named Anthony Marks.\u201d<\/p>\n
I remembered him vaguely.<\/p>\n
Regional service manager.<\/p>\n
Left Hartwell during the reform period.<\/p>\n
\u201cWhat\u2019s the claim?\u201d<\/p>\n
Rachel slid the envelope toward me.<\/p>\n
\u201cHe says you retaliated against him for defending one of Grant\u2019s old policies.\u201d<\/p>\n
I felt my chest tighten.<\/p>\n
\u201cWhat did I do?\u201d<\/p>\n
\u201cHe says you blocked his promotion and reassigned major accounts.\u201d<\/p>\n
\u201cI did reassign accounts.\u201d<\/p>\n
\u201cWhy?\u201d<\/p>\n
\u201cPerformance.\u201d<\/p>\n
\u201cDocumented?\u201d<\/p>\n
\u201cI think so.\u201d<\/p>\n
\u201cYou think?\u201d<\/p>\n
That word again.<\/p>\n
I looked at the envelope.<\/p>\n
For years, I had helped build systems that forced authority to answer questions.<\/p>\n
Now the system had turned toward me.<\/p>\n
Rachel watched quietly.<\/p>\n
\u201cDo I recuse?\u201d<\/p>\n
\u201cYes.\u201d<\/p>\n
Immediate.<\/p>\n
I almost laughed.<\/p>\n
Of course.<\/p>\n
The process did not care that I had designed parts of it.<\/p>\n
That was the point.<\/p>\n
\u201cWhat happens now?\u201d<\/p>\n
\u201cIndependent review.\u201d<\/p>\n
\u201cWho?\u201d<\/p>\n
\u201cNot me.\u201d<\/p>\n
\u201cWhy?\u201d<\/p>\n
\u201cYou appointed me.\u201d<\/p>\n
I smiled despite the tension.<\/p>\n
\u201cGood.\u201d<\/p>\n
Rachel stood.<\/p>\n
At the door, she looked back.<\/p>\n
\u201cYou okay?\u201d<\/p>\n
\u201cNo.\u201d<\/p>\n
\u201cGood.\u201d<\/p>\n
I stared.<\/p>\n
She smiled.<\/p>\n
\u201cMaya says that.\u201d<\/p>\n
Then she left.<\/p>\n
The envelope remained on my desk.<\/p>\n
Anthony Marks.<\/p>\n
Blocked promotion.<\/p>\n
Reassigned accounts.<\/p>\n
Retaliation.<\/p>\n
I remembered enough to feel confident.<\/p>\n
That was dangerous.<\/p>\n
Confidence had protected too many people at Hartwell.<\/p>\n
So I did the thing I had spent years asking everyone else to do.<\/p>\n
I stopped defending myself.<\/p>\n
I preserved my records.<\/p>\n
I disclosed what I remembered.<\/p>\n
And I let someone else decide whether the system I had helped build could survive finding fault with me too.<\/p>\n
The palletizing incident occurred at a consumer-goods distribution plant outside Nashville. A robotic arm transferred stacked cases from a conveyor onto pallets. During a maintenance-clearing sequence, the arm moved unexpectedly … <\/p>\n","protected":false},"author":1,"featured_media":21990,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-22055","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-insightdrama"],"_links":{"self":[{"href":"https:\/\/insightdrama.com\/index.php?rest_route=\/wp\/v2\/posts\/22055","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/insightdrama.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/insightdrama.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/insightdrama.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/insightdrama.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=22055"}],"version-history":[{"count":1,"href":"https:\/\/insightdrama.com\/index.php?rest_route=\/wp\/v2\/posts\/22055\/revisions"}],"predecessor-version":[{"id":22090,"href":"https:\/\/insightdrama.com\/index.php?rest_route=\/wp\/v2\/posts\/22055\/revisions\/22090"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/insightdrama.com\/index.php?rest_route=\/wp\/v2\/media\/21990"}],"wp:attachment":[{"href":"https:\/\/insightdrama.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=22055"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/insightdrama.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=22055"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/insightdrama.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=22055"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}