README: revert the 3 failed diagram-gap test changes

None of edge reduction, classDef removal, or multi-line label removal
fixed the gap - restoring the full diagram content since there's no
reason to keep it degraded for a fix that didn't work.
This commit is contained in:
thesabear committed 2026-08-23 09:32:25 +03:00
1 parent 9054ac7027
commit 742ffec430
1 file changed
+20 -6
+20 -6
View File
@@ -81,12 +81,12 @@ flowchart LR
Internet(["Internet"]) --> Edge["Edge Firewall"] Internet(["Internet"]) --> Edge["Edge Firewall"]
Edge --> LAN["LAN"] Edge --> LAN["LAN"]
LAN --> DNS["Internal DNS"] LAN --> DNS["Internal DNS<br/>two zones"]
LAN --> Vault["Vault"] LAN --> Vault["Vault<br/>PKI + secrets"]
DNS --> Vault DNS --> Vault
Vault --> Apps["App Host<br/>41 stacks"] Vault --> Apps["App Host<br/>41 stacks"]
Vault --> Automation["Automation VM"] Vault --> Automation["Automation VM<br/>Git + orchestration"]
LAN --> FileServer["File Server"] LAN --> FileServer["File Server"]
DNS --> FileServer DNS --> FileServer
LAN --> Automation LAN --> Automation
@@ -94,13 +94,27 @@ flowchart LR
Apps --> InternalProxy["Internal Proxy Zone"] Apps --> InternalProxy["Internal Proxy Zone"]
Apps --> SSO["SSO"] Apps --> SSO["SSO"]
Vault --> EdgeProxy["User-Facing Proxy"] Vault --> EdgeProxy["User-Facing Proxy<br/>mTLS"]
DNS --> EdgeProxy DNS --> EdgeProxy
Apps -.proxied.-> EdgeProxy Apps -.proxied.-> EdgeProxy
SSO -.auth.-> EdgeProxy SSO -.auth.-> EdgeProxy
Automation -.-> Monitoring["Monitoring"] Apps -.-> Monitoring["Monitoring"]
Automation -.-> SecMon["Security Monitoring"] Automation -.-> Monitoring
FileServer -.-> Monitoring
EdgeProxy -.-> Monitoring
Apps -.-> SecMon["Security Monitoring"]
Automation -.-> SecMon
FileServer -.-> SecMon
EdgeProxy -.-> SecMon
classDef edge fill:#f8cecc,stroke:#b85450,color:#333
classDef core fill:#dae8fc,stroke:#6c8ebf,color:#333
classDef obs fill:#fff2cc,stroke:#d6b656,color:#333
class Internet,Edge edge
class LAN,DNS,Vault,Apps,Automation,FileServer,InternalProxy,SSO,EdgeProxy core
class Monitoring,SecMon obs
``` ```
Solid arrows are real dependencies; dotted arrows are asynchronous telemetry reporting, not a blocking dependency. Full breakdown of all 8 traffic laws (ingress, east-west, secrets, DNS, observability, notifications, CI/CD, management) with the actual trust-boundary reasoning: [docs/architecture-overview.md](docs/architecture-overview.md). Solid arrows are real dependencies; dotted arrows are asynchronous telemetry reporting, not a blocking dependency. Full breakdown of all 8 traffic laws (ingress, east-west, secrets, DNS, observability, notifications, CI/CD, management) with the actual trust-boundary reasoning: [docs/architecture-overview.md](docs/architecture-overview.md).