Governing the fair resolution of disputes, the enforcement of penalties,
and the preservation of system integrity across all SD partners.
✶ ✶ ✶
01
Preamble & Founding Principles
"This system exists to eliminate procrastination, not to protect my ego."
The Self Discipline System was created to enforce consistent execution across six critical life areas: Health, Spiritual, Financial, Business, Relationships, and Personal Growth. It exists to force action over intention.
This Constitution establishes the judicial framework governing the fair resolution of disputes between SD participants. It supplements the SD System Official Guide and takes precedence in all matters of dispute resolution.
Founding Principles
Radical Honesty — The system only functions when all participants report truthfully, even when the truth triggers consequences.
No Self-Exemptions — No participant may serve as both defendant and judge in their own case. All disputed penalties are resolved by the Judicial Bench.
Inevitable Consequences — Penalties that are found valid by the Bench are non-negotiable and must be enforced immediately.
Transparency Over Privacy — All task data, statuses, comments, and system interactions are admissible evidence. There are no sealed records in the SD System.
The System Serves Growth — The purpose of penalties is behavioural change, not punishment. The purpose of the judiciary is fairness, not gotcha moments.
02
Definitions
Term
Definition
Participant
Any person whose tasks are tracked within an SD System spreadsheet.
Partner
An accountability partner who monitors a Participant's task completion and system compliance.
Prosecution
The party (typically the Partner) alleging that a penalty should be triggered or that a system violation occurred.
Defence
The party (typically the Participant) arguing against the alleged penalty or violation.
The Bench
The panel of four AI judges that adjudicates disputes. Comprises the Chief Justice and three Associate Justices.
Case Brief
The formal written submission containing the prosecution's charges and evidence, and the defence's response.
Verdict
The Bench's ruling: Guilty, Not Guilty, or Partially Guilty (reduced penalty).
Precedent
A recorded ruling that must be referenced by the Bench when adjudicating future cases with similar facts.
IGA / NIGA
Income Generating Activity / Non-Income Generating Activity — the task classification that determines weight.
The Journal
The daily task execution workspace where statuses are tracked.
The Archive
The permanent, tamper-proof record of all completed days.
03
Task Lifecycle & Valid Statuses
Every task that enters the Journal must terminate in one of these statuses. There are no other valid end states.
Completed
The full activity has been finished. The intended outcome has been achieved. No critical step remains undone. The result is usable, not symbolic. Marking a task Completed without finishing it is a system violation.
Started
At least 25–30 minutes of meaningful effort was made (not just opening tools or files). A real external blocker prevented completion: technical error, power/internet outage, missing dependency, physical constraint. The task is normally finishable in one day. A comment must explain what was done, what blocked progress, and what the next attempt will be. If ANY condition is missing, the task must remain Pending and will become Overdue.
Overdue
The task remained Pending after midnight. No meaningful attempt was made. The system was violated. A penalty is triggered automatically. There are no manual overrides for Overdue status.
Critical Rule: Once Added, Never Removed
Once a task appears in the Journal — whether auto-generated from Settings or manually added — it cannot be removed, hidden, or deleted. It must reach one of the three terminal statuses above. Removing a task to avoid a penalty is classified as system sabotage under Article 14.
04
Penalty Triggers
A penalty is triggered when:
A task remains Pending after midnight and becomes Overdue.
A task is marked Completed without being genuinely completed (system sabotage).
A task is marked Started without meeting all four Started conditions.
A task is removed from the Journal to avoid consequences.
A Partner reminder is ignored for more than 48 hours without the task being added to the Journal (see Article 5: The Avoidance Doctrine).
No penalty applies when:
The task is genuinely Completed.
The task is validly Started (all four conditions met and documented).
An Update Blocker Exception applies (see Article 12).
Tiered Penalty Structure
When the first penalty of the day triggers, the full penalty amount applies. For subsequent overdue tasks on the same day, 50% of the penalty amount applies per task. This prevents the "already failed today, might as well give up" mentality. Every additional failure still costs.
05
The Avoidance Doctrine
Failure to add a known obligation to the Journal does not exempt the Participant from consequences.
This article addresses the most common dispute pattern in the SD System: a Partner identifies a task that should be done, reminds the Participant, and the Participant avoids adding it to the Journal — thereby preventing the system from ever triggering a penalty.
The 48-Hour Rule
Clause 5.1 — Partner Task Escalation
When a Partner identifies a task that falls within the SD System's six life areas (Health, Spiritual, Financial, Business, Relationships, Personal Growth) and reminds the Participant, the following timeline applies:
First Reminder: The Partner communicates the task. The clock starts. 24 Hours: If the task has not been added to the Journal, the Partner issues a formal second reminder referencing this clause. 48 Hours: If the task is still not in the Journal, the Partner may file a case under the Avoidance Doctrine. The Bench will evaluate whether the Participant wilfully avoided adding the task to dodge accountability.
Clause 5.2 — Valid Defences Against Avoidance
The Participant may defend against an Avoidance charge by demonstrating:
1. The task does not fall within the SD System's six life areas.
2. The task is already being tracked through a different mechanism.
3. The task requires research or planning before it can be defined as an actionable Journal entry (maximum 72-hour planning grace period, after which it must be added as a planning task).
4. The Partner's reminder was not clear or specific enough to create an actionable task.
Clause 5.3 — The Skipping vs. Avoiding Distinction
"I skipped it" and "I avoided it" are treated identically when the Partner provided multiple reminders. The system does not distinguish between passive neglect and active avoidance — both result in the same outcome: the task was not done. Intent does not reduce the penalty; only the defences in Clause 5.2 apply.
06
Evidence & Burden of Proof
Admissible Evidence
Journal tab screenshots showing task statuses and timestamps
Archive tab records
WhatsApp messages between Partners (including timestamps)
SD Dashboard metrics (Weighted Score, IGA Ratio, completion rates)
System logs (Apps Script execution logs, trigger histories)
Settings tab entries showing when tasks were added or removed
Clause 6.1 — Prosecution Bears Initial Burden
The Prosecution must present: (a) the specific rule or article allegedly violated, (b) evidence that the violation occurred, and (c) the penalty being requested.
Clause 6.2 — Defence Bears Rebuttal Burden
Once the Prosecution presents its case, the Defence must respond with specific counter-evidence or cite a valid exception from this Constitution. General denials ("that doesn't count" or "I didn't avoid it") without supporting evidence are treated as weak defences by the Bench.
Clause 6.3 — Missing Evidence Clause
If evidence should exist but cannot be produced (e.g., sleep tracking data that "stopped working," a task that "disappeared" from the Journal), the absence of evidence is itself treated as evidence. The Bench may draw adverse inferences from conveniently missing data.
07
The Judicial Bench
The Bench comprises four AI judges, each receiving the identical case brief and Constitution text. No judge receives additional information or context that the others do not.
ClaudeChief Justice
ChatGPTJustice 2
GeminiJustice 3
DeepSeekJustice 4
Judicial Independence
Each judge deliberates independently. They do not see each other's verdicts.
Each judge receives the same prompt containing: this Constitution, the case brief (prosecution + defence), and all submitted evidence.
Judges may not be lobbied, prompted with biased framing, or given additional context by either party outside the case brief.
If either party is found to have tampered with the prompt sent to any judge (adding persuasive text, removing evidence, or altering the Constitution text), the case is automatically ruled in favour of the opposing party.
Recusal
If any judge is unavailable (API down, service disruption), the case proceeds with the remaining judges. A minimum of three judges must rule for a valid verdict. If only two judges are available, the case is postponed until a third becomes available.
08
Filing a Case
Who May File
Either the Partner (as Prosecution) or the Participant (as Defence seeking to overturn an automatic penalty) may file a case. A Partner files when they believe a penalty should trigger but hasn't. A Participant files when they believe a penalty triggered unfairly.
Case Brief Format
Every case submitted to the Bench must follow this structure:
Section 1 — Case Identification
Case number (sequential), date filed, Prosecution name, Defence name.
Section 2 — Prosecution Brief
The charge: which article or rule was violated. The facts: what happened, with dates and times. The evidence: screenshots, messages, system data. The requested penalty amount.
Section 3 — Defence Brief
The response: admission, denial, or partial admission. The counter-evidence: any data that supports the defence. Mitigating circumstances (if applicable). The requested outcome: no penalty, reduced penalty, or alternative remedy.
Section 4 — Constitution Reference
Both parties must cite the specific articles of this Constitution that support their position. The Bench will reference these citations in its ruling.
Filing Deadline
A case must be filed within 7 days of the disputed event. After 7 days, the event is considered settled under the status quo (penalty triggered or not triggered, as the system recorded it).
✶ ✶ ✶
09
Trial Procedure
Judicial Process Overview
The following diagram illustrates the complete trial process from filing through to sentencing and precedent recording:
SD Judicial Process
Step-by-Step Process
Filing: The Prosecution prepares the case brief and shares it with the Defence.
Response: The Defence has 24 hours to add their response to the brief.
Submission: The complete case brief (both sides) is submitted to all four judges simultaneously. The prompt must include: the full Constitution text, the case brief, and all evidence.
Deliberation: Each judge independently returns a verdict (Guilty / Not Guilty / Partially Guilty) with a written explanation.
Tallying: The verdicts are recorded in the SD Court log.
Ruling: The majority verdict becomes the final ruling.
Precedent: The ruling and its reasoning are recorded for future reference.
The Prompt Template
To ensure judicial consistency, the following template must be used when submitting cases to each judge. Neither party may modify this template.
Standard Judicial Prompt
"You are a judge on the SD (Self Discipline) Judicial Bench. You have been presented with a dispute between two parties in a self-discipline accountability system. Your role is to determine whether a penalty should be triggered based on the SD Constitution and the evidence presented. You must rule: GUILTY (penalty applies in full), NOT GUILTY (no penalty), or PARTIALLY GUILTY (reduced penalty — specify the reduction and reasoning). Base your ruling strictly on the Constitution and evidence. Do not add rules that don't exist. Do not show sympathy to either party. Be fair, precise, and reference specific articles in your reasoning. [CONSTITUTION TEXT] [CASE BRIEF]"
10
Verdicts & Sentencing
Majority Rule
Verdict Count
Outcome
4 Guilty
Unanimous guilty. Full penalty applies.
3 Guilty, 1 Not Guilty
Strong majority. Full penalty applies.
2 Guilty, 2 Not Guilty
Split decision. Chief Justice (Claude) casts the tiebreaker with an extended written explanation.
1 Guilty, 3 Not Guilty
Strong majority not guilty. No penalty.
0 Guilty, 4 Not Guilty
Unanimous not guilty. No penalty. Prosecution is advised to review the relevant Constitution article.
Partially Guilty Verdicts
If one or more judges rule Partially Guilty, the penalty is calculated as follows: take the average reduction percentage recommended by the Partially Guilty judges and apply it to the full penalty. For example, if two judges say Guilty (100%), one says Partially Guilty (50%), and one says Not Guilty (0%), the final penalty is the average of the majority that found guilt: (100 + 100 + 50) / 3 = 83% of the full penalty.
Sentencing
The standard penalty amount is defined in each Participant's Penalty tab. The Bench does not set penalty amounts — it determines whether the penalty triggers. The penalty amount structure (including tiered penalties) is a matter of system configuration, not judicial discretion.
11
Precedent & Case Law
Every ruling by the Bench becomes precedent. Future cases with substantially similar facts must reference and follow prior rulings unless the Bench explicitly distinguishes the new case from the precedent.
Precedent Record Format
Field
Description
Case Number
Sequential identifier (e.g., SD-2026-001)
Date
Date the ruling was issued
Parties
Prosecution vs. Defence
Charge
The article(s) allegedly violated
Summary
Brief description of the facts
Ruling
Guilty / Not Guilty / Partially Guilty
Vote
Each judge's individual verdict
Key Reasoning
The principle established by this ruling
Penalty Applied
Amount enforced (if any)
Clause 11.1 — Precedent Override
A precedent may only be overturned by a unanimous (4-0) vote of the Bench in a subsequent case. A 3-1 majority may distinguish a new case from a precedent but cannot overrule it.
12
Exceptions & Mitigating Circumstances
Update Blocker Exception
A task that was genuinely completed but could not be updated in the system before midnight due to an external blocker may be corrected under these strict conditions:
The task was fully completed before midnight.
The update was blocked by power outage, internet failure, device failure, or system malfunction.
A comment explaining the blocker must be added within 24 hours.
The Partner must be notified within 24 hours.
This exception may not be used more than twice per month. Beyond that, it triggers a review of task scheduling practices.
This exception does NOT cover: forgetting to update, choosing to update "later," or the task not actually being completed.
Force Majeure
Clause 12.1 — Extraordinary Circumstances
In genuinely extraordinary situations (medical emergency, natural disaster, bereavement, or similar), a Participant may request a Force Majeure suspension of up to 3 days. The Partner must be notified. No penalty applies during the suspension period. This is not a loophole for busy days, travel, or tiredness.
Grace Periods for New Features
Clause 12.2 — System Change Grace Period
When a new feature, tab, or tracking requirement is added to the SD System, a 3-day grace period applies. During this period, failures related to the new feature are flagged but do not trigger penalties. After 3 days, full enforcement resumes. This prevents disputes like "I didn't know that tab existed."
13
System Failures & Automation Disputes
The SD System relies on automated scripts. When automation fails, disputes often follow. This article governs those situations.
Clause 13.1 — Automation Failure Does Not Erase Obligation
If a script fails to mark a task as Overdue, the task is still Overdue. The automation is a convenience, not the source of truth. The rules in this Constitution are the source of truth. A Participant may not argue "the system didn't catch it, so no penalty applies."
Clause 13.2 — Reporting Credit
If a Partner detects and reports a system failure (e.g., "the overdue script didn't run last night"), the Partner's vigilance is noted. However, reporting the failure does not void the penalty — it only ensures the penalty is correctly applied.
Clause 13.3 — Manual Override Rules
When automation fails, manual correction is permitted only if: (a) the automation verifiably failed (not user error), (b) the manual action replicates what the script would have done, (c) the correction is made within 24 hours, (d) a comment documents what failed and what was corrected, and (e) the Partner is notified.
Clause 13.4 — Disappearing Tasks
If a task that was present in the Journal disappears without reaching a terminal status (Completed, Started, or Overdue), this is presumed to be task removal unless the Participant can produce evidence of a system error (script logs, error messages). The burden is on the Participant to prove the task was removed by automation, not by human action.
14
Anti-Sabotage Provisions
The following actions constitute system sabotage. Any confirmed act of sabotage triggers the full penalty amount automatically, without requiring a judicial hearing.
Prohibited Actions
1. Marking tasks Completed without finishing them.
2. Marking tasks Started without meaningful effort.
3. Removing, hiding, or deleting tasks to avoid penalties.
4. Editing timestamps retroactively.
5. Downgrading task difficulty or weight after failure.
6. Hiding failures from accountability Partners.
7. Tampering with automation scripts to alter outcomes.
8. Manipulating tracking devices (turning off sleep trackers, step counters, etc.) to conceal non-compliance.
9. Altering the judicial prompt or Constitution text when submitting cases to the Bench.
10. Deliberately not adding known obligations to the Journal to avoid tracking (see Article 5).
Clause 14.1 — Suspicion vs. Proof
A Partner may raise suspicion of sabotage (e.g., "your sleep tracker conveniently stopped working the night you said you went to bed at 9:50pm"). Suspicion alone does not trigger the sabotage penalty. However, the Bench may consider a pattern of convenient failures as circumstantial evidence. Three or more instances of the same type of "failure" in a 30-day period shifts the burden of proof to the Participant to demonstrate the failures were genuine.
15
Partner Rights & Obligations
Partner Rights
To view all system tabs, including Journal, Archive, Settings, Dashboard, and Penalties.
To question any status, comment, or data entry.
To file a case with the Bench when they believe a penalty should trigger.
To challenge manual overrides, corrections, or exceptions.
To request evidence or explanation for any system anomaly.
To remind the Participant of tasks and invoke the 48-Hour Rule (Article 5).
Partner Obligations
To check the Participant's system at least once daily.
To report penalties immediately upon detection ("Penalty Triggered").
To file cases in good faith — not as harassment or for financial gain.
To respect the Bench's ruling once issued, even if they disagree.
To maintain their own system with the same integrity they demand of the Participant.
Clause 15.1 — Frivolous Cases
If a Partner files a case and the Bench returns a unanimous (4-0) Not Guilty verdict, the case is deemed frivolous. Three frivolous cases within 90 days may result in a review of the Partner's filing privileges. This prevents weaponizing the judiciary.
✶ ✶ ✶
16
Amendments
This Constitution may be amended under the following conditions:
An amendment may be proposed by any Participant or Partner.
The proposed amendment must be submitted in writing with the rationale for the change.
All active Participants and Partners must be notified of the proposed amendment.
A 7-day comment period allows objections to be raised.
If no objections are raised, the amendment is ratified and takes effect immediately.
If objections exist, the amendment is submitted to the Bench for advisory opinion. A 3-of-4 majority advisory in favour of the amendment allows ratification.
Clause 16.1 — Immutable Provisions
The following provisions may never be amended or weakened, regardless of process:
1. The requirement for radical honesty (Article 1).
2. The prohibition on self-exemptions (Article 1).
3. The anti-sabotage provisions (Article 14).
4. The inevitability of validly triggered penalties (Article 4).
5. This immutability clause itself.
No future amendment may weaken the enforcement logic of this system.