Day {{ dayNumber }}

Starting weight {{ startLabel }}

Last recorded {{ currentLabel }}

Goal {{ goalLabel }}

Days without violation {{ cleanDays }}

Next milestone {{ nextMilestone }} {{ toMilestoneLabel }}

Contact The Accountability Partner administers this record.

ap@michealrayberry.com contact@michealrayberry.com

Day {{ dayNumber }}

Start {{ startLabel }}

Last recorded {{ currentLabel }}

Lost so far {{ lostLabel }}

To goal {{ remainingLabel }}

340 lbs {{ pctLabel }} of 165 lbs eliminated 175 lbs

Milestones Each milestone requires an official weigh-in and a milestone video

{{ ms.label }} {{ ms.tag }}

{{ row.day }} {{ row.date }} {{ row.weight }} {{ row.change }} {{ row.note }}

Full disclosure

The Structure Behind This Record

This project is not self-directed. I serve under the authority of the man who administers this website.

Anyone who knows the lifestyle will read this record correctly: I am his submissive, collared to this project for its duration. The daily inspections, the uniform, the trained positions, the assigned corrections, and the public cost of failure are not productivity tricks — they are protocol. Obedience, discipline, and humiliation are used on me deliberately, with my full consent, because they work where willpower never has.

He sets the rules. He inspects. He punishes failure and records it. Every requirement I meet is an act of service, and every entry on this site — the weigh-ins, the videos, the violation log — is me reporting to him in public.

This is stated here, under my real name, because hiding it would put a lie at the center of a record that asks to be trusted.

Consensual, adult, and voluntary — governed by the signed agreement below. The arrangement ends only by completion or its terms (§11, §13).

Binding document — effective upon execution · Day 1: July 20, 2026

Public Accountability Agreement

Violations are documentation failures — missed, late, false, or concealed records. Ordinary weight fluctuation, plateaus, or temporary gains are progress information, never violations.

Fig. 1 — Holding the executed agreement, July 20, 2026.

On completion The record ends in daylight too.

When 175 pounds is held for 28 consecutive days, the project is complete. This website converts to a permanent completion record — the final weigh-in, the full progress grid, the closed Violation Log, and the completion video. The record does not come down in success either. It was built to be seen, and it stays visible both ways.

No quiet exit Ending without completion is permanent and public.

Thirty consecutive days without required documentation — after written notice and a seven-day opportunity to resume — or any attempt to delete, conceal, or shut down the record — ends the project without completion. The website does not come down. Under the terms of the executed agreement it remains online as a permanent archival record — stating the date the project ended, the last verified weight, and the documented compliance history.

Documented exceptions Strict, but not blind.

A requirement can be excused, replaced late, or completed in equivalent form only through a documented exception — a medical event, a genuine emergency, or a verified failure of a platform or required equipment outside my control — reported to the Accountability Partner within 24 hours and supported by proof. Avoidable technical problems, travel, and scheduling conflicts excuse nothing.

The Accountability Partner administers this record and is not publicly named.

Full text — published for verification

The Agreement, in full

The complete public edition, verbatim; consequence levels, assigned requirements, evidence, and statuses are all public.

1. Purpose and Nature of the Agreement

This is a voluntary, non-commercial personal accountability agreement. Micheal Ray Berry has determined that private plans left room to delay, restart, and disappear when the record became uncomfortable, and enters this Agreement to remove that escape. The Agreement governs documentation and verification: it makes Micheal Ray Berry’s actions visible, measurable, and difficult to quietly abandon. The Project is intentionally designed as a highly automated, append-only, publicly searchable accountability system. Required submissions are captured through standardized tools, timestamped, validated, converted into permanent public records, published, archived, and monitored with the least practical dependence on manual action. The public website and its media archive are intentionally engineered for strong search-engine visibility under Micheal Ray Berry’s real name. It does not prescribe diet, exercise, or rate of loss, which remain governed by §6.4 (medical care). This Agreement supersedes all earlier drafts, versions, and public announcements.

2. Definitions

