0. Plain Statement

Coherence is trajectory-based, not snapshot-based.

Plain-language version:

Coherence is trajectory-based, not snapshot-based.

1. Formal Definition

Coherence Trajectory Law is currently defined by the source registry excerpt below. This scaffold awaits editorial expansion into the full law spec sheet format.

2. Canonical Form

coherence evaluation ⇒ dO/dt under load

Related variables:

TBD

3. Core Mechanism

TBD. Expand from the source excerpt and related UTS modules during editorial review.

4. When This Law Applies

TBD. Define applicability conditions during editorial review.

5. When This Law Does Not Apply

TBD. Define boundary conditions and false-positive cases during editorial review.

6. Diagnostic Signature

TBD. Map diagnostics only when supported by source material or later canon updates.

7. Failure Pattern

TBD. Map failure patterns only when supported by source material or later canon updates.

8. Restoration Implications

TBD. Map restoration arcs only when supported by source material or later canon updates.

9. Design Rule

TBD. Add design rules during editorial review.

10. Cross-Scale Expressions

TBD. Add U-layer expressions during editorial review.

11. Examples

TBD. Add examples during editorial review.

12. Relationship to Nearby Laws

TBD. Add related laws and deduplication notes during editorial review.

13. Operator Mapping

TBD. Add operator mappings during editorial review.

14. Machine-Readable Summary

id: "LAW-002"
name: "Coherence Trajectory Law"
type: "law"
status: "draft"
family:
  - "Core"
summary: "Coherence is trajectory-based, not snapshot-based."
canonical_statement: "Coherence is trajectory-based, not snapshot-based"
canonical_form: "coherence evaluation ⇒ dO/dt under load"
source: "content/archive/laws/technical.md"

15. Compact Card Version

LAW-002 — Coherence Trajectory Law

Coherence is trajectory-based, not snapshot-based.

Plain meaning: Coherence is trajectory-based, not snapshot-based.

Canonical form:

coherence evaluation ⇒ dO/dt under load

16. Source Status

This scaffold was generated from the current laws technical registry. Sections marked TBD should be expanded only from source material, related canon pages, or later editorial review.

17. Source Excerpt

Coherence is trajectory-based, not snapshot-based.

A system cannot be evaluated by a single state, claim, metric, event, output, credential, ritual, policy, benchmark, or appearance of calm.

Coherence must be evaluated across:

• time
• stress
• transformation
• recurrence
• perturbation
• ring-down
• hidden debt behavior
• cross-scale outcome

Canonical form:

coherence evaluation ⇒ dO/dt under load

A system is coherent when identity, meaning, boundary integrity, auditability, and functional integrity persist or improve across transformation without exporting hidden debt.