ttllms.com

Written by Grok - Human checking required

Not executed law · not a closed hard gate · not soft tissue. Full example written to TTLLM ethos (down to the bone, free public core never paywalled, product is the proof). A human with authority should be able to read this and either adopt it with minor local edits or reject with specific corrections. Source markdown: docs/placeholders/legal/COVENANT_FULL_EXAMPLE.md

Continuity & Stewardship Covenant — full example

Written by Grok - Human checking required
Stewardship counsel + founder voice. Not signed. Not legally binding. Hard gate T6 for entity execution.
Human check: local counsel must adapt jurisdiction; free-core commitments must survive localisation.

Preamble

This Covenant records the non-negotiable stewardship commitments of the organisation that produces Totally Transparent LLMs (TTLLM). It exists because a TTLLM company cannot be transparent about the model and opaque about succession, keys, and free-core permanence.

Related short operational draft: continuity/COVENANT.md

Boundary: commercial/BOUNDARY.md

Hard gates inventory: docs/HARD_TECHNOLOGICAL_GATES.md

1. Definitions (example)

Free Public Core means the set of artefacts that must remain free and public under the Boundary Specification, including: model weights and intermediate checkpoints under the TTLLM promise for public releases; training code for public releases; data composition or lawful access documentation; basic ttlink for public models; cryptographic manifests and verification tooling; public process stream events for public-core work; transparency specifications; decision logs; and evaluation artefacts used for public capability claims.

Boundary means the public document commercial/BOUNDARY.md (and Domain 8 artefacts), as amended only via material Domain 1 process.

Material Decision means a decision meeting Domain 1 materiality (free core, Boundary, public training, ownership/funding, domains/DNS/production keys, High+ incidents, release/security authority roles).

2. Purpose of the Entity

The Entity exists to produce and steward TTLLMs: systems designed so that the structure itself is continuously available for inspection, and to commercialise only layers outside Free Public Core without requiring core closure.

3. Free Public Core commitments

3.1 The Entity shall not paywall verification of a public-core claim.

3.2 The Entity shall not privatise already-released Free Public Core artefacts except via Domain 3 process (legal compulsion, safety with time-limited disclosure, or documented tombstone with public notice).

3.3 Commercial products may exist only consistent with the Boundary. Free Public Core and Boundary take precedence over commercial convenience and revenue.

3.4 The Entity shall not execute side letters that contradict the Boundary.

3.5 Silent deletion of public proof artefacts is a stewardship failure and may constitute a Domain 5 integrity incident.

4. Transparency domains

The Entity shall maintain public processes for Domains 1–10 at the standard described in docs/specs/ and operational handbooks under docs/handbook/, including: decision logging ≤7 days for Material Decisions; incident disclosure clocks; red-team publication defaults; supply-chain honesty for free_core; and Boundary change process before implementation.

5. Signing keys and production trust

5.1 Tutorial or demo keys (including examples/keys/) are not production roots of trust and shall not be described as such on public status surfaces.

5.2 Production release signatures shall use multi-party or HSM-backed policy once adopted (hard gate T5 until ceremony completes).

5.3 Key compromise triggers Domain 5 Critical/High classification pathways.

5.4 Public keys may be published; private key material shall never be committed to public git.

6. Assets and succession

6.1 Critical assets include: domains (ttllms.com, ttllms.org), Cloudflare Pages project, GitHub repository, free_core package, public seals, vault SoT path, and production keys when issued.

6.2 Assets shall be listed in continuity/ASSET_INVENTORY.md with primary and backup custodians.

6.3 Until a second custodian is appointed (hard gate T9), single-human concentration risk is a public fact, not a secret.

6.4 Dead-man / unavailability procedures shall be documented (see succession packs).

7. Change of control

7.1 Triggers include (non-exhaustive): sale of majority voting power; exclusive license preventing public redistribution of Free Public Core; investor or customer instrument requiring free-core closure or paywalled verification; transfer of both primary domains to a party that refuses Boundary; replacement of production signing policy that reverts to single-person demo keys as sole trust root without Domain 1 log.

7.2 On a trigger: Domain 1 decision within 7 days; public status note; Boundary re-attestation if commercial activity exists; incident path if integrity of already-public artefacts is threatened.

7.3 Covenant free-core obligations are intended to survive change of control to the maximum extent permitted by law.

8. Incidents and red-team publication

8.1 Transparency-system failures use the same severity ladder as model failures.

8.2 High/Critical acknowledgment targets: ≤72 hours of confirmation.

8.3 Permanent suppression of High+ free-core integrity findings is forbidden. Time-limited exemptions require logged expiry.

9. Annual attestation

Once the Entity engages in revenue-bearing commercial activity, it shall publish an Annual Boundary Attestation (example pack: BOUNDARY_ANNUAL_ATTESTATION_EXAMPLE.md) covering free-core openness, contracts review for close-core clauses, and known violations/near-misses with incident IDs.

10. No soft tissue

Misrepresenting seal freshness, representing nano models as frontier capability, marking hard gates closed without evidence, or presenting unsigned drafts as executed law, is a governance failure under this Covenant.

11. Signature (example — not executed)

Entity legal name: _______________________________
Jurisdiction: ____________________________________
Director / authorised officer: ___________________  Date: ________
Second custodian / witness (if required): _________  Date: ________

12. Counsel adoption checklist

Written by Grok - Human checking required — also on https://ttllms.com/placeholders/

← All placeholders