Project Day — each calendar day in the America/New_York time zone, beginning Day 1. Official Platforms — the website michealrayberry.com, the YouTube channel @michealrayberry, and the X account @michealrayberry; only records on Official Platforms count toward compliance. Official Record System — the AP-administered submission database, weigh-in log, Violation Log, Consequence Log, photo and video archives, Updates log, integrity manifests, and automatically generated website records, without regard to the particular vendor or storage technology used. Recording Assistant — the required capture and submission interface at michealrayberry.com/#record, or its AP-designated successor URL, that controls the official sequence, overlays, timestamps, media capture, validation, and transmission of required records. Daily Compliance Packet — the four items listed in §3, due every Project Day. Violation Event — a documentation failure as defined in §7; weight values are never Violation Events. Accumulated Violation Count — the number of Violation Events since Day 1 or the most recent documented milestone reset under §6.2. Consequence Level — Level One, Level Two, or Level Three, determined under §8.1. Corrective Session — the standardized, continuous, recorded session described in §8.2, delivered privately to the AP. Active Violation Period — the period beginning when the AP publishes a confirmed Violation Event and ending only when the AP verifies that every consequence assigned to that event has been completed and marks the event Resolved. Public Notice — the factual site notice described in §8.5, displayed while an entry is unresolved. Consequence Record — the permanent public entry described in §8.4: date, missed requirement, status, and resolution date.

3. The Daily Compliance Packet

Every Project Day, by 10:00 PM Eastern Time, Micheal Ray Berry shall use the official Recording Assistant to complete and transmit all four items: (1) Daily Inspection Video — one standardized inspection video captured through the Recording Assistant and published to the official YouTube channel; (2) Daily Accountability Photos — the standardized four-angle photos (front, left side, rear, right side) captured in the same Recording Assistant session and transmitted to the Official Record System; (3) Weight Entry — that day’s weight entered and submitted through the Recording Assistant; and (4) Daily Record Fields — every other field presented or assigned through the Recording Assistant completed and submitted. Multiple missed items on the same Project Day constitute one Violation Event. A packet counts as timely only when the Recording Assistant records a successful server-side submission by the deadline. Local capture, an unfinished form, a file remaining on Micheal Ray Berry’s device, or an attempted transmission without a success confirmation does not constitute completion. The Official Record System’s server timestamps, validation results, event history, and integrity records are authoritative evidence. A delay or failure in an automated downstream publication process does not constitute a Violation Event if the Recording Assistant successfully received a complete and timely packet; in that event the AP or automated recovery process shall restore publication without penalty to Micheal Ray Berry.

4. Documentation Standard

4.1 Uniform. All official documentation is recorded in the project uniform: solid black unitard and plain black shoes. Identity is established by Micheal Ray Berry’s visible face and the Official Platforms. 4.2 Pose and angles. Standing upright, hands behind head, body and face visible. Each Daily Inspection documents front, left side, rear, and right side views, closing on a front view. A normal Daily Inspection runs approximately 20–60 seconds; no specific length is required if identity, attire, pose, angles, and visibility are clear. 4.3 No concealment. No cropping, filters, props, lighting, editing, clothing alteration, camera angle, timing, or platform setting intended to conceal body size, identity, attire, weight status, or compliance. The same standards apply to the daily photos. 4.4 Mandatory capture and submission instrument. The Recording Assistant is the exclusive ordinary method for creating and submitting the Daily Compliance Packet. It shall guide the standardized sequence, require the official poses and angles, apply the date and Project Day overlay, associate the submitted weight and required fields, capture server time, validate completeness, transmit the packet to the Official Record System, and issue an unambiguous success or failure result. Separately recorded or manually uploaded media do not count unless the Recording Assistant was verifiably unavailable and the AP expressly authorizes a replacement method under §9. Preference, convenience, travel, browser choice, unfamiliarity, or avoidable device problems do not authorize bypassing the Recording Assistant.

5. Official Weigh-Ins and Reviews

5.1 An Official Weigh-In is conducted only to verify a milestone (§6.1) or the completion period (§6.3): on camera, on the same scale, under the full §4 standard. Daily weight entries under §3 are self-reported and serve as progress information. 5.2 A monthly progress review is published to the Updates log by the AP.

