Salvato in:
| Autore principale: | |
|---|---|
| Natura: | Recurso digital |
| Lingua: | |
| Pubblicazione: |
Zenodo
2026
|
| Accesso online: | https://doi.org/10.5281/zenodo.18736689 |
| Tags: |
Aggiungi Tag
Nessun Tag, puoi essere il primo ad aggiungerne!!
|
Sommario:
- <p>This paper introduces a protocol-level method for cross-domain legal analysis, addressing the structural difficulty that legal domains (tax, contract, tort, trust, and public law) operate as self-contained semantic systems that do not readily compose into a unified analytical framework.</p> <p>Rather than pursuing semantic alignment, the paper proposes an Interface Routing Framework in which each legal domain is treated as an interface processor acting on a shared, observable event-flow. A single event-flow is routed across multiple interfaces and encoded at each stage without requiring semantic reconciliation. Cross-domain non-alignment is recorded as a structured output rather than resolved.</p> <p>The method is operationalized using a stable tracing unit—the owner–manager role configuration—which enables continuous tracking of a single flow across heterogeneous legal interfaces. To stabilize observability, the framework incorporates a minimal structural condition derived from the Cabinet–Drawer Model (CDM), defined by the joint presence of horizontal and vertical support capacities.</p> <p>This condition is expressed as a coordinate-based constraint:</p> <p>F^GC = X × Y</p> <p>where X represents cross-interface continuity of the event-flow and Y represents its admissibility across successive processing stages. The superscript GC specifies a going-concern constraint: routing remains operative only when both dimensions are non-zero.</p> <p>The paper contributes:<br>(1) a routing grammar (Flow → Interface₁ → Interface₂ → … → Output);<br>(2) a lab-usable interface table for encoding transformations and mismatch/distortion flags;<br>(3) a minimal conflict-handling rule that records non-alignment without resolving it; and<br>(4) a structural method for preserving flow continuity across domains without semantic unification.</p> <p>The framework is descriptive and protocol-oriented. It does not provide doctrinal interpretation, causal explanation, or policy evaluation. Its function is to make cross-domain routing observable, encodable, and comparable at the level of interface processing.</p>