architecture-overview: verify against Trilium, fix inaccurate dependency graph, add real evidence

Browse Source

Removed the dependency-graph Mermaid diagram (had backwards Vault
dependency arrows, contradicted the documented ingress model) and the
four-boundary Mermaid diagram (fully redundant with the table below it).
Verified every remaining claim against Trilium's Traffic Flow Model and
fixed two that didn't hold up: the DNS-bypass failure behavior overstated
an unconditional SSO bypass, and the notifications failure behavior had
an unsourced claim about backlog retry.

Added the real story behind the trust-boundary hardening (three stages
of the same "trusted by default" flaw getting found and closed, not a
changelog of dated facts), a new trust-depth diagram showing that being
"inside the network" still enforces its own internal boundaries, and
real pfSense screenshots proving the LAN lockdown rules actually exist
in production, not just in the doc.

...

This commit is contained in:

thesabear committed 2026-08-25 21:58:42 +03:00

1 parent c11395825c

commit cb5a2de638

10 files changed

+52 -65

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

assets/pfsense-rules-wan.png

BIN

Binary file not shown.

Side by Side After Width:  |  Height:  |  Size: 128 KiB