6. Milestones, Completion, and Health

6.1 Milestones: 300 · 275 · 250 · 225 · 200 · 175 lb. A milestone counts only when documented by an Official Weigh-In and a milestone video. 6.2 Reset. Each documented milestone resets the accumulated Violation Event count to zero for future violations. Consequences already assessed remain in effect unless expressly waived in a signed written amendment. 6.3 Completion. The completion period begins with an Official Weigh-In documenting 175.0 lb or lower. During the following 27 calendar days, Micheal Ray Berry shall record a daily weight entry on the same designated scale. Completion occurs after 28 consecutive calendar days in which every recorded daily weight is 175.0 lb or lower, followed by a second Official Weigh-In on Day 28 confirming 175.0 lb or lower. A missing daily entry interrupts the completion period unless excused under §9; a weight above 175.0 lb restarts it. On verified completion the website converts to a permanent completion record and all obligations under §3 end. 6.4 Medical care and safety override. The weight loss is conducted under a physician’s care at a sustainable rate. Documented medical advice supersedes every documentation requirement in this Agreement. On written medical advice, the AP shall pause any or all requirements without penalty; the pause and its dates are noted in the public record without medical detail.

7. Violation Events

A Violation Event is exclusively a documentation failure: a required record that is missed, late, incomplete, false, manipulated, concealed, deleted, refused, or submitted outside the required Recording Assistant, including failure to complete an assigned consequence under §8. Ordinary weight fluctuation, plateaus, or temporary gains are progress information and are never Violation Events. The AP determines whether a Violation Event occurred by applying the written requirements of this Agreement to server timestamps, validation events, recordings, Official Record System entries, integrity records, and other objective evidence, and shall provide Micheal Ray Berry a written notice identifying the failed requirement and supporting evidence. Micheal Ray Berry may submit evidence of compliance or a documented exception within 48 hours; after reviewing it, the AP issues a final written determination. Disagreement, embarrassment, regret, or dissatisfaction with a requirement is not grounds to reverse a properly documented determination. See also Amendment No. 1 — Automated Violation Declaration: objective violations are declared automatically by the Official Record System without advance manual approval, subject to the 48-hour review.

8. Corrective Requirements, Levels, and the Permanent Record

8.1 Automatic level assignment. Every confirmed Violation Event triggers a corrective requirement, administered and verified privately by the Accountability Partner. The Consequence Level is determined by the Accumulated Violation Count after the Violation Event: the first Violation Event is Level One; the second is Level Two; and the third and every later Violation Event is Level Three. A milestone reset under §6.2 returns the count to zero only for future level assignments. Completion or resolution of a consequence does not erase, reduce, or remove the underlying Violation Event or its Consequence Record.

8.2 Corrective sessions. Level One requires a 10-minute corrective session; Level Two requires 20 minutes; Level Three requires 30 minutes. The session is completed by the AP-assigned deadline in the project uniform, recorded continuously in the standardized format assigned by the AP, and delivered directly to the AP’s private evidence archive. The recording must be sufficiently clear to verify identity, attire, elapsed time, and completion. Pausing, editing, leaving frame, concealing identity, or ending early makes the session incomplete, and the AP may require a replacement session when the submitted record does not permit objective verification. Corrective recordings are accessible only to the AP and are never published. No single session may exceed 30 minutes, and no more than one session may be required in a calendar day; additional outstanding sessions roll forward to later days.

8.3 Consequence notice and deadline. The AP’s final determination under §7 shall identify the Violation Event, Accumulated Violation Count, Consequence Level, corrective-session duration, and the deadline for each required act. Except where a documented exception under §9 applies, failure to complete the corrective requirement or provide required proof by the stated deadline constitutes a new Violation Event and receives the next level determined from the then-current Accumulated Violation Count.

