dot-iu-cutter v0.1 — UOSL / Đ44 Compatibility Note (D7)

Date: 2026-05-15 Status: DESIGN DRAFT Baseline: rev5d §3.5 Scope: DESIGN ONLY. UOSL is a controlled draft; do not treat fields as enacted.

---

1. Purpose

Map cutter design surfaces (D1–D6, D9, D11) to UOSL / Đ44 concepts so the cutter remains schema-compatible as UOSL matures. Flag every unmapped field as a schema gap, not a silent assumption.

2. Scope

• UOSL concept inventory: OQC, G1–G12, Family Registry, Relation Layer, Maturity M0–M4, IU profile
• Mapping table: cutter design field ↔ UOSL concept
• Compatibility flags
• Identified schema gaps

Out of scope: enacted-law-only design; UOSL revision proposals; DDL.

3. Dependencies

• rev5d §3.5 (Đ44/UOSL guardrail)
• UOSL v0.1.2 controlled draft (Đ44/UOSL)
• D1–D11 (consume mappings)
• Đ24 (vocabulary boundary), Đ33/Đ43 (PG placement), Đ39 (universal_edges Relation Layer)

4. Key Decisions

4.1 UOSL Is a Controlled Draft (rev5d §3.5)

• UOSL is currently the compatibility target, not enacted law.
• Cutter design MUST align with UOSL concepts where applicable.
• Unmapped fields → schema gap; do NOT assume enacted-equivalent.
• This deliverable is conceptual mapping only; no DDL.

4.2 UOSL Concept Inventory (v0.1.2)

Concepts referenced by rev5d §3.5:

Concept	Role
OQC	Object Qualifying Core — minimal identity fields
G1–G12	Field groups defining object semantics
Family Registry	Object family classification
Relation Layer	universal_edges-compatible relation graph (Đ39)
Maturity M0–M4	Object maturity ladder
IU Profile	Expectations for Information Units specifically

4.3 Mapping Table — Axis-1 / Axis-2 Fields → UOSL

Cutter field	UOSL hint	Mapping confidence	Notes
canonical_address	G1 identity	High	New field; needs DDL gap
source_path	G1 / OQC	High	Likely present
source_revision	G1 / OQC	High	Existing
source_span_start/end	G3 source representation	Medium	New field
render_order	G4 publication	Medium	New field
parent_unit_id	G3 hierarchy	High	Existing
publication_membership	G4 publication	High	Existing
body_source_policy	G3 representation	Medium	New field
section_type	G2 classification (Đ24)	High	Existing in profile JSON
unit_kind	G2 classification (Đ24)	High	Existing
classification_labels	G2 classification (Đ24)	Medium	Multi-value JSON or table
semantic_role	G6 semantics	Medium	New field
candidate_edges	Relation Layer (Đ39)	High	Prefer universal_edges with status
edge_readiness_notes	Relation Layer	Medium	JSONB on unit
universal_edges_compat_flag	Relation Layer	Medium	New field
vector_projection_readiness	Outside UOSL core	N/A	Indexing-side concern
thread_hint	Relation Layer / Family Registry	Medium	New field
lifecycle_stage_hint	Family Registry / G2	Medium	New field
risk_class	G5 governance	High	New explicit field
authority (enacted/draft/runtime)	G5 governance	High	Đ0-G distinction
visibility / readiness / publication_state	G4 / G5	Medium	Audience access fields
reviewer_identity	G7 provenance	Medium	New field

4.4 Manifest Family Mapping → UOSL

Cutter object	UOSL family hint	Notes
Manifest envelope	New family (Decision Artifact?)	Likely outside current Family Registry
Review decision	New family (Governance Event)	Family Registry gap
Cut change-set	New family	Family Registry gap
Verify result	New family	Family Registry gap
Report envelope	New family	Family Registry gap

These are NEW object families. They need Family Registry entries or explicit waiver. Recorded as schema gaps.

4.5 Threading Family Mapping → UOSL

Cutter object	UOSL family hint	Notes
semantic_thread	New family (Living Concept?)	Family Registry gap
semantic_thread_membership	Relation Layer (universal_edges)	Prefer reuse
semantic_thread_candidate	Pending state of membership	Lifecycle vocabulary
semantic_thread_evidence	New family (PROV record)	Family Registry gap
semantic_thread_negative_knowledge	New family	Family Registry gap
semantic_thread_health_signal	New family (Signal Event)	Family Registry gap
semantic_thread_expected_chain	JSONB on thread	Field, not family

