Split exception issuer resolution
Split exception issuer resolution is one of 70 measurements this engine publishes in full. It is regenerated from a real run rather than transcribed, and it is shown here with its own claim boundary so the number and its limits arrive together.
The measurement
- Author
- Arhan Canli
- Content hash
- sha256:29178f88644be6ca80e328ba1305e35acbe0da7979b0cb4ba0b7e89b561fad59
- Decision
- ISSUER_EXCEPTIONS_RESOLVED_AS_NONEXECUTABLE_LIFECYCLE_METADATA
- Hypotheses spent
- 0
- Retrieved at
- 2026-08-23T03:04:13.219498+00:00
- Return data opened
- no
- Schema
- canli.alphac-split-exception-issuer-resolution.v1
Lineage
- Lifecycle content hash
- sha256:deed344bd2823f820e326b69f510f704a11b3ba3d2621100594da2600f78cb2d
- Lifecycle path
- artifacts/audit/sharadar_split_lifecycle_scope.json
- Lifecycle sha256
- 017f1723f1937900bc2e40aa1f54f0187286ffda794e4cddcf11159ce82031bf
- Provider crosscheck content hash
- sha256:b401c5260988ba900d0acac857bfeda28a3cb353d6a18db3b9ef55890dc67a32
- Provider crosscheck path
- artifacts/audit/polygon_split_crosscheck.json
- Provider crosscheck sha256
- 5c00be6dee175309d3511f1d183906824f651847e7561df722a03fad5a3e0fb8
Required next action. Implement and test fail-closed lifecycle scoping: source rows outside possible pre-existing exposure remain in lineage but are not executable share mutations. Do not infer a general provider precedence rule from these three cases.
Resolutions
Nested beyond what this page renders. Read it in the artifact.
Check it yourself
Every figure above is read from /glassbox/split_exception_issuer_resolution.json, the
artifact the engine wrote. Nothing on this page is typed by hand: the page is generated from that
file, so a figure that moves in the artifact moves here and a figure that is not in the artifact
cannot appear here at all.