GPT Review — P44-3 Profile Registry Design Draft

Verdict

P44-3 đúng hướng nhưng cần polish trước khi upload. Điểm lớn nhất là phản biện ngược P44-1 F5 cardinality: đề xuất 0..n là hợp lý, nhưng không nên đổi tên F5 thành plural ở P44-1. Giữ logical field schema_profile_binding như một capability binding tổng quát, và trong P44-3 định nghĩa binding cardinality là multi-binding / 0..n. Tránh churn tên field không cần thiết.

Required polish

1. Q1: accept direction A, but soften implementation

   • Không dùng Cách B bundle.
   • Chấp nhận 1 family có nhiều profile entries.
   • Không đổi tên P44-1 F5 sang schema_profile_bindings ngay trong P44-3. Ghi feedback amend P44-1: F5 schema_profile_binding cardinality phải được hiểu là 0..n binding capability, không phải 0..1 scalar.

2. Không để Q1 block upload

   • P44-3 có thể upload với mục amendment candidate for P44-1 F5 cardinality.
   • Không sửa P44-1 rev 1 ngay nếu User chưa yêu cầu. P44-3 chỉ ghi rõ dependency/amend candidate.

3. Profile role vocab: avoid overfitting to information_unit

   • 4 defaults identity/content/publication/custom are acceptable for controlled draft.
   • Add note: publication is optional/domain-specific, not universal; other families may define roles via APR.

4. Required vs optional enforcement: soften default block

   • Required fields generally feed birth gate; enforcement mode should be declared per profile/family.
   • Avoid saying default block universally, because Đ44/L3 allow block/warn/escalate and some controlled-draft families may begin with warn/escalate.

5. required_g_set belongs to Family Registry but should not be patched now

   • Keep as amendment candidate for P44-1/P44-3 interface.
   • In P44-3, define it as a logical contract need, not as a finalized Family Registry field.

6. Non-binding information_unit sketches are useful but must remain clearly non-normative

   • Keep the sketches.
   • Add warning: no field name in §6 may be used as schema requirement until P38-X passes.

Direction

Opus should produce P44-3A polish with the six changes above, then upload knowledge/dev/laws/dieu44-trien-khai/design/03-profile-registry-design.md. Do not create decision logs. Do not update P44-1 yet. After upload, stop and ask whether to begin P38-X or P44-4.