4.6 Retrieval Family Mapping → UOSL

Cutter object	UOSL family hint	Notes
retrieval_metric_event	New family (Instrumentation Event)	Family Registry gap
search_gap_signal	New family (Signal Event)	Family Registry gap
audience_filter_policy	New family (Policy)	Family Registry gap

4.7 Maturity Mapping (M0–M4)

Each new object family declares its UOSL maturity level:

Family	Proposed maturity
Manifest envelope	M1 (defined, not yet enacted)
Review decision	M1
Cut change-set	M2 (operational, in pilot)
Verify result	M2
semantic_thread + family	M0–M1 (concept)
retrieval_metric_event + family	M0 (concept; not yet instrumented)

Maturity drives risk and approval (Đ32).

4.8 IU Profile Expectations

Existing tac_logical_unit profile JSON is the current IU profile carrier. The cutter MAY extend the profile JSON with axis-2 fields where canonical columns are not present (recorded as gap; final shape via UOSL maturity).

4.9 Compatibility Flags

Each unit's metadata declares:

• uosl_compat_version — which UOSL draft version this metadata aligns with.
• uosl_compat_status — full / partial / draft.
• Per-field mapping status if needed (in profile JSON).

This enables tracking compatibility as UOSL evolves.

4.10 Guardrails

1. No silent invention of UOSL fields. Gaps → recorded; do NOT mint new G-group entries.
2. No treating draft as enacted. All references carry uosl_compat_status='draft'.
3. universal_edges first (Đ39). Before proposing new Relation Layer constructs, attempt reuse.
4. No parallel Family Registry. All new families must be proposed to Đ44 governance, not created locally.

5. PG Storage per Object (Design Intent — No DDL)

UOSL compat itself does not own data; it maps existing/new objects. The metadata fields live on objects defined in D2, D3, D5, D6, D9, D11. UOSL governance lives outside this deliverable.

6. Schema Gaps

1. canonical_address first-class column (also D6 gap).
2. semantic_role field (D6 gap).
3. risk_class, authority, visibility, readiness, publication_state — G5/G4 group fields not yet first-class.
4. reviewer_identity (D1/D2 gap).
5. Manifest envelope family in Family Registry.
6. Review decision family in Family Registry.
7. Cut change-set family in Family Registry.
8. semantic_thread family in Family Registry.
9. retrieval_metric family in Family Registry.
10. audience_filter_policy family in Family Registry.
11. uosl_compat_version / uosl_compat_status fields on units and objects.
12. Maturity declaration per family.
13. IU profile extension for axis-2 fields where canonical columns missing.

7. Law References

Surface	Law
UOSL itself (DRAFT)	Đ44
Vocabulary	Đ24
Relation Layer	Đ39
Birth gate / authority	Đ0-G
Risk / governance state	Đ32 / Đ37
PG placement	Đ33 / Đ43

8. Open Questions

1. Are manifest/review/cut/report each a new UOSL family, or do they belong to a single "Decision Artifact" family with a kind distinguisher? Defer to Đ44 governance.
2. Should semantic_thread live in Family Registry as a top-level family, or as a sub-type under "Domain Axis"? Defer to Đ44.
3. How does UOSL maturity ladder interact with the cutter's tool revision (D4)? Recommendation: independent, but track via D4 intake.
4. Does Đ44 currently support multi-valued classification labels first-class, or via profile JSON?

9. Coverage

Questions covered (primary): none directly; this deliverable is the cross-cut mapping. Questions covered (secondary): Q4 (manifest field mapping), Q31, Q32, Q39.

Acceptance criteria covered:

• 25 (UOSL/Đ44 mapping)
• 29 (separates schema gaps from impl tasks — supporting)

Schema gaps: 13 named (see §6).

Law dependencies: Đ24, Đ32, Đ33/Đ43, Đ37, Đ39, Đ44, Đ0-G.

Open questions: 4 (see §8).

Law conflicts encountered: none. UOSL guardrail honored — draft treated as draft, no silent invention.