Contraintes

Relations

• has_member → Disponibilité du service TT-CST-0001

Lifecycle

{
  "states": [
    "Draft",
    "Active",
    "Superseded",
    "Archived"
  ],
  "state": "Active",
  "initial": "Draft",
  "terminal": [
    "Archived"
  ],
  "transitions": [
    {
      "from": "Draft",
      "to": "Active",
      "trigger": "published"
    },
    {
      "from": "Active",
      "to": "Superseded",
      "trigger": "a newer version of this object is published"
    },
    {
      "from": "Active",
      "to": "Archived",
      "trigger": "withdrawn without a successor"
    },
    {
      "from": "Superseded",
      "to": "Archived",
      "trigger": "kept for the record and no longer served"
    }
  ],
  "assurance": "declared",
  "note": "The same four-state publication lifecycle every object in this record uses: it governs how this record's own entries are published and retired, not any business process."
}

Members

• TT-CST-0001

Scope

The constraints the site and program operate under.

Registered Types

• Constraint

Membership Rule

An object joins this registry only by being authored as a member here; nothing is added to a registry it does not also declare membership of.

Access Policy

{
  "read": "public",
  "write": "the owning role only",
  "note": "Every member of this registry is published on traffic-titans.com."
}

Retention Policy

{
  "current": "published",
  "superseded": "not published",
  "note": "The current version of each member is published. Superseded versions are not."
}

Versioning Policy

Each member carries its own version; the registry is versioned with the operating record.

Purpose

To hold the hard conditions that cannot be crossed.