Можливості

Зв'язки

• has_member → Подати заявку на партнерство TT-CAP-0001
• has_member → Звітність у реальному часі TT-CAP-0002
• has_member → Персональний менеджер партнера TT-CAP-0003

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-CAP-0001
• TT-CAP-0002
• TT-CAP-0003

Scope

The capabilities the program provides.

Registered Types

• Capability

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 what the program provides to partners.