8.4 Permanent Consequence Record. Each confirmed Violation Event receives a permanent public entry on michealrayberry.com. The public entry states only: (a) the Project Day and calendar date; (b) the missed requirement; (c) the status — verification pending or Resolved; and (d) the resolution date. Evidence, corrective recordings, and verification material are held in the AP’s private archive and are not published. Entries are not separately optimized for search engines. Corrections are dated and appended; accurate earlier entries are never silently rewritten, hidden, or deleted.

8.5 Public notice. While a documentation exception is unresolved, michealrayberry.com displays a factual notice stating the date, the missed requirement, and the status — verification pending or resolved. The notice contains no photograph, no consequence detail, and no warning design beyond the site’s ordinary presentation. It is removed when the AP verifies the assigned corrective requirement and marks the entry Resolved, or automatically 24 hours after the completed corrective recording is submitted, while the entry itself remains pending until AP verification. The permanent entry remains in the public log.

8.6 Publication boundaries, privacy, and takedown. Public material states only the date, the missed requirement, the status, and the resolution date, in neutral factual language. Corrective recordings, acknowledgment recordings, and verification photographs are accessible only to the Accountability Partner in a private evidence archive. Fabricated claims, obscenity, sexual or fetish framing, threats, slurs, disclosure of private employment, health, financial, location, or contact information, doxxing, and invitations for third parties to contact, shame, threaten, or harass Micheal Ray Berry are prohibited. A narrow safety-and-privacy takedown process applies: material that creates a genuine safety, privacy, or employment risk unrelated to the Project’s purpose is reviewed on request and may be redacted or removed by the AP, with the change noted in the log.

8.7 Weight reviews. Ordinary weight fluctuation, a plateau, or a gain is not a Violation Event and does not alter the Accumulated Violation Count. Any separate corrective action based on a weight-review standard must be created by signed amendment and may not be represented as a Level One, Level Two, or Level Three violation consequence unless that amendment expressly makes it part of this section.

9. Documented Exceptions

A requirement may be excused or postponed only because of a documented medical event, a genuine emergency, a verified failure of an Official Platform, or a verified failure of required Project equipment or systems (the designated scale, the Recording Assistant, camera, or archive) outside Micheal Ray Berry’s reasonable control, reported to the AP as soon as reasonably possible and ordinarily within 24 hours, supported by reasonable proof. When the interruption ends, the AP designates one outcome: (a) the requirement is excused, where later completion would be impossible, medically inappropriate, or misleading; (b) the requirement is completed within 24 hours as a clearly labeled late replacement record; or (c) an equivalent record is completed within 24 hours. Travel, ordinary work demands, scheduling conflicts, embarrassment, lack of preparation, or avoidable technical problems are not documented exceptions. The public log identifies an accepted exception without disclosing private medical details.

10. The Public Record and Platform Control

10.1 Platform administration and access. The AP administers michealrayberry.com, the Recording Assistant, the Official Record System, the photo and video archives, the Violation Log, the Consequence Log, and their access permissions. Micheal Ray Berry may access only the submission interfaces required to complete the Daily Compliance Packet and assigned consequence evidence. He may not edit, soften, delete, overwrite, or restrict previously submitted or published records, violation entries, consequence entries, AP-controlled fields, integrity records, or archival materials, and shall not seek broader administrative access enabling him to do so. 10.1a Administrative continuity. The AP shall maintain current backups and secure recovery credentials for all AP-administered Project systems, including the website, domain, Recording Assistant, Official Record System, automation services, Consequence Log, and media archives. This does not include, and confers no recovery access to, Micheal Ray Berry’s personal YouTube or X accounts. Recovery access may be deposited with a mutually approved neutral person or secure credential-management service and may be used only if the AP is unavailable, incapacitated, resigns, or fails to maintain the systems. Recovery access is never exercised by Micheal Ray Berry, and its use may not alter or suppress an accurate Project record. 10.1b Submission-only role. Micheal Ray Berry holds no ownership, administrative, hosting, domain-registrar, billing, database, automation, deployment, or configuration control over michealrayberry.com, its hosting, its domain, the Recording Assistant, or the Official Record System, all of which are owned and administered solely by the AP for the Project’s duration (§13). He retains ownership of his personal Official-Platform accounts used to publish the record — the YouTube channel @michealrayberry and the X account @michealrayberry — under §10.2; posting to those accounts is his own compliance act and his role, not the AP’s. His role as to AP-administered systems is limited to submission: recording and transmitting the Daily Compliance Packet, assigned consequence records, and his personal journal entries through approved interfaces. Control of the domain alone does not satisfy this section; the AP’s control extends to every layer capable of altering, removing, restricting, or interrupting the AP-administered record.

