Problem context and objectives
Mission briefing
Lead systems engineer · Vault Perimeter
Design secure file sharing for organizations. Links may expire, access must be revocable, and audit records must survive file deletion.
The design must survive organizations 100K and files billions. Every box must earn its place by satisfying a requirement or containing a failure.
How you win
- 1Trace one user action from request to durable outcome
- 2Connect every component to a stated requirement
- 3Explain the losing tradeoff, not only the chosen technology
Rules and pressure
- organizations: 100K
- files: billions
- Tenant isolation
- Least privilege
Lesson 1 of 3
Live architecture trace
Vault Perimeter: request to outcome
LIVE EVENTauthorize
User sends “authorize” to Policy service. Every access path must reach a trusted authorization decision using explicit resource policy.
organizations = 100K
Design secure file sharing for organizations. Links may expire, access must be revocable, and audit records must survive file deletion. Follow one real user action through the complete architecture; a component is useful only when you can explain the request, state, or failure it handles.