Every revision to the Founder Continuity & System Safeguard Protocol is recorded here. Entries are never edited and never removed. To verify any continuity announcement, see /continuity/verify.

Continuity Protocol Changelog

Append-only. Every change to the protocol is recorded here, oldest first. Entries are never edited or removed.

Entry 0 — Aarambam · Founding

Action: Protocol drafted and published as reference architecture.

What was set:

Eight protected laws (System Law Lock).
Six continuity levels (0 — Normal through 5 — Permanent Continuity Mode).
Seven Continuity Council roles, all sealed (no holders).
Founder Legacy File defined as sealed-and-offline; opening requires four approvals.
Takeover risks and controls documented.
Public Distance Modes (Visible / Architect / Silent Steward / Continuity).
System Survival Checklist across Legal, Technical, Finance, Governance, Public, Sensitive.
Per-system continuity rules for Domains, Technical, Treasury, Starter Card, VinMin, MOZI, Aayvu, Thayagam, Velicham.
Public Continuity Statement published at /continuity.
Empty continuity_events table created — no events recorded.

What was deliberately not built:

No live inactivity timer.
No notification engine.
No council-approval UI.
No real Legacy File contents on the site.

Reviewer: Founder. Status: Active reference. No live activation.

Entry 1 — Aarambam · Licensing Firewall added

Action: Clause 9 (Licensing Firewall) added to the Continuity Protocol. Published on /continuity-guard and referenced from the Becoming-layer papers /critical-research/parliamentary-pathway and /critical-research/distributed-spine.

What was set:

TLTE C.I.C. may license Governance OS, Velicham, Aayvu, evidence registry, citation system, and continuity infrastructure to any lawful political vehicle that adopts the Seven Sacred Rules and the two-layer rule.
TLTE does not own, control, fund, or direct any licensed vehicle.
Each licensed vehicle registers under its own jurisdiction's law and is governed independently.
No licensee may advocate or glorify political violence.
Inclusion of Hill-Country Tamils, East Coast Muslims, and Sinhalese democrats is mandatory on any licensed platform.
Any licence may be reviewed and revoked in writing by the Continuity Council, with public reasons.

What was deliberately not built:

No licensee exists.
No licence has been issued.
No political party is registered, sponsored, owned, or funded by TLTE.

Reviewer: Founder. Status: Active reference. No live activation.

Entry 2 — Aarambam · Move #3 (EU GSP+ Compliance Desk) anchored

Action: The Recorded Legal Memory work (Move #4) and the EU GSP+ Compliance work (Move #3) are added to the protected-instruments list governed by the Continuity Protocol. Their multi-community rules become protocol-grade — they cannot be silently removed by any future steward.

What was set:

The EU GSP+ Compliance Desk and MP Pack #6 are protected civic instruments.
Hard rule fixed in protocol: TLTE never asks the UK, EU, or any MP/MEP to call for GSP+ withdrawal. This may not be reversed without a public Continuity Council resolution.
Hard rule fixed in protocol: every Tamil-specific labour citation on the GSP+ surface must be paired with at least one Eastern Muslim and one up-country labour citation.
MEP fork (MP Pack #6.5) authorised — same instrument adapted for the European Parliament cycle leading to 1 January 2027.

What was deliberately not built:

No direct intake from Sri Lankan apparel workers, estate workers, or Eastern Province workers — TLTE routes to ILO / OHCHR / credentialed unions only.
No "Tamil GDP" or aggregated trade-loss figures.

Reviewer: Founder. Status: Active reference. Public.

Entry 3 — Aarambam · Move #4 (Recorded Legal Memory Desk) anchored

Action: The Recorded Legal Memory Desk (/unmai/desk/legal-memory), the 5-custodian Archive Map, and MP Pack #7 (tamil-legal-memory) are added to the protected-instruments list. The Soulbury (1945) and Donoughmore (1928) commission reports are added to the citations registry to close the 1806 → 1947 continuity chain.

What was set:

The 1706 → 1806 → 1947 → present-day continuity is fixed as the legitimacy spine of the desk.
Hard rule fixed in protocol: the Dutch and British colonial administrations are described as record-keepers, never as authorities — Tamil Mudaliars are the legal authors. May not be silently reversed.
Hard rule fixed in protocol: TLTE defers all reform of Thesawalamai content to Magalir Avai. The diaspora and this desk recover the fact of codification only.
Hard rule fixed in protocol: TLTE never asks the UK, the Netherlands, or any MP/MEP to recognise Tamil statehood or to support restoration of Thesawalamai content.
MEP fork of MP Pack #7 reserved (mp-pack-tamil-legal-memory-mep dossier slug registered for future fork).

What was deliberately not built:

No Tamil-customary-law revival project. The desk recovers the record; reform is for the homeland and for Magalir Avai.
No claim that Tamil land or sovereignty was "granted" by any colonial power. The wording is "recorded".

Reviewer: Founder. Status: Active reference. Public.

Entry 4 — Aarambam · Phase P3: Second Witness · Stewardship Register stub · first Recall dry-run

Action: Three procedural anchors are added on the same era-stamped revision. They take the Continuity Protocol from "written" to "exercised once on the public record".

What was set:

A second Witness is recognised on this entry. Entries 0 → 3 carried a single reviewer (the Founder). From Entry 4 onward every protocol revision is co-witnessed: Witness A (Founder) and Witness B (a Continuity Witness, recorded by sealed identifier until the era-2 rotation opens that seat for confirmation). The two-witness rule is now binding for all future entries — no single hand may edit the protocol.
The public Stewardship Register stub is published at /stewardship-register. It declares, with honesty, that during the founding era most seats are sealed and report "0 confirmed holders". The Register's schema — what it commits to publish at each cycle — is fixed now so no future steward can quietly narrow it.
The first Recall procedure dry-run is published at /recall-dry-run. The recall mechanism described in /accountable-stewardship is exercised, end-to-end, against a hypothetical Charter violation. No real person is named. The dry-run proves the procedure is operable; it does not open a real recall.

What was deliberately not built:

The second Witness identity is not disclosed by name. Personal-safety convention applies until the Stewardship Register opens the seat for public confirmation.
The Stewardship Register does not list real human beings during Aarambam beyond the Founder. Sealed seats are shown as sealed.
The Recall dry-run is not a real proceeding. No respondent, no complainant, no jurisdictional claim.

Reviewer A (Founder): witnessed. Reviewer B (Continuity Witness, sealed identifier cw-02-aarambam): witnessed. Status: Active reference. Public.