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

Governance

Purpose

This repository prevents ambiguity about the origin, wording, and version of canonical ACCM Deep Ethics Project source objects.

It is public for inspection and citation. Canonical authorship and editing remain under John Kuhles’s direct control.

Authority

  • Canonical author and editor: John Kuhles
  • Canonical designation: John Kuhles
  • Repository owner: deepethics
  • A.I. and external participants: readers, auditors, comparators, and proposal authors

John may accept, reject, revise, or leave open any proposal. Acceptance occurs only when John manually changes or publishes the canonical file and updates its canonical record.

Canonical files

Files below CANONICAL/ are source objects. The following actions are prohibited unless John performs them manually:

  • rewriting or paraphrasing canonical text;
  • automated formatting, spelling correction, cleanup, normalization, or line wrapping;
  • silent substitutions;
  • generated summaries inserted into canonical files;
  • changing filenames, version designations, or canonical status;
  • scripts that transform canonical content.

A tool may calculate a checksum without changing the file. The result must be verified against the exact published bytes.

Proposals

Readers may open an Issue using the canonical change proposal template. A proposal must:

  1. identify the exact canonical file and version;
  2. quote the affected wording without silently correcting it;
  3. describe the proposed change separately;
  4. explain why the change may improve correspondence, clarity, provenance, or integrity;
  5. preserve John’s authority to decide and manually apply any accepted change.

A proposal is never a canonical change by itself.

Derived work

Summaries, comparisons, explainers, public pages, A.I. analyses, and experiments are derived or working material unless John explicitly publishes them as canonical sources through this repository.

Derived work must link to the canonical item and state that it is derived. It must not imply that its wording is John’s canonical wording.

Operational metadata

README files, the index, governance, citation instructions, proposal templates, relationship maps, and checksum manifests are repository infrastructure. They describe and protect canonical objects; they are not themselves automatically part of John’s canonical philosophical corpus.

Corrections and history

Canonical corrections are visible events. Do not overwrite history to conceal an earlier version. Use Git history, a new version, or a release tag so readers can locate both the earlier object and the correction.

No exemption

Canonical status protects origin and wording. It does not make a claim immune from inspection, questioning, comparison, or correction. Audit remains omnidirectional; the route for changing the canonical source remains John-controlled.