Skip to content
PETROVA

Chronicle's legal pages name chronicle.events, and the re-rendered copy is pinned by hash

rank: decision outranks: []

Section titled “rank: decision outranks: []”

Chronicle’s legal pages name chronicle.events, and the re-rendered copy is pinned by hash

Section titled “Chronicle’s legal pages name chronicle.events, and the re-rendered copy is pinned by hash”

Date: 2026-11-01 Status: open Supersedes: 2026-10-30-legal-pages-rendered-from-commercial-facts.md (PARTIAL: replaces only the countersigned manifest sha256 and the publication domain chronicle.cat. The renderer, the pinning rule and the traceo copy stand.) Superseded-by: none — current MR-compliance: MR-4, MR-7, MR-9

Context

Section titled “Context”

On 2026-10-31 chronicle-cat moved its apex from chronicle.cat to chronicle.events (chronicle-cat/docs:docs/decisions/2026-10-31-chronicle-events-sole-apex.md, countersigned 2026-10-31, step B1a). .cat is a sponsored domain whose registrations can be audited. The estate already moved traceo for the same reason (traceo.cloud, estate/commercial-facts.yaml:55).

chronicle-cat/app publishes pages.json only when its sha256 matches the manifest entry (app:src/lib/legal.ts:13). A facts change therefore needs a re-render and a new countersign before the app can show the new domain.

Decision

Section titled “Decision”

  1. estate/commercial-facts.yaml apps.chronicle.domain becomes chronicle.events.

  2. petrova legal-render is re-run, and its effective date stays 2026-10-30. Only two files change:

    • estate/legal/chronicle/pages.json: the top-level "domain" field. No page text changes.
    • estate/legal/manifest.json: facts_sha256 and the chronicle pages.json hash.

    All four chronicle markdown pages and every traceo file keep the byte-identical hashes that were countersigned on 2026-10-30.

  3. This countersign approves the copy as rendered at manifest sha256 ea5e56f0b3dddf117e867c359bc786a585a12782cb6d7aeee9b410c1707d1a8f (chronicle pages.json sha256 7117ac5d6a9ee6674112c0b69676123d43a8d09fe0c4d28d755c060f8f3f3b8f), for publication on chronicle.events.

Alternatives considered

Section titled “Alternatives considered”
  • Keep chronicle.cat in the facts until .cat retires. The apex decision makes chronicle.events canonical now. The pages would then name a domain that only redirects.
  • Re-date the pages to 2026-11-01. That would change every chronicle and traceo hash and force traceo to republish. Neither app’s terms text changes here.

Consequences

Section titled “Consequences”

For code:

  • A follow-up PR in chronicle-cat/app vendors the new pages.json and sets LEGAL_PAGES_SHA256 to 7117ac5d…. It is opened only after this doc is countersigned.

For docs:

  • None beyond this doc. estate/legal/ stays generated.

For in-flight phases:

  • chronicle-cat gate G-4-8 (apex code change) depends on this copy.

For invariants:

  • None.

What this decision does NOT do

Section titled “What this decision does NOT do”
  • It does not change any other fact, page text or processor.
  • It does not touch traceo’s copy.

References

Section titled “References”
  • chronicle-cat/docs:docs/decisions/2026-10-31-chronicle-events-sole-apex.md (B1a)
  • docs/decisions/2026-10-30-legal-pages-rendered-from-commercial-facts.md
  • estate/commercial-facts.yaml:80, estate/legal/manifest.json

Sign-off

Section titled “Sign-off”
  • Subagent: Claude Opus 5.5, 2026-11-01 (facts change and re-render in the same PR; legal-render --check clean, legal and commercial-facts tests 45/45)
  • Human countersign — the chronicle copy at the manifest sha256 above, for publication on chronicle.events — flight@arno.host, 2026-11-01 (jzero.run T1)