tegwick
1353267569
Assistant: codex Assistant-Model: gpt-5.6-luna Assistant-Session: 01a087b0-7b1e-7531-8ef3-6525ebaf7ee7
15 lines
1.3 KiB
Markdown
15 lines
1.3 KiB
Markdown
# FIAM v0.2 — Declaration Matching Contract
|
|
|
|
`declared` is not a shortcut for “the runtime target node appears in a `uses` assertion.” It is a time-aware graph query.
|
|
|
|
For a runtime logical edge `(from, target, domain, channel?, intended_target?)` at time `T`:
|
|
|
|
1. project observed identifiers through the non-destructive working-set mapping effective at `T`;
|
|
2. select the latest declared snapshot from each declaration source effective at `T` and applicable to the edge population;
|
|
3. resolve declaration subjects/objects to architectural owners where appropriate;
|
|
4. consider the runtime target, intended target, and mediating Channel as valid declaration surfaces according to domain;
|
|
5. return the matching declaration ids and reasons, not only a boolean.
|
|
|
|
A mediated messaging edge may therefore be declared by `Producer --uses--> Channel` even if the runtime topology view also resolves a downstream consumer. A gateway-mediated runtime edge is declared when the intended target is declared even though the observed responder is the gateway. An observed identifier and its preferred declared working-set identity are treated as the same query-time navigation target without merging the source records.
|
|
|
|
Ambiguous or absent declarations remain explicit findings. The declaration matcher never creates `same-entity-as` and never changes evidence.
|