Binding document — effective upon execution · Day 1: August 13, 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, August 13, 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 of the agreement signed on August 13, 2026, incorporating every amendment made since. 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 official YouTube channel @michealrayberry, and the AP-administered media archive, together with any Project account the AP designates for republication; only records on Official Platforms count toward compliance. The daily inspection video is both published to the official record and posted publicly to the official YouTube channel by the deadline; a verified outage of either platform is handled under §9. 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, published on the permanent record beside the Violation Event that caused it. 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 five items: (1) Daily Inspection Video — one standardized inspection video captured through the Recording Assistant, published to the official record at michealrayberry.com, and posted publicly to the official YouTube channel @michealrayberry, where each day page embeds it; a missed or late YouTube posting is itself a Violation Event; (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; (4) Daily Record Fields — every other field presented or assigned through the Recording Assistant completed and submitted; and (5) Activity Sync — that day’s device-recorded activity data (steps, active-zone minutes, distance, and calories), delivered to the Official Record System by automatic sync from the connected device platform while a device connection is active. Activity figures are read from the device platform, never self-reported. A failure of the device platform or the sync service itself, evidenced by the Official Record System’s sync log, is a downstream failure and not a Violation Event. 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.

3.1 Additional structure and requirements. In addition to the Daily Compliance Packet, the Accountability Partner may establish further daily structure, routines, check-ins, and requirements in support of the Project's purpose. Such requirements (a) must serve the Project's health and accountability purpose and be reasonable in light of it; (b) remain at all times subject to §6.4 and §9 — documented medical advice and a physician's guidance supersede them, and any requirement a licensed physician advises against is void; (c) must be safe, lawful, and strictly non-sexual and safe-for-work under §10.4; (d) take effect only when adopted by a written amendment signed under §12.1 and then noted in the public Updates log by title and date; and (e) once in effect, are enforced under §§7–8 on the same automatic, non-discretionary basis as every other requirement. Micheal Ray Berry may contest a new requirement within 48 hours only on the ground that it fails (a), (b), or (c); otherwise it takes effect and stands. This authority exists only for the Project's duration and ends on completion (§6.3) or termination (§11).

4. Documentation Standard

4.1 Uniform. All official documentation is recorded in the project uniform: solid black unitard and plain black shoes. It is a visible symbol of the commitment entered into at the start of the Project, appearing in every inspection and standardized photograph from beginning to completion. Identity is established by Micheal Ray Berry’s visible face and the Official Platforms. 4.2 Wait position. Every inspection recording opens and closes in the Wait position: standing upright and squared to the camera, feet apart at the established width, hands behind the back, head level, eyes forward. The opening Wait is held while the Project Day, date, recorded weight, and verification code are established on the record; the closing Wait is held while the session is closed. Wait files no progress photograph. 4.3 Pose and angles. Standing upright, hands behind the head, body and face visible. Each Daily Inspection documents front, left side, rear, and right side views in sequence, closing on a front view before returning to Wait. A normal Daily Inspection runs approximately 20–60 seconds; no specific length is required if identity, attire, pose, angles, and visibility are clear. 4.4 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.5 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. Violation Events are declared automatically by the Official Record System from objective evidence — server timestamps, validation results, and event history — without advance approval by the Accountability Partner. The Accountability Partner has no discretion to declare, excuse, soften, downgrade, or overlook a violation; the Partner’s role is confined to confirming or rejecting each automatic declaration against the written requirements of this Agreement, and on those written requirements alone. Micheal Ray Berry may contest a declaration within a fixed 48-hour window by submitting evidence of compliance or a documented exception (§9); the Partner rejects the declaration only where that evidence establishes, under the written rules, that no Violation Event occurred. After the 48-hour window closes the determination stands and is not reopened. Disagreement, embarrassment, regret, or dissatisfaction with a requirement is not grounds to reverse it.

8. Corrective Requirements, Levels, and the Permanent Record

8.1 Automatic level assignment. Every confirmed Violation Event triggers a corrective requirement, assigned automatically by the Accumulated Violation Count and verified 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. The Consequence Level follows automatically from the count; the Accountability Partner cannot raise, lower, or waive it. 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. A confirmed Violation Event is answered by corrective corner time. Level One requires 10 minutes; Level Two requires 20 minutes; Level Three or higher requires 30 minutes. Unless the AP assigns otherwise, the position is facing the designated corner or wall, standing upright, hands behind the head, substantially still for the whole period, with no phone, entertainment, reading, or unrelated activity. The timer begins only once that position is established. Leaving the position, materially changing posture, ending early, or otherwise failing the verification standard invalidates the attempt, and the full period is completed again from zero. The session is completed by the AP-assigned deadline in the project uniform, recorded continuously in one unbroken take, published on the permanent record beside the Violation Event that caused it, and posted publicly to the official YouTube channel. 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. Submitting the recorded session and posting it publicly resolves the entry; the AP reviews the posting and may overrule — reopening the entry and requiring a replacement session — only against the written verification standard of this section (identity, project uniform, elapsed time, and an unbroken, unedited take), and only with a stated written reason. A session that meets that standard resolves the entry and may not be reopened. Corrective recordings are published on the permanent record and are not removed on completion or resolution.

8.3 Consequence notice and deadline. The determination identifies the Violation Event, Accumulated Violation Count, Consequence Level, and corrective-session duration. The corrective session must be completed, recorded, and filed within 72 hours of the violation notice. The Accountability Partner cannot extend, shorten, or waive this deadline except under a documented exception (§9). Except where such an exception applies, failure to complete the corrective requirement or provide required proof within the 72 hours constitutes a new Violation Event and receives the next Consequence 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 — open, corrected, or resolved; (d) the timestamp at which the correction was submitted; (e) the timestamp at which the entry was resolved; and (f) the Accountability Partner's verification result. Where the record for a Project Day is absent or incomplete, the entry states that neutrally as "No record" or "Incomplete record". The corrective recording is published on the permanent record beside the entry that caused it and posted publicly to the official YouTube channel. Completing the requirement closes the obligation; it does not remove the recording, and neither does resolution of the entry. Verification photographs are held privately 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 an entry is open, michealrayberry.com carries a notice on every page. It is deliberately prominent and strictly factual, and states the date and the requirement missed, how many required items remain missing, whether a correction has been submitted, that assigned consequences remain pending until completed and verified, and how many other entries remain open. It carries no photograph and no embedded recording, and no description of the assigned consequence beyond the required facts; once the corrective recording is published on the record, the notice may link to it beside the entry. The notice is removed when the completed corrective recording is submitted, which marks the entry Resolved; if the AP subsequently overrules, the entry reopens and the notice returns. The permanent entry remains in the public log.

8.6 Publication boundaries, privacy, and takedown. The public record is factual. It states the date, the requirement missed, the status, the submission and resolution timestamps, and the verification result, in neutral language. Corrective recordings are published in full, beside the Violation Event that caused them, and are not removed on completion or resolution. Nothing about the corrective process is withheld: what was assigned, what was served, and how it was served are all on the record. All published material is safe for work and non-sexual — the participant is fully covered in the project uniform throughout. Verification photographs are held privately and are not published. Corrections to the record are dated and appended so the correction history is itself permanent and auditable; accurate earlier entries are never silently rewritten, hidden, or deleted. 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 social 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 accounts — including 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. Compliance under §3 requires publication to the official record and a public posting to the official YouTube channel @michealrayberry; posting the same material to any other personal account is optional and is neither required for compliance nor sufficient to establish it. 10.2a Purpose-limited license and republication. For the Project's purpose — public accountability and documentation — Micheal Ray Berry grants the AP a worldwide, royalty-free, perpetual license to repost, share, distribute, mirror, create short factual excerpts of, and archive public Project content on Official Platforms, official Project-controlled accounts, and reasonable archival or visibility mirrors, in any medium, without attribution requirement, approval, notice, or compensation, so long as the reuse serves that accountability and documentation purpose. The AP may not sell, monetize, or commercially exploit Project content; may not license or sublicense it except to technical service providers solely for hosting, storage, or delivery of the official record under confidentiality obligations; may not materially alter it beyond ordinary formatting and factual Project context; and may not provide it to impersonation accounts or contexts. No repost may disclose private contact, employment, health, or location information beyond the city already public, or information unrelated to the Project. This license does not override the content standard in §10.4 or the safety-and-privacy process in §8.6, and the AP may remove, relocate, or restrict a repost as those sections require. The license survives completion or termination of the Project for archival purposes only. 10.2b Reposting by others; loss of control. Micheal Ray Berry acknowledges that once any Project content is public it may in fact be copied, reposted, shared, mirrored, altered, and reused by third parties anywhere, permanently and outside the control of either party, and that neither he nor the AP can guarantee its removal or recall from those third parties. This clause is an acknowledgment of that reality only; it grants no license or right to any third party, and it does not enlarge the AP's license under §10.2a. The AP retains and shall use the safety-and-privacy process in §8.6 to address unlawful, dangerous, or privacy-violating third-party reuse where reasonably possible.

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. The official public record — the material published on michealrayberry.com and the Official Platforms — is and remains safe-for-work: the project uniform provides full coverage, and no recording, photo, or log entry on the official record 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. Material violating this standard is not published on the official record; if discovered there, 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. 12.5 Additional or successor Accountability Partner. A person becomes an additional or successor Accountability Partner, and gains any authority under this Agreement, only through a written amendment signed under §12.1 that identifies them to the parties (their identity may remain private to the public under §12.2) and states the scope of their authority. Until such an amendment takes effect, no person other than the current Accountability Partner holds any authority under this Agreement, and no additional structure or requirement under §3.1 is effective.

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 — corner time of 10, 20, or 30 minutes by level — completed in the project uniform, recorded in one unbroken take, and verified by the Accountability Partner, together with a factual public log entry — date, requirement missed, status, submission and resolution timestamps, and verification result — that becomes part of the permanent public record. I understand that the corrective recording is published on the permanent record beside the entry that caused it, that completing the requirement closes the obligation without removing the recording, and that resolution of the entry does not remove it either. I understand that violations are declared automatically from objective evidence and that the Accountability Partner cannot excuse, soften, or downgrade one — only confirm or reject it against the written rules — and that I have a fixed 48 hours to contest with evidence before the determination stands. I understand that I must complete each corrective session within 72 hours of the notice, and that missing that deadline is itself a new violation at the next level. I understand that the Accountability Partner may set additional daily structure and requirements in support of the goal, that these are enforced on the same automatic terms as every other requirement, and that they are bound by the medical, safety, lawful, and non-sexual limits stated in §3.1. I understand that submitting the corrective recording resolves the entry, that the Accountability Partner may overrule and reopen it only on the written verification standard with a stated reason, and that resolution never erases the entry. I understand that my Project content is public and that I grant the Accountability Partner a license to repost, share, mirror, and archive it anywhere for the Project's accountability and documentation purpose, but not to sell, monetize, materially alter, or sublicense it for unrelated purposes (§10.2a). I understand and accept that, as a practical matter, public content may be copied and reused by third parties beyond either party's control (§10.2b). 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.

Signed and executed August 13, 2026 by both parties, and amended by agreement since. Signatures and the amendment record are held by the Accountability Partner. Day 1: August 13, 2026 · Declared starting weight: 340.0 lb · First filed weigh-in: 337.0 lb · Goal: 175.0 lb.