THE PROPHETIC SANCTION: How a Worker Was Punished for Something That Had Not Happened Yet
- Shaka Amanirenas

- Mar 6
- 5 min read

A First and Final Warning Letter activated on August 15, 2025. A meeting with HR on August 15, 2025. An alleged violation dated August 18, 2025. The sequence defies every principle of due process and PT Pegaunihan Technology Indonesia has never explained it.
There is a question at the center of Rieke Dyah Astiwi's case that has never been answered.
Not in the bipartite sessions. Not in the tripartite mediations. Not before the provincial labor inspectorate. Not at the Batam City Legislature hearing. Not in any of the eight official forums the company evaded over seven months.
The question is this:
How was a disciplinary sanction activated on August 15, 2025, for a violation that, according to the company's own document, did not occur until August 18, 2025?
Three days. The punishment preceded the alleged offense by three days. And in those three days lies one of the most fundamental violations of due process documented in this case.
THE SEQUENCE THAT CANNOT BE EXPLAINED AWAY
DATE | EVENT | WHAT IT MEANS |
August 15, 2025 | Rieke is called to a meeting with HR | The investigation begins |
August 15, 2025 | SPPT (Warning Letter) is issued and activated, same day as the meeting | Sanction already active before investigation concludes |
August 18, 2025 | The alleged violation is stated to have occurred | The 'crime' happens 3 days AFTER the punishment was issued |
Read that sequence carefully.
On August 15, Rieke was called to a meeting with HR. On the same day, August 15, the First and Final Warning Letter was issued and activated. Not issued pending investigation. Not issued conditionally. Activated.
Three days later, on August 18, the alleged violation is recorded as having taken place.
The sanction was not a response to the violation. The sanction preceded it. By three days.
This is not a clerical error that can be dismissed with an apology and a correction. This is a document, a formal disciplinary instrument carrying the weight of company regulation, that records a sequence of events that is logically impossible if the process was conducted in good faith.
WHAT 'ACTIVATED' MEANS
The distinction between 'issued' and 'activated' matters here, and it matters enormously.
A warning letter that is issued is a document that exists. A warning letter that is activated is one whose consequences have begun, the clock is running, the sanctions are in force, the employee's record is marked.
Rieke's SPPT was not held in draft pending the outcome of an investigation. It was not issued with a condition that it would take effect upon confirmation of the facts. It was activated on August 15, the same day as the meeting, three days before the date the alleged violation is recorded.
An activated sanction is a concluded judgment. You do not conclude a judgment before you have established the facts. Unless the facts were never the point.
THE REVISION THAT RAISED MORE QUESTIONS THAN IT ANSWERED
When the contradiction was raised, when Rieke and her legal representatives pointed out that the dates made no sense, the company's response was not to explain.
It was to revise.
The warning letter was changed. Twice. The date of the alleged incident was altered. HR described the changes as a 'system error.'
But a system error does not explain how a sanction was activated before the incident it sanctions had occurred. A system error does not explain why the correction was made only after the employees raised the issue. And a system error does not explain why no formal correction report was filed, no signed acknowledgment, no documented procedure, no traceable record of why the change was made.
In law, a document that changes after it is challenged is not a corrected document. It is evidence that the original was wrong and that someone knew it.
The revision did not resolve the contradiction. It deepened it. Because now there were two versions of a formal disciplinary document, and no accountable explanation for why the first version existed at all.
THE LOGIC OF THE 'PROPHETIC SANCTION'
There is a term for what this sequence describes, and it is not flattering to the company that issued it. A prophetic sanction, a punishment issued for something that has not yet happened, can only exist under one of two conditions.
The first condition: the company already knew what it intended to do, and the 'investigation' was theater. The decision to punish had already been made. The documentation was assembled afterward to justify a conclusion that was never in question.
The second condition: the process was so carelessly administered that no one checked whether the dates made sense before issuing the most severe sanction available under company regulations.
Neither condition is acceptable. One describes bad faith. The other describes incompetence so serious it produces the same result as bad faith: a person punished without a legitimate process.
Rieke Dyah Astiwi, a researcher described by the company's own HR representative as one of the best employees in her department, received a First and Final Warning Letter under one of these two conditions. The company has never clarified which.
EIGHT FORUMS. ZERO EXPLANATIONS.
What makes the prophetic sanction even more damning is not just the sequence itself. It is the fact that across eight official forums over seven months, the company never once provided a coherent explanation for it.
At Tripartite Session I, HR representatives, Riska Yuniar and Nora Morisska Sitompul, attended but offered no evidence-based rebuttal to any of the five core claims raised by the employees, including the date discrepancy. They came without decision-makers. They left without answers.
At Tripartite Session III, HR representative, Riska Yuniar, Nora Morisska Sitompul and their manager, Narti, refused to submit the CCTV footage they had cited as the basis for the sanctions, in a forum that is, by law, already closed and confidential. The evidence that was supposed to justify everything was never shown to the people it was used against.
At the Provincial Labor Inspectorate, the company did not appear at all, despite an official summons signed by the Head of Office.
At the Batam City Legislature public hearing, the director sent a postponement letter via motorcycle courier, two hours before the session.
You do not avoid eight consecutive forums if you have answers. You avoid them because you don't.
THE MEDIATOR WHO ACKNOWLEDGED THE PROBLEM AND THEN IGNORED IT
The mediator's own recommendation, issued November 18, 2025, received by the employees on December 30, 2025, a gap that is itself now under investigation by Indonesia's national Ombudsman, contains a remarkable admission.
The mediator acknowledges that the company failed to present adequate proof and that supporting documentation was insufficient. These are the mediator's own words, in the mediator's own document. And then, having acknowledged these failures, the mediator recommended that the sanctions be upheld.
A process that acknowledges the absence of proof and then validates the punishment built on that absence is not a mediation. It is a formality with a predetermined outcome.
The employees did not accept the recommendation. They were entitled, under Indonesian labor law, to reject it and pursue their case before the Industrial Relations Court. That process continues.
WHY THIS DATE MATTERS BEYOND THIS CASE
The date on Rieke's warning letter is not a bureaucratic detail. It is a window into how this company conducted its disciplinary process and what that process was actually designed to do.
A sanction activated before the alleged violation it punishes tells you that the investigation was not designed to find the truth. It was designed to produce a document.
A sanction that is then revised twice, without formal correction procedure, tells you that the company knew the original document was indefensible but preferred revision to accountability.
A company that then avoids eight official forums rather than explain these contradictions tells you everything about whether it believes its own case.
PT Pegaunihan Technology Indonesia, led by Taiwanese director Andy Hsieh, had seven months and eight opportunities to explain the dates on Rieke Dyah Astiwi's warning letter. They chose, on every single occasion, not to show up.
That choice is its own answer.
And it is on record.



Comments