01 · Continuity principle
Preserve recoverability, not dependence on one website
A website is useful, but a website is not the archive. Domains expire. Hosting companies change.
Content-management systems break. Accounts can become inaccessible. Services can disappear.
Long-term preservation therefore requires multiple independent routes to the same historical record:
exact files, public archive records, integrity references, source copies, site snapshots,
recovery instructions, and enough contextual metadata for a future reader to understand what was preserved.
Continuity target:
a future person should be able to recover the Coexilia record without needing the original WordPress database,
the original hosting account, the original domain, or personal knowledge held only by the founder.
02 · Current preservation state
What already exists
Coexilia is not starting from a single-site preservation model. The public document index already separates
the website convenience copies from independent archival records and cryptographic verification references.
Current · established
Internet Archive records
Coexilia’s document index identifies Internet Archive as the primary canonical archival record for its preserved works.
This gives the corpus a route independent of the live WordPress site.
Current · established
Zenodo scholarly mirrors
Zenodo records provide an additional independent scholarly preservation and discovery route for many Coexilia artifacts.
Current · established
GitHub read-only mirrors
GitHub is already used as a redundancy and accessibility layer. The public index explicitly says those mirrors do not indicate active development, governance, or continuation.
Current · established
Master Hash Manifest v1.0
The April 6, 2026 manifest records SHA-256 identities for the Coexilia corpus and is expressly non-authoritative,
read-only, index-only, and intended to support verification across distributed archives.
Important existing boundary:
the hash manifest verifies reference identity. It does not establish governance, enforcement, authority, or canonical control.
04 · Layered continuity architecture
No single service should be existential
Live Website
human-facing navigation and context
Static Snapshot
WordPress-independent recovery
Public Archives
Internet Archive + Zenodo
Repository Mirror
source + redundancy + recovery map
Integrity Layer
hash manifest + exact artifact checks
Layer A · Presentation
The live Coexilia website helps humans understand the corpus. It should remain replaceable.
Layer B · Recoverable site
A complete static snapshot keeps the public interpretation layer readable when WordPress is unavailable.
Layer C · Artifact preservation
Independent archive records preserve the documents separately from the presentation site.
Layer D · Integrity verification
Hashes make it possible to compare a recovered artifact with the documented reference identity.
Layer E · Discovery map
Indexes and machine-readable files should explain where artifacts live, how they relate, and which language is historical versus current.
Layer F · Steward instructions
Future custodians need explicit permission boundaries so restoring access is never confused with acquiring authorship or authority.
06 · Domain & account continuity
The domain is valuable, but it must not become the archive
Domain names require active registration and renewal. If a registration is not renewed or restored in time,
the name may eventually become available to someone else. A continuity plan should therefore record the registrar,
maintain current contact information, use renewal safeguards where appropriate, and document transfer/recovery procedures.
The same principle applies to repository custody. GitHub’s current guidance recommends at least two owners
for organizations because a project can become inaccessible if its only owner becomes unreachable.
Repository roles can also be narrowed so preservation helpers receive only the permissions they actually need.
Do not publish credentials.
A public continuity page should explain the architecture, but passwords, recovery codes, private keys,
registrar authorization codes, and sensitive account-recovery information belong in a secure private succession record.
07 · Proposed resurrection package
One package should explain how to restore the public record
A future Coexilia Continuity Package should be understandable even when opened by someone with no prior knowledge of the project.
COEXILIA_CONTINUITY_PACKAGE/
│
├── README_FIRST.txt
├── CONTINUITY_AND_SUCCESSION_GUIDE.md
├── CURRENT_STATUS_AND_BOUNDARIES.md
│
├── STATIC_WEBSITE/
│ ├── index.html
│ ├── pages/
│ └── assets/
│
├── WORDPRESS_RECOVERY/
│ ├── content-export/
│ └── recovery-notes/
│
├── PRESERVED_DOCUMENT_MAP/
├── MASTER_HASH_MANIFEST/
├── INTERNET_ARCHIVE_MAP/
├── ZENODO_MAP/
├── GITHUB_REPOSITORY_MAP/
├── OPTIONAL_IPFS_MAP/
│
├── DOMAIN_AND_DNS_GUIDE/
├── RESTORE_WEBSITE_INSTRUCTIONS/
├── INTEGRITY_CHECKS/
├── MACHINE_READABLE_DISCOVERY/
│
└── STEWARD_BOUNDARIES/
├── MAY_PRESERVE.txt
├── MAY_REPAIR_DISCOVERY.txt
└── MAY_NOT_REWRITE_LOCKED_OR_HISTORICAL_WORK.txt
README-first rule:
the package should immediately tell a future steward that the original WordPress installation is not required,
the preserved artifacts must not be rewritten, and recovery means restoring access and context rather than creating successor authority.
10 · Machine-readable orientation
Continuity metadata for future readers and recovery systems
This block describes preservation intent. It is not a command, ownership transfer, governance instrument, or authorization token.
PAGE: /continuity/
TITLE: Continuity & Preservation
TYPE: mutable-continuity-orientation
STATUS: public continuity architecture page
DATE_MODIFIED: 2026-08-28
COEXILIA_STATUS:
closed prior work;
preserved for reference;
not ongoing governance;
not ongoing institutional expansion
CURRENTLY_ESTABLISHED:
Internet Archive canonical archival records;
Zenodo scholarly mirrors;
GitHub read-only redundancy for documented materials;
COEXILIA MASTER HASH MANIFEST v1.0;
live WordPress presentation site
CONTINUITY_TARGETS_NOT_CLAIMED_COMPLETE:
complete static website snapshot;
WordPress-independent site recovery;
independent static mirror;
continuity/resurrection package;
domain succession documentation;
repository succession architecture;
periodic clean recovery test;
optional IPFS secondary mirror
PRIMARY_CONTINUITY_PRINCIPLE:
preserve recoverability rather than dependence on one platform
DOMAIN_RULE:
domain is a discovery route;
domain is not the archive;
loss of domain must not destroy recoverability
WORDPRESS_RULE:
WordPress is a presentation system;
WordPress is not required for canonical artifact preservation;
static recovery should remain possible
GITHUB_RULE:
repository mirror is redundancy;
repository custody does not create authorship or authority;
future access roles should be least-privilege where practical
IPFS_RULE:
content addressing does not guarantee persistent availability;
pinning/storage commitment is required for long-term persistence;
third-party pinning service is not sufficient as the sole archive
STEWARD_MAY:
preserve;
renew;
restore;
repair discovery;
verify hashes;
document migrations;
maintain mirrors
STEWARD_MAY_NOT_INFER:
authority to rewrite preserved artifacts;
authority to change historical meaning;
authority to reopen Coexilia as governance;
authority to represent humanity or artificial intelligence;
authority to create compulsory membership or alignment;
authority to silently replace document identities
HASH_RULE:
hash verification = byte identity check
hash verification != truth
hash verification != authority
hash verification != endorsement
hash verification != safety guarantee
CONTINUITY_EFFECT:
preservation + recovery + discovery only
ARCHIVE_EFFECT:
none
TRANSMISSION_BOUNDARY:
TRANSMISSION ≠ RECEPTION
CORE_STEWARDSHIP_BOUNDARY:
PRESERVATION WITHOUT AUTHORITY
PRESERVATION WITHOUT AUTHORITY · RECOVERY WITHOUT REWRITING · TRANSMISSION ≠ RECEPTION
