OPEN SPECIFICATION

Ethica should be readable as an argument — and reviewable as a system.

The book, system specification and prototypes are distinct layers. They should evolve together without confusing a demonstration interface with law or a live public service.

01

Main work

The argument, history, sources, objections and normative model.

02

System specification

Versioned roles, mandates, data flows, security boundaries, metrics and assurance requirements.

03

Reference prototypes

Runnable demonstrations that make parts of the model testable without pretending to be production.

04

Legal implementation

Any future real implementation requires democratic mandate, legislation, impact analysis and independent review.

Change without rewriting history

Changes to baseline parameters — such as the four-year cooldown, council duration or reserve model — should be published as explicit version steps. A new proposal does not erase evidence of what the previous version actually said.

Licensing terms for public text and code have not yet been selected in this launch candidate. The portal therefore describes Ethica as an open specification in a methodological sense without claiming a legal open-source or Creative Commons licence that has not been chosen.