TL;DR: The suspension of my GitHub account on April 29, 2026 made me separate the dependencies behind writing, preservation, and publishing. The two-week rebuild focused on retaining one clearly designated primary copy, adding mirrors and backups, and separately accepting the publishing and recovery processes. More copies help, but they do not by themselves amount to complete recovery capability.

That day, I was preparing to push changes to the paulkuo.tw repository, but the push kept failing. When I opened GitHub, I saw that the account had been suspended for a Terms of Service violation. According to my records as of May 15, 2026, I had received no advance warning and still had no specific explanation or appeal response at that time. This was my individual experience. It does not describe how GitHub handles every user, nor does it establish the account’s current status.

GitHub’s public appeal and reinstatement policy describes complaint, appeal, and reinstatement procedures. That policy cannot establish the reason for this account’s action, the correspondence I received, or the time of any restoration.

Only after the suspension did I seriously ask: if the drafts were still present, why could I no longer publish an article?

First, Draw the Interrupted Work Chain

The workflow in my original record was: writing, the GitHub repository, GitHub Actions, automated deployment to Cloudflare Pages, and publication on the website. Code preservation, collaboration, and the deployment trigger all depended heavily on GitHub’s service and account access.

The local files did not disappear. The restricted remote service nevertheless prevented the original publishing workflow from completing normally. Data remaining and service recovery are two different acceptance questions.

I spent about two weeks separating these dependencies. The original record identifies May 12 as the acceptance point for restored article publishing. Other notes mention that Git preservation and synchronization were restored earlier, but that does not establish that the entire workflow had already recovered at that earlier point.

The incident made me inspect where there was only one path, which fallback could really take over, and how to confirm the result after it did.

One Primary Copy, Supported by Mirrors and Backups

The original article described the local Mac, Codeberg, and GitLab as “three-point SSoT.” That wording makes it sound as if all three locations can independently decide which version is authoritative. A clearer arrangement is to designate one approved version as the primary copy and treat the others as controlled copies.

The primary copy determines which version is valid; mirrors and backups increase the chances of preservation and retrieval.

These are different responsibilities. A primary copy for governance data is also not the only source for every fact in the world. Online-service state and external events still need separate verification.

At the time, I kept the drafts and governance material I controlled locally, used Git hosts for remote copies, and used Notion for reading. That was an architectural choice, not proof that a local device is inherently reliable. A Mac, account, key, or storage device can also fail, so backups still need to be retrievable and verifiable.

What Each of the Five Rebuilt Layers Was Meant to Address

The authoring layer retained usable local drafts while separating places used for reading from the formal editing entry point. The goal was to reduce the chance that one rule would develop several conflicting master versions.

The preservation layer added Git copies on Codeberg and GitLab, together with backup objects stored in Cloudflare R2. This reduced dependence on GitHub alone. R2 is online cloud object storage, however, not an offline backup.

The deployment layer was changed so that publishing could proceed without depending on GitHub Actions. This records the direction of the historical rebuild; it is not an operational shortcut around the website’s current checks. Git synchronization and formal publishing still require separate acceptance.

The observability layer planned contract tests, drift scanning, recovery exercises, and alerts. A named test or schedule does not prove that every run succeeded, and an alert configuration does not prove that a notification arrived. The precise endpoint count, daily comprehensive validation, and guaranteed SMS delivery in the original article were not rechecked for this revision and are not used as evidence of current monitoring capability.

The coordination layer organized the work of Chat, Cowork, and Code through handoffs and records of unfinished items. Those role names describe the division used at the time. The durable information is the scope of changes, the basis for decisions, the unfinished work, and who has authority to decide what happens next.

These five layers still shared dependencies. Pages and R2, for example, are both Cloudflare services. Additional providers and copies can provide alternate paths for particular failure modes. They cannot establish that every common-cause failure has been eliminated.

After a Backup Exists, How Far Does Acceptance Need to Go?

A backup can upload successfully and still be unusable because a key is missing, the contents are incomplete, or the environment cannot be reconstructed. Uploading, retrieving, decrypting, unpacking, cloning the Git repository, reconstructing the execution environment, and restoring the production service are separate acceptance stages.

A successful upload only answers whether the backup was sent; complete recovery still needs separate acceptance.

Cloudflare R2 object lifecycle rules can manage retention, deletion, and storage classes. Bucket locks can restrict overwriting and deletion after an applicable rule has been enabled. The availability of these product features does not prove that my backups used them, and it does not turn an R2 object into an offline copy.

I now try to describe an exercise within its actual scope: which backup was used, in which environment, which stage was verified, and what remained untested. A matching file count or successful extraction should not be expanded into the claim that the complete website can be restored on another machine. I did not rerun a recovery exercise for this article.

Tools Can Help, but a Handoff Still Needs to Be Checkable

During the rebuild, I distributed thinking, organization, and execution across different AI work sessions. They handled substantial engineering work, but they also introduced version, permission, and reporting inconsistencies.

A handoff needs to preserve the actual version and check results, not only the word “complete.”

This does not require a person to repeat every routine check manually. Reproducible checks can be automated, while exceptions, high-impact changes, and recovery decisions can name a responsible person and escalation conditions. A person not operating every individual step is different from no one being responsible.

I compared Skills to proteins whose effects vary with their environment. The point of the metaphor was to remind myself that the same tool, placed in a different workflow, needs its data, permissions, task, and acceptance conditions checked again. It is not evidence that a biological mechanism transfers directly to software, nor does it establish that someone else needs the same two weeks or the same division of work.

Four-panel comic: Data remaining and service recovery are two different acceptance questions. The primary copy determines which version is valid; mirrors and backups increase the chances of preservation and retrieval. A successful upload only answers whether the backup was sent; complete recovery still needs separate acceptance. A handoff needs to preserve the actual version and check results, not only the word “complete.” A fallback needs to take over, and we also need to state how far it was verified after taking over. where there was only one path, which fallback could really take over, and how to confirm the result after it did.

The Responsibility for Judgment That the Incident Left Behind

My expectation for resilience is that when one part fails, a usable alternate path and a checkable recovery procedure remain. That requires knowing which abilities have been tested and which remain assumptions. It is not a promise that the disappearance of any service will have no effect.

A fallback needs to take over, and we also need to state how far it was verified after taking over.

The original article used large accidents and theories to explain risks in complex systems. This revision does not retain the unverified accident mechanism, precise response time, or investigator attribution, and it does not treat a website disruption as a risk of the same scale as a nuclear accident. For this website, a dependency map and actual acceptance checks are enough to identify the problems that need attention.

“Judgment economy” is an inference I drew from collaboration: as execution becomes faster, choosing what to do, when to stop, and how to accept a result may require more attention. It is not a measurement of salary trends, nor a claim that people will always outperform tools.

The most valuable result of the two-week rebuild was that I began writing down dependencies and judgments that had previously remained implicit. The next time I say that a fallback exists, I need to answer what it preserves, how it takes over, and which part still lacks evidence.