Core Contract: Domain Name

Purpose, owner and applicability

Name the domain and what it governs. State whether each rule applies project-wide, to a medium, or to a work. Keep named instances in Content.

Inputs and prerequisites

Link relevant contracts and explain what sufficiently defined input is required. Distinguish prerequisites from feedback and optional inputs.

Rules and limits

State reusable decisions, conditions, effects, costs, exclusions and exception criteria. Define the recognizable promise or convention where a causal formula would be inappropriate.

Contradiction tests

Explain how different proposed content entries can be checked against the rules. Record stable assumptions and what can evolve within them.

Unknowns and revision impact

Identify provisional decisions and intentional unknowns. For a revision, record its reason, affected contracts/content and review findings. Preserve creator approval through available conversation or Git; do not add a workflow status database.