Canon 0.6.0 freeze: ITC-CAP draft, AVT catalog, joinable review

Finish ITC-WP-0013 (AttributeValueType under ITC-DATA) and ITC-WP-0014
T02/T03/T05/T06/T07. Capability contract schemas, live-catalog review
CLI, landscape/kernel-map pointers. Sit on this version.

infospace/models/data/InfoTechCanonDataModel.md

@@ -26,6 +26,7 @@ This standard provides a canonical vocabulary for:
 - fields,
 - schemas,
 - data elements,
+- attribute value types,
 - code lists,
 - data stores as references,
 - data flows,
@@ -761,6 +762,30 @@ A **DataType** specifies the technical or logical type of a field or data elemen
 
 ---
 
+## 11.15a AttributeValueType
+
+An **AttributeValueType** is a closed, versioned, application-facing value
+type for structured capture. It names the type id, meaning, wire encoding,
+and whether a CodeList is required. It does not name a widget and it is not
+a competing entity with Attribute or Field.
+
+It is a closed profile of **Representation** for capture and forms.
+Constraint still owns required/format/cardinality. CodeList still owns
+permitted values. Email, phone, and percentage are not types.
+
+The catalog is `models/data/attribute-value-types.yaml`. Current ids:
+`text`, `text-long`, `date`, `time`, `datetime`, `amount`, `one-of`,
+`some-of`. Reserved: `boolean`, `integer`, `number`, `uri`, `identifier`.
+Legacy alias `textarea` normalizes to `text-long`.
+
+`amount` is structured `{value, currency}`. `one-of` / `some-of` require a
+CodeList; domain lists are not new types.
+
+**Provenance.** `demand/AttributeValueTypes.md` (citation-evidence),
+ITC-WP-0013.
+
+---
+
 ## 11.16 Constraint
 
 A **Constraint** is a rule limiting valid data.