dot-iu-cutter v0.5 — Fabric Addendum Topic Formation GPT Position

Date: 2026-05-18 Reviewer: GPT Context: User added requirements about internal/external laws, dynamic metadata/schema, multi-dimensional assembly, SQL data binding, Directus boundary, automatic split/merge/edit, and asked to define the supplemental design topic before sending Agent/Opus forward.

Position

The next objective should not be a broad 10-part architecture rewrite. It should be a bounded supplemental design phase that turns the current cutter into the next layer of an Information Unit Fabric.

Opus's 4-workstream compression is accepted as the better planning shape, with one modification: WS-1 should be broadened slightly to include the minimal cross-cutting contracts required by the user's new requirements, without designing all downstream application features now.

Accepted workstreams

WS_1_relation_edge_topic_graph_and_assembly_contract:
  priority: highest
  reason: needed for the second confirmed dimension, topic threading, and for all later SQL/data/code/report/process connections

WS_2_metadata_key_registry_and_source_profile:
  priority: high
  reason: prevents hardcoded labels/keys/grammar and supports internal Incomex laws plus government laws

WS_3_assembly_by_topic:
  priority: high
  reason: proves non-document reconstruction beyond original-document assembly

WS_4_edit_amend_supersede_pipeline:
  priority: high_after_WS1_WS2
  reason: needed for automatic add/remove/update flows with gates and forward-compensation

Deferred but recorded

SQL_data_binding_for_contracts:
  status: record_as_principle_and_interface_requirement_now
  defer_full_schema_until_real_contract_pilot: true

Directus_contract_template_feature:
  status: use_as_assembly_first_UI_when appropriate
  boundary: Directus is UI/form/template assembly; SQL/IU Fabric remains semantic authority and provenance layer

render_snapshot_contract_lifecycle:
  status: defer detailed design
  reason: application-level feature; should not bloat core IU Fabric design before relation/topic foundation exists

Recommended supplemental design topic

phase: v0_5_information_unit_fabric_addendum_scope_and_WS1_design_brief
nature: design_only
purpose:
  - define supplemental architecture scope
  - settle 4 workstream roadmap
  - produce precise WS-1 implementation/design brief for Agent
  - preserve SQL SSOT and Assembly First boundaries
  - avoid over-engineering application-level contract features before foundation

Key direction

Start with WS-1 because the system already has original-document assembly proof, but lacks the second dimension: topic/thread assembly across law, process, SQL, code, reports, lessons, and architecture notes.

The supplemental design must explicitly support:

required_capabilities:
  - original document reconstruction
  - topic/specialty threading
  - relation edges between IUs and non-IU entities
  - future SQL entity binding without copying entire SQL data into text units
  - future Directus template use without moving authority out of SQL/IU Fabric
  - automatic add/remove/amend flows through gated lifecycle
  - no hardcoded labels, metadata keys, grammar profiles, or source types

Not authorized

forbidden:
  - schema migration
  - production write
  - code change
  - index DDL execution
  - CUT/VERIFY
  - Constitution dry-run
  - bulk cut
  - Directus mutation
  - vector/NoSQL integration
  - contract template implementation