thesabear/public
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

TEMP: swap diagram for a trivial 3-node placeholder to diagnose the gap

Browse Source 
Diagnostic only - not a real content change. If the gap disappears
with this minimal diagram, it's genuinely about the real diagram's
content and I can bisect from here. If the gap is still there, it's
not about the diagram at all.
This commit is contained in:
thesabear committed 2026-08-23 09:50:33 +03:00
1 parent 742ffec430
commit 3aeeb21518
1 file changed
+2 -37
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+2 -37
View File
@@ -78,43 +78,8 @@ This repo is a sanitized showcase of the systems behind that platform — the ac
```mermaid ```mermaid
flowchart LR flowchart LR
Internet(["Internet"]) --> Edge["Edge Firewall"] A["Test A"] --> B["Test B"]
Edge --> LAN["LAN"] B --> C["Test C"]
LAN --> DNS["Internal DNS<br/>two zones"]
LAN --> Vault["Vault<br/>PKI + secrets"]
DNS --> Vault
Vault --> Apps["App Host<br/>41 stacks"]
Vault --> Automation["Automation VM<br/>Git + orchestration"]
LAN --> FileServer["File Server"]
DNS --> FileServer
LAN --> Automation
Apps --> InternalProxy["Internal Proxy Zone"]
Apps --> SSO["SSO"]
Vault --> EdgeProxy["User-Facing Proxy<br/>mTLS"]
DNS --> EdgeProxy
Apps -.proxied.-> EdgeProxy
SSO -.auth.-> EdgeProxy
Apps -.-> Monitoring["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).