Ethics
Supreme orientation — what must never be traded away for efficiency, compliance, or effect
Ethics is the supreme orientation of this project: the layer above values, principles, patterns, and mechanisms — what must govern them and what must never be traded away because a structure works, satisfies an auditor, or moves a metric.
The site tagline states it plainly: Ethics demands truth. Systems enable it. Ethics is not a softer alternative to engineering rigour; it is the reason rigour exists — so people are not harmed by coercion, deception, indifference, or records that lie.
Layer in the knowledge stack
Historically the stack was drawn as:
The dedicated Ethics collection is not yet published as a separate layer. Until it is, this term entry is the canonical link target for ethics in prose, maps, and the hero — so readers and authors have one place to land. Values and principles on the site already express much of what ethics demands; dark patterns name where structures violate it.
What ethics demands here
People as ends, not instruments. H0: Humane Core is the primary value expression: dignity, care in how truth is delivered, refusal of coercion and deception as design choices.
Truth that cannot be laundered. Truth and immutability of facts — committed records must not be rewritten for convenience; record falsification is failure, not hygiene.
Accountability with a name. Accountability and commitment requires authority — blameless pipelines and activity logs are not substitutes for who committed what, on what evidence, at which boundary.
Refusal of seductive violation. Dark patterns deliver their claimed effect while violating ethics and values — consent theatre, surveillance as accountability, metric substitution. Ethics is why they are listed for recognition and refusal, not imitation.
Judgment channels toward ethics
On the epistemic architecture map, judgment channels toward ethics, then values, then purpose and strategy. Technical capability — intelligence, models, harnesses — is insufficient without that channel: the Decision Strategy Framework and Artifact Classification describe how to match trust to stakes; ethics states why certain cells and mechanisms are forbidden regardless of efficiency.
At platform scale
Ethics must scale like security, architecture, and compliance — as platform guardrails, not a review ticket on every feature. The traditional shape is an ethics board on each release; the platform shape encodes refusal contours — dark-pattern checks, consent and surveillance boundaries, values-aligned release gates — so product teams ship in-set without waiting on a human gate per launch. Ethics remains single writer for the contour and for novel-harm exceptions; widening the in-set is not licence to ship seductive violation. See platform self-service and One Authority Per Invariant — At Scale.
Corpus stance
A2 — working context: Ethics as used here is the author’s orienting commitment for published work, not a complete moral philosophy or legal code. External traditions and workplace compliance frameworks may overlap; this entry names the epistemic-organisational spine the Genesis series and pattern library assume.
Promotion path A3 — open question: when ready, ethics may move to a dedicated /ethics/ layer with immutable adoption records (as sketched in knowledge-stack.md). Until then, link /terms/ethics/ and cross-link values, principles, and dark patterns rather than leaving “ethics” undefined in prose.