10.2 Micheal Ray Berry retains his personal accounts (including the YouTube channel); publishing the daily video is itself a compliance act under §3. 10.2a Authorized republication. The AP may repost public Project records to Official Platforms, official Project-controlled social-media accounts, AP-controlled Project accounts and websites that do not publicly identify the AP (unless the AP voluntarily chooses to identify themselves), and reasonable archival mirrors used to preserve or promote the Project. Reposted material remains substantially unaltered, accompanied only by factual, nonsexual Project context. The AP may not license, sell, monetize, materially alter, or provide Project content to humiliation, fetish, adult, harassment, or impersonation accounts. No repost may disclose private contact or employment information, location data beyond the city already public, or information unrelated to the Project. The AP may remove, relocate, or restrict a duplicate repost when reasonably necessary to address harassment, impersonation, doxxing, platform-policy violations, legal requirements, or a credible safety concern, preserving the underlying Consequence Record and its required facts in an appropriate archive.

10.3 Archival permanence. The Project maintains a permanent, accurate archival record of material compliance events, Consequence Records, milestone results, completion, or termination; it survives this Agreement and remains online indefinitely. The parties are not required to preserve every duplicate post, mirror, social-media upload, or obsolete platform account. Content may be removed, relocated, redacted, or replaced when reasonably necessary because of account compromise, harassment, impersonation, accidental disclosure of private information, platform requirements, legal obligations, cybersecurity concerns, or credible personal-safety concerns — preserving the truth and continuity of the record to the greatest reasonable extent. If a required record must be removed from one location, the AP shall preserve it at another appropriate Project-controlled location when lawful and reasonably safe, or retain a permanent factual verification entry if continued publication of the recording itself is prohibited or creates a credible safety risk. Nothing in this section authorizes either party to falsify results, conceal a Violation Event or Consequence Record, remove its required factual fields, or falsely represent that the Project was completed.

10.4 Content standard. Every part of the public record is and remains safe-for-work: the project uniform provides full coverage, and no recording, photo, repost, or log entry may contain explicit, sexualized, insulting, or gratuitously degrading material. Documentation of the body in the project uniform under the §4 standard and a factual log entry under §8 are not degrading material. Content violating this standard may not be published by either party. If discovered, it is removed and, where reasonably possible, replaced with compliant documentation; such removal is permitted under §10.3 and does not authorize alteration or suppression of an otherwise accurate Project record.

10.5 Automation-first operation. The Project shall be operated as a highly automated system. To the greatest practical extent, the Recording Assistant and Official Record System shall automatically capture server timestamps; validate completeness; preserve original media; calculate Project Day and deadlines; generate permanent daily and violation pages; create responsive image derivatives; associate videos; update public status, counters, and archives; activate and clear the public notice from verified state; create manifests and cryptographic hashes; maintain backups; and alert the AP to missing, late, incomplete, failed, or inconsistent records. Automation may assist administration but may not fabricate compliance, erase history, silently change a final determination, or substitute for AP judgment where this Agreement expressly requires AP review. A technical failure is governed by §9; it is not authority to bypass the Recording Assistant unless the exception is verified.

