coulomb/railiance-fabric
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: render graph explorer zone boundaries

Browse Source
This commit is contained in:
Bernd Worsch
2026-05-24 17:02:12 +02:00
parent ea81533172
commit 5a2d987b6a
4 changed files with 437 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
docs/graph-explorer-contract.md
View File

@@ -154,6 +154,23 @@ The graph explorer should support zone-oriented modes for Fabric payloads:
Zone modes are diagnostic views. They answer "where does this run or who can
reach it here?" without mutating the underlying Fabric responsibility boundary.
Zone boundary overlays are a visual layer over the graph canvas. They should be
computed from visible node positions after layout/filtering rather than modeled
as graph parent nodes. The default boundary grouping is `deploymentEnvironment`:
| Overlay label | Matching nodes |
|---------------|----------------|
| `dev-tegwick` | visible nodes with `deploymentEnvironment: dev` in the private local development overlay |
| `test` | visible nodes with `deploymentEnvironment: test` or legacy `staging` |
| `prod` | visible nodes with `deploymentEnvironment: prod` |
Nodes without deployment overlay data are not enclosed. Edge-only deployment
overlay evidence may contribute to zone summaries and warnings, but it should
not create a boundary unless at least one visible node belongs to the same zone.
When access-zone grouping is selected, boundaries use `accessZone` values such
as `private-dev`, `collaborator-test`, `production-public`, or
`production-admin`.
Useful warnings for the graph explorer include:
- control surfaces in user-facing access zones;