You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 469e912
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs/design/platform-house-reference-processing.md
+22-10Lines changed: 22 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -649,7 +649,7 @@ collapsed into strings, optional parameters, or nullable tuples.
649
649
| --- | --- | --- |
650
650
|**Realize**| One library identity or complete population demand | One owning Library realization or one platform population of owning Library realizations, each with resource-free source and view correspondence |
651
651
|**Resolve assembly reference**| One exact Metadata `AssemblyBindingRequest` and platform-route prerequisites | Metadata-owned binding decision plus the platform contribution used by the ladder |
652
-
|**Resolve type definition**| One exact Metadata `TypeResolutionRequest`, starting candidate with its owner-issued view, and required view |Metadata-owned `TypeResolutionOutcome` plus reference/implementation correspondence when the required view differs from the starting view |
652
+
|**Resolve type definition**| One exact Metadata `TypeResolutionRequest`, starting candidate with its owner-issued view, and required view |One resource-free Platform projection of the exact Metadata terminal arm and forwarding evidence, plus reference/implementation correspondence when the required view differs from the starting view |
653
653
654
654
`Realize` supports direct platform browsing and supplies source candidates for
655
655
the other operations. The two reference-resolution operations are the only
@@ -675,6 +675,16 @@ work. The completed value and receipt preserve whether the operation returned
675
675
one reference outcome, one implementation outcome, or the existing paired
676
676
reference-and-implementation outcomes.
677
677
678
+
The live `TypeResolutionOutcome` remains inside execution while its Metadata
679
+
catalog and copied Library images are available. Before those authorities are
680
+
retired, PlatformHouse projects its exact terminal arm, ordered forwarding
681
+
hops, terminal assembly identity, physical definition address and supplier
682
+
when resolved, and typed non-success evidence into a detached
683
+
`PlatformTypeDefinitionResolutionResult`. The projection retains
684
+
owner-issued Metadata names, tokens, identities, provenance, and failure
685
+
values, but no `ResolvedAssemblyReference`, opener, candidate, context,
686
+
catalog, stream, or disposal obligation.
687
+
678
688
### View and population demand
679
689
680
690
View demand is closed:
@@ -1546,7 +1556,8 @@ When a platform operation begins from a .NET Standard facade:
1546
1556
3. the House supplies those candidates through an explicit Metadata binding
1547
1557
policy;
1548
1558
4. Metadata follows any exact `ExportedType` and `AssemblyRef` evidence and
1549
-
returns its unchanged reference-view outcome;
1559
+
returns its reference-view outcome, which the House projects without
1560
+
changing its terminal arm or forwarding evidence;
1550
1561
5. when implementation demand remains, the House requires an explicit
1551
1562
reference-to-implementation view correspondence for the resolved contract
1552
1563
definition and starts a second Metadata resolution in the authorized
@@ -1972,7 +1983,8 @@ one exact .NET runtime target. The starting and required views are both
1972
1983
Implementation. Metadata follows the exact `System.Xml` and
1973
1984
`System.Xml.ReaderWriter` forwarding declarations to the physical
1974
1985
`System.Private.Xml` definition under the House-supplied implementation
1975
-
policy. The House retains one Metadata outcome and every forwarding hop. It
1986
+
policy. The House retains the outcome's exact terminal arm, physical
1987
+
definition identity, and every forwarding hop in one resource-free result. It
1976
1988
does not introduce a reference resolution or view-correspondence transition.
1977
1989
1978
1990
### .NET Standard facade resolves to runtime implementation
@@ -2129,11 +2141,11 @@ rejected outcomes. The stage-7a population operation does not expose catalog
2129
2141
semantics or change CLI or Inspect Web routing. Step 9a, tracked by
2130
2142
[#8164](https://github.com/richlander/dotnet-inspect/issues/8164), adopts the
2131
2143
family-default population and catalog query for versionless bare CLI type and
2132
-
member routing. Browser/Wasm adoption, exact-demand Metadata binding, and
2133
-
Services-era resolver retirement remain later focused slices.
2134
-
Issue #8298 owns the first exact-demand Metadata binding slice: one
2135
-
implementation-view start and required implementation result. It does not
2136
-
implement the reference-to-implementation bridge.
2144
+
member routing. Browser/Wasm adoption and Services-era resolver retirement remain later
2145
+
focused slices. The first exact-demand Metadata binding slice, implemented
2146
+
under [#8298](https://github.com/richlander/dotnet-inspect/issues/8298),
2147
+
supports one implementation-view start and required implementation result. It
2148
+
does not implement the reference-to-implementation bridge.
2137
2149
2138
2150
The step-6 ownership correction was designed under
2139
2151
[#6984](https://github.com/richlander/dotnet-inspect/issues/6984). It adopts
@@ -2358,13 +2370,13 @@ The implementation and adoption slices own these Release gates:
2358
2370
| Package-backed reference population ownership | One authoritative package-backed reference population produces one source-ordered reference-only Library owner per distinct managed identity and one source settlement after Package Source detaches. Every content item retains source-issued package provenance. Completion transfers every Library owner beside one Artifact session; terminal, cancellation, duplicate identity, foreign contribution, and incomplete work transfer neither authority. |
2359
2371
| Package-backed implementation population ownership | One authoritative package-backed runtime population produces one source-ordered implementation-only Library owner per distinct managed identity, assigns each exact runtime content both mandatory roles under Platform-owned declaration-surface evidence, and records one source settlement after Package Source detaches. Every content item retains source-issued package and runtime-support provenance. Completion transfers every Library owner beside one Artifact session; terminal, cancellation, duplicate identity, foreign contribution, and incomplete work transfer neither authority. |
2360
2372
| Selected reference population | One family-default, reference-only complete-population operation freezes one exact target, applies the authorized Reference source policy, and publishes one non-empty authoritative population. Installed success suppresses package work; package fallback uses only the exact selected discovery association; failure or work exhaustion cannot publish a shortened population. Completion preserves the original request, selected target and discovery evidence, source-generation settlements, and cumulative work while transferring all Library owners beside the separate Artifact session. Every terminal path cleans up before projection and retains no live authority. |
2361
-
| Resource-free House boundary | Focused contract tests over contributions, completed House values, receipts, requests, and cache entries prove that they retain no live source handle or content obligation, Artifact owner or lease, Library owner or lease, callback, opener, stream, or disposal delegate. |
2373
+
| Resource-free House boundary | Focused contract tests over contributions, completed House values, type-definition resolution results, receipts, requests, and cache entries prove that they retain no live source handle or content obligation, Artifact owner or lease, Library owner or lease, Metadata context or catalog, candidate, callback, opener, stream, or disposal delegate. |
2362
2374
| Internal Library access | PlatformHouse Metadata work reads exact content only through a fresh internal `LibraryOperationLease`; every borrow ends before `await`, and the lease settles before completion. |
2363
2375
| Terminal owner disposition | Completed non-owning operations, unavailability, ambiguity, rejection, failure, incomplete completion, and cancellation retire every constructed owner the House does not return, including partially constructed multi-Library population work; only a completed owning `Realize` result transfers owners, and retirement failure remains visible. |
2364
2376
| Failure precedence | A superseded source fault may remain evidence in another terminal outcome; construction, borrow, lease-settlement, retirement, or child-release failure produces `Failed`, including when cleanup fails after cancellation. |
2365
2377
| Permissive Workspace admission | A participant targeting a newer platform remains admissible and usable for same-participant inspection without realizing a matching complete platform. |
2366
2378
| Exact traversal compatibility | Under an owner-classified unsupported downgrade, an exact Metadata member-signature match succeeds with downgrade context; a missing or changed signature returns the attributed compatibility failure without blocking unrelated work. Supported upward compatibility does not warn merely because targets differ. |
2367
-
| Metadata ownership | Platform type resolution invokes the structured Metadata API and preserves its exact outcome and forwarding hops. |
2379
+
| Metadata ownership | Platform type resolution invokes the structured Metadata API and projects its exact terminal arm, owner-issued facts, and ordered forwarding hops before retiring the live resolution context. |
2368
2380
| Direct implementation start | An implementation-view `System.Xml.XmlReader` request resolves through `System.Xml.ReaderWriter` to the physical `System.Private.Xml` definition in one Metadata outcome, with no fabricated reference outcome or view correspondence. |
2369
2381
| Transparent .NET Standard | A `.NET Standard` facade can resolve through an exact runtime target without constructing a `NetStandard` family or implementation population. |
2370
2382
| Physical supplier retention | A resolved implementation type or assembly retains its physical supplier rather than being relabeled as the reference facade. |
0 commit comments