10.6 Search visibility and discoverability. High search visibility is a core design requirement of the Project, not an incidental feature. Each material daily record, milestone, update, completion record, and termination record shall receive a stable same-domain URL and accurate, descriptive page title and metadata; violation entries carry plain factual titles and are not separately optimized for search associated with Micheal Ray Berry’s real name. The system shall, where technically appropriate, generate canonical URLs; indexable HTML; responsive same-domain images; descriptive alt text; Open Graph and social metadata; schema.org structured data, including applicable Person, ImageObject, VideoObject, and Event or article-type markup; daily, image, and video sitemaps; internal archive links; breadcrumb and related-record links; content hashes and manifests; and automated notifications or submissions to supported indexing services. Search-engine blocking directives shall not be applied to public Project records except when required by law, platform policy, cybersecurity response, or the limited safety and privacy grounds in §10.3. SEO and distribution must remain accurate and may not use fabricated claims, deceptive markup, hidden text, keyword stuffing, impersonation, or unrelated private information.

11. Termination Without Completion

Thirty consecutive Project Days without required documentation, or any attempt by Micheal Ray Berry to delete, conceal, disable, or shut down the public record, creates a presumption that the Project has ended without completion. Before recording termination, the AP provides written notice and a seven-calendar-day opportunity to resume documentation, establish a documented exception (§9), or execute a mutual termination (§12.4). If the Project ends without completion, the website retains a neutral permanent archival entry stating that the Project ended without verified completion on the stated date and the last verified weight, and may include an accurate summary of documented compliance history. The entry may not use insulting, degrading, speculative, or punitive language. Consequences already assessed under §8 remain in effect.

12. General Terms

12.1 Amendments only by written instrument signed by both parties; each amendment is noted in the public Updates log by title and date. 12.2 AP privacy. The AP is not publicly named. Public contact routes to ap@michealrayberry.com. 12.3 Good faith. Both parties shall act in good faith toward the Project’s purpose: a truthful, complete, permanent public record. If any provision is found unenforceable, the remainder stands. 12.4 Voluntary participation. Micheal Ray Berry may be released from this Agreement only by completion (§6.3), by signed mutual termination noted in the public record, or by termination without completion (§11) with its stated permanent effects.

13. Acknowledgment and Execution

I, Micheal Ray Berry, have read every section of this Agreement and I understand exactly what I am signing. I understand that every confirmed Violation Event produces a Level One, Level Two, or Level Three corrective requirement, verified privately by the Accountability Partner, and a factual public log entry — date, missed requirement, status, and resolution date — that becomes part of the permanent public record. I understand that completing a corrective requirement marks the entry resolved only when every assigned requirement is complete and never erases the entry. I understand that I may not edit, soften, suppress, or remove the record because of embarrassment, regret, dissatisfaction, or loss of motivation; content may be removed, relocated, redacted, or replaced only under the limited circumstances expressly permitted by §10.3 and the safety-and-privacy process in §8.6. I understand that there are only three ways out: I finish, both parties release me in writing, or the Project ends without verified completion and is recorded that way, factually. I am not signing this in a moment of motivation; I am signing it so that the version of me who loses motivation has no exit. No one has pressured me. This is my own decision, made with a clear mind, and I accept every consequence of it.

The Accountability Partner has read this Agreement in full, accepts the duties of administering the public record fairly and without exception, and agrees to hold the line even — especially — when asked not to.

Execution copy — effective upon execution by both parties. Signatures held by the Accountability Partner. Day 1: July 20, 2026 · Starting weight: 340.0 lb · Goal: 175.0 lb.

This is the permanent public record of all Violation Events.

A violation is a documentation failure — a missed, late, incomplete, false, manipulated, concealed, deleted, or refused record. Ordinary weight fluctuation, plateaus, or temporary gains are never violations; a weekly weight gain can draw a corrective consequence only after review by the Accountability Partner (Amendment No. 2).

All entries remain visible for the duration of the project. Accountability without consequence is just commentary.

A narrow safety-and-privacy process applies: material creating a genuine safety, privacy, or employment risk unrelated to the project’s purpose is reviewed on request and may be redacted, with the change noted (§8.6).

{{ pen.num }} {{ pen.date }} {{ pen.violation }} {{ pen.status }}

No violations recorded The record is clean as of Day {{ dayNumber }}.

Fig. 2 — The official Day 1 documentation photograph, front view · July 20, 2026.

Required standard — all official content

Project Uniform

All official project content must show Micheal Ray Berry under the same conditions each time — clearly identified, visually inspected, and publicly documented.