tegwick 1353267569 Establish FIAM repository governance baseline

Assistant: codex
Assistant-Model: gpt-5.6-luna
Assistant-Session: 01a087b0-7b1e-7531-8ef3-6525ebaf7ee7

2026-09-09 21:53:43 +02:00

2.1 KiB

Raw Blame History

FIAM v0.2 — Runtime Topology Lens

Purpose

fiam.lens.runtime-topology projects aggregated runtime observations into architecture dependency edges while preserving different interaction mechanisms.

It does not require FIAM to retain every source span as an Interaction.

RPC

When client/server trace evidence can be correlated:

client SystemNode -> server SystemNode

If only one side is sampled, the partial dependency remains in the runtime catalog's unresolved findings rather than inventing an edge.

Messaging

Span-link causality creates:

producer SystemNode -> Channel -> consumer SystemNode

The Channel is not flattened into a direct service dependency.

A producer without a linked consumer still establishes production to the Channel, but downstream topology remains partial.

Database

Database runtime aggregates and reads-from / writes-to / targets evidence project as:

application SystemNode -> InformationResource

Working-set projection

By default the Lens uses the non-destructive working-set view:

a high-confidence observed->declared correspondence may display the declared id as preferred;
the observed id is retained in the result;
ambiguous mappings stay separate.

Gateways and meshes

A reconciled intended target and an observed responder can coexist.

Example result:

from: declared-client
to: observed-istio-proxy
via_gateway: true
gateway: observed-istio-proxy
intended_target: declared-server

This distinguishes deployment intermediaries from application ownership.

Unresolved is not failure

The Lens result contains an unresolved section. Real sampled topology is expected to have unresolved observations.

The complete multi-domain fixture happens to resolve all five deterministic edges, but the estate conformance suite separately requires partial RPC, messaging, DB and HTTP cases to remain unresolved.

Multi-domain proof

The deterministic fixture yields:

RPC direct-call:             1
broker-mediated messaging:   2
database resource access:    2

All three are projected from one unchanged FIAM Core.

2.1 KiB Raw Blame History