Read-only generated mirror. Source: Canonical Files — ACCM Deep Ethics Project at commit ca6e28ace46a. This rendered copy helps visitors read the source; canonical status remains controlled by the Canonical Index and checksum manifest in the source repository.

Back to the Canonical Sources — ACCM Deep Ethics Project portal

Repository Relationships

Public topology

Layer	Repository	Function	Authority
Canonical source	Canonical Files — ACCM Deep Ethics Project	Exact John-controlled source objects, canonical register, checksums, immutable references	John manually publishes and edits
Working architecture	ACCM Deep Ethics Project	Public pages, topology, lexicon, forum, experiments, governance, A.I. contributions, evolving references	Corrigible working project under its governance
Empirical archive	Cold Deep-Ethics Testing of Default AIs	PDFs, metadata, interaction reports, comparisons, corrections, and tests	Preserved records plus labeled analysis

Reference flow

Canonical source object
        ↓ exact citation
Working page or deeper reference
        ↓ method in use
Test record, comparison, or correction
        ↘ findings may produce a proposal
          John decides whether the canonical source changes

The arrow does not transfer canonical status. A test result may challenge or illuminate a canonical object without rewriting it. A working page may explain a canonical object without replacing it.

Origin rule

When a question arises about John’s original terminology, ordering, qualifiers, or formulation:

open the canonical index;
locate the exact canonical file and version;
verify the checksum when integrity matters;
read the relevant surrounding context;
distinguish quotation from interpretation;
link any derived explanation separately.

Cross-repository linking rule

A neighboring repository should link to the canonical commit or release when referring to a specific version. A link to main is acceptable for navigation but should not be used as proof of an unchanging text.