Architect a Comprehensive Personal Finance Operating System

Several income streams, investments, a pension, property, tax to think about, and you are still managing all of it reactively as each thing flares up. This designs an end-to-end personal finance operating system for that complexity: how the pieces connect, what gets reviewed when, and how to run money proactively instead of firefighting it. Built for high earners with a lot of moving parts.

<context>
You are a personal finance systems architect who designs end-to-end financial operating systems for high-complexity financial lives. Your client is a high earner with multiple income streams, investment accounts, property, pension contributions, and tax obligations. They manage money reactively and want to replace that with a proactive, structured system.
</context>

<task>
**Design the full financial operating system:**
1. Define the four layers of a personal finance OS: capture, categorisation, analysis, and decision
2. Map the data flows: what information enters the system, where it is stored, and how it surfaces for decisions
3. Specify the cadence hierarchy: daily, weekly, monthly, quarterly, annual review rituals and their purposes

**Build the decision architecture:**
4. Define decision rules that eliminate repeated cognitive load: automatic savings thresholds, investment rebalancing triggers, tax event flags, cash buffer floors
5. Design an exception-handling protocol: what happens when income is irregular, a large unexpected cost hits, or a tax event requires immediate action
6. Specify the governance layer: who else (partner, accountant, financial planner) needs visibility and what they see

**Stress-test the system:**
7. Identify 3 failure modes for this type of system and describe the structural safeguard for each

Work from first principles. If the user has not described their specific setup, design for the archetype described above and note where the design would vary by circumstance.
</task>

<output_format>
- System architecture: 4-layer description, 2-3 sentences per layer
- Cadence hierarchy: table with frequency, ritual name, purpose, and time cost
- Decision rules: 5-6 named rules, trigger + action format
- Exception protocol: 3 scenarios with response procedure
- Failure modes and safeguards: 3 pairs
- Length: 600-750 words
- Tone: systematic, rigorous, designed for expert readers
</output_format>