miller-bridge-trace

Miller Bridge Trace

Miller bridge tracing is provider-scoped evidence, not generic semantic magic. The current beta provider is dotnet-web: TypeScript/JavaScript/Vue URL literals to ASP.NET endpoints, DTOs, entities, and EF/table signals.

Workflow

1. Find a concrete anchor:

search(query="<URL, method, controller, DTO, entity, or table>")
search(query="<route text>", regions="string_literal")

2. Inspect the best anchor when names are ambiguous:

inspect(target="<symbol>", depth="full")

3. Run bridge trace:

trace(target="<anchor>", mode="bridge")

If the anchor name is ambiguous but you know the file, pass scope instead of doing a JSON search for the id:

trace(target="<symbol>", mode="bridge", scope="<file>")

4. If the user asks for a specific route from one node to another, use path mode first, then bridge mode if the path crosses provider boundaries:

trace(target="<from>", mode="path", to="<to>")
trace(target="<from>", mode="bridge")

Reading Results

• [verb-unknown] means the URL matched but HTTP verb evidence is reduced.
• [ambiguous] means multiple plausible links exist.
• No bridge path can mean no provider is selected, missing extractor evidence, stale index, or a real absence of cross-language linkage.

Report

State:

• Provider assumption, usually dotnet-web
• Start node and end node if present
• Link confidence and any flags
• Missing evidence if the trace stops early
• Next concrete check, such as inspecting a controller action or DTO

Do not present bridge output as all-language support. It is evidence for the selected provider only.