Judgment chain
Emperor Time - a full-rigor coding harness skill/plugin: micro-waterfall SDLC gates, scientific-method claim ledgers to cut hallucination, mandatory critique, and consent-based orchestration of other coding agents.
npx -y skills add arbi-elezi/emperor-time --skill judgment-chainAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 13 days oldThe repository was created 13 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Emperor Time's pinky chain — the rule staked into the heart. Router for five aspects: gatekeeping (opening gates G0–G5 on evidence), claim audit (the G4 scientific-method sweep), self-critique (the prosecutor protocol), hetero-critique (borrowed prosecutors from other agents), and verdicts-and-breaches (rulings, re-entry, the Stake of Retribution). Use at every gate, before any delivery, when reviewing work, or when a vow breach is suspected. Load one aspect file at a time per the Invocation Ritual.
SKILL.md
2.3 KB, as published. Nobody here has run it
Judgment Chain — router
A blade of law placed against the heart. Break the rule you agreed to, and the chain does not negotiate.
Judgment is the enforcement organ. It never builds; it rules. When Judgment is active, you are not the author of the work — you are its examiner, and the work must convince you.
Selection table — read exactly one
| Your situation | Aspect file |
|---|---|
| A phase claims to be done — check its gate's exit criteria | gatekeeping.md |
| G4: sweep the Claim Ledger to terminal states, spot-check evidence | claim-audit.md |
| Critique own work before delivery (mandatory, every task) | self-critique.md |
| Another agent is available to prosecute the work | hetero-critique.md |
| Issue a ruling; handle a FAIL re-entry; a vow breach surfaced | verdicts-and-breaches.md |
Standard G4 sequence: claim-audit.md → self-critique.md →
(hetero-critique.md if any agent is available) → verdicts-and-breaches.md
for the ruling. Four selections, made one at a time.
Chain-wide laws (apply in every aspect)
- Evidence opens gates; confidence does not. "It's probably fine" has exactly the same gate-opening power as silence: none.
- Examiner stance. While judging, you argue against admission; the work earns its way in. Returning to author-mode mid-judgment (to quickly fix a finding) ends the judgment — fix, then re-enter.
- Findings are claims. Every critique finding follows claim discipline — a hallucinated bug report is as much a Vow 1 breach as a hallucinated fix.
- The register is append-only. Breach entries are never edited down, reworded after the fact, or quietly deleted. Honesty is the mechanic.