id: conformance/railiance-fabric/visualization-examples title: Railiance Fabric Visualization Examples status: candidate consumer: railiance-fabric conformance_pack: conformance/railiance-fabric examples: - id: clean-service-runtime-slice title: Clean service to runtime slice purpose: Show service, deployment, runtime, endpoint, data, signal, policy, and evidence as distinct nodes. nodes: - id: service/billing-portal category: service canon_anchor: model/landscape - id: deployment/production category: deployment canon_anchor: model/devsecops - id: runtime/billing-namespace category: runtime-resource canon_anchor: model/landscape - id: endpoint/billing-api category: endpoint canon_anchor: model/network - id: datastore/subscription-ledger category: datastore canon_anchor: model/data - id: signal/access-review category: telemetry-signal canon_anchor: model/observability - id: policy/tenant-isolation category: policy canon_anchor: model/governance - id: evidence/access-review category: evidence canon_anchor: model/observability edges: - source: deployment/production type: deploys target: runtime/billing-namespace display_only: false - source: service/billing-portal type: exposes target: endpoint/billing-api display_only: false - source: service/billing-portal type: reads_or_writes target: datastore/subscription-ledger display_only: false - source: runtime/billing-namespace type: observed_by target: signal/access-review display_only: false - source: service/billing-portal type: governed_by target: policy/tenant-isolation display_only: false - source: policy/tenant-isolation type: evidenced_by target: evidence/access-review display_only: false - id: bad-shape-service-runtime-collapse title: Bad shape where service and runtime collapse bad_shape: problem: One node named billing-portal carries service, deployment, namespace, endpoint, and evidence semantics. why_bad: The graph cannot distinguish declared service boundary from deployed runtime and observed evidence. correction: - Split service, deployment, runtime resource, endpoint, and evidence into distinct nodes. - Connect them with deploys, exposes, observed_by, and evidenced_by edges. - Preserve a display cluster only as display_only metadata. - id: bad-shape-display-edge-as-canon title: Bad shape where display grouping becomes canon bad_shape: problem: A same_color_group edge is used to claim ownership or dependency. why_bad: Rendering choices become semantic claims and pollute downstream reasoning. correction: - Replace ownership with owned_by when evidence exists. - Replace dependency with depends_on or flows_to only when source evidence supports it. - Keep same_color_group as display_only true. - id: bad-shape-flow-dependency-confusion title: Bad shape where network flow equals dependency bad_shape: problem: Observed traffic is captured as service_depends_on_service without policy, endpoint, or protocol context. why_bad: A transient flow may not be an intentional dependency. correction: - Capture flow as Flow with protocol, source, target, and evidence. - Create depends_on only when a declared or inferred dependency has separate support. - Link both to evidence and confidence. visualization_rules: - Canonical graphs must be recoverable without layout metadata. - Views may collapse or cluster nodes, but collapsed source nodes and edges must remain retrievable. - Display attributes may include color, group, rank, x, y, icon, collapsed, highlighted, and hidden. - Display attributes must not be used by validation as proof of ownership, dependency, reachability, policy, or evidence.