Why forkability preserves consent
Exit disciplines authority, repair gives voice, and forkability prevents coercive unity. A community that cannot leave, correct, or fork is structurally vulnerable to platform capture even when its public values sound open.
VNWO treats forkability as a civic design pattern. It does not compel a fork, assign legal ownership, or transfer private records without consent.
Fork triggers
Fork packet rules
Shared memory snapshot
Only export records that are public, scoped, consented, or otherwise portable under the network rules. Private memory and third-party records require separate consent or exclusion.
Identity continuity
Participants should know which profiles, names, reputation records, and public correction notices remain connected after separation.
Name and branding boundaries
A fork should state what names, symbols, domains, and public descriptions can travel and what must remain with the original network.
Non-retaliation
A peaceful fork should not trigger misleading labels, deletion theater, public smears, or hidden reputation penalties.
Forkability anti-patterns
- fork suppression through hidden ownership
- reputation capture
- export in unusable formats
- public smear labels after exit
- private archives used as leverage
- coercive unity framed as safety
Copyable fork packet
Fork packet: source_network=[name]; fork_created_utc=[ISO 8601 UTC]; exportable_records=[charter, public rules, scoped memory, public evidence]; non_exportable_records=[private memory and third-party records without consent]; name_boundaries=[limits]; public_correction_notice=[URL]; continuity_statement=[text]; non_retaliation_statement=[text].