Purpose

Define how laws, delegated orders, technical standards, Schemas and Registries acquire, change and lose legal effect, preventing lower-layer technical implementation from silently becoming law.

PART I｜LAWMAKING

1. Constitutional Basis

Every L2 Act / Code must conform to the Constitution / Fundamental Rights Charter.

2. Enactment Record

A formal law must record at least:

  • law_id
  • title
  • constitutional authority
  • enacting body
  • effective_from
  • jurisdiction_scope
  • amendment history
  • supersession status

3. Public Deliberation

Ordinary legislation should include a public proposal / review / objection period or an equivalent civilizational procedure; emergency exceptions require later ratification/review.

4. Amendment

A legal amendment may not be carried out covertly through a glossary, technical profile, FAQ or implementation note.

PART II｜DELEGATED RULEMAKING

5. Delegation

An L3 regulation must have explicit enabling authority in its parent law, including:

  • subject matter
  • purpose
  • scope
  • permitted sanctions/effects
  • limits

6. No New Fundamental Restriction by Regulation

Unless authorized by the parent law, an administrative order may not create a new major restriction of fundamental rights, criminal punishment, permanent personhood downgrading, or compulsory neural intervention.

7. Reasons / Evidence

A material regulation should explain its purpose, evidence, expected effects, rights impact and alternatives.

8. Sunset / Review

High-risk, new-technology, emergency or predictive governance rules should in principle include a review date / sunset.

PART III｜STANDARDS INCORPORATION

9. Standard ≠ Law by Default

An S3/S4/S5 technical standard/profile/schema/registry does not automatically become legally binding merely because it is widely used.

10. Incorporation by Reference

If law makes a technical standard mandatory S2, it must expressly state:

  • exact standard_id
  • version
  • incorporated sections
  • legal purpose
  • affected population/system
  • effective date
  • alternative/exception process

11. Version Pinning

'Comply with the latest standard' may not operate as unlimited dynamic delegation. Material rights effects require pinning an exact version or providing a clearly bounded auto-update procedure.

12. Standard Update

Updating a technical standard does not automatically change existing legal effects. If a new version changes legal duties, eligibility, criminal exposure or rights thresholds, incorporation review must be completed again.

13. Schema / Registry Boundary

A Schema enum, machine key, default value or validation rule may not independently create a legal classification not authorized by higher-order law.

PART IV｜EMERGENCY RULEMAKING

14. Emergency Rule

Must state:

  • triggering condition
  • constitutional/statutory authority
  • scope
  • start/end
  • rights affected
  • review
  • sunset

15. No Permanent Emergency by Reissuance

Successive short-term emergency rules may not be used to evade ordinary legislative procedure.

16. Post-Emergency Ratification

If an emergency rule is to remain in force long term, it must return to normal lawmaking.

PART V｜CONFLICT / HIERARCHY

17. Conflict Priority

C0 Constitution > C1 constitutional interpretation > L2 Act/Code > L3 regulation > L4 individual order.

Technical S2 binds only within the scope of incorporation; S3-S5 remain technical unless incorporated.

18. Later vs Higher

A newer lower-order rule cannot override an older higher-order rule merely because of its later date.

19. Local / Temporal Scope

Laws, orders and standards references must preserve location, population, version, deployment phase and temporal scope where needed, consistent with Soul v3.7 §2.4.1.

PART VI｜MACHINE-READABLE LAW

20. Legal Source of Truth

A machine-executable representation of law must point to the human-legible authoritative text and version.

21. Compiler / Binding

Machine binding may execute law but may not silently reinterpret it; a semantic mismatch must fail closed / request review rather than invent law.

22. Audit

Every law-to-machine-binding transformation must preserve compiler/version/mapping/audit records.

PART VII｜REPEAL / SUPERSESSION

23. Supersession Chain

A repealed / superseded law retains its historical text, period of effect and reason for change.

24. Derivative Update

After amendment, affected regulations / standards / schemas / registries / public guidance should be identified; the principal law may not be changed while downstream systems continue executing obsolete rules.