This is part of the actual course, not a sales excerpt.
I use “the matrix” as a working name for systems I rarely notice while I am inside them: employment norms, household obligations, status incentives, algorithms, debt, and my own repeated responses. It is not one hidden controller, and it does not explain every outcome. It is a way to make influences visible enough to examine.
Layer 1 — The path around me
I inherited a familiar sequence: study, find stable work, increase income, increase commitments, and defer optionality until later. That path can provide skills, relationships, and real security. It can also narrow my choices when my costs rise with my income or one employer controls most of my cash flow.
The useful question is not “Is employment a trap?” It is:
What does my current arrangement give me, what does it cost me, and which parts did I choose deliberately?
Layer 2 — The path inside me
Familiar choices often feel safer because I have more evidence about them. Unfamiliar choices can feel dangerous before I have measured their actual downside. That feeling is information, but it is not a forecast.
I separate three things:
- Constraint: a fact I must work with, such as rent, caring responsibilities, health, or a contract.
- Prediction: what I think will happen, such as “Nobody will pay for this.”
- Preference: what I want, such as more control over my time.
When I mix them together, a prediction can masquerade as a constraint.
My systems map
I draw one page with five headings:
| Area | What currently shapes my choice? | What evidence do I have? | What can I change in 30 days? |
|---|
| Work | | | |
| Money | | | |
| Attention | | | |
| Relationships | | | |
| Time | | | |
I keep the entries specific. “Society” is too broad. “I accept meetings after 4 pm because my manager praises availability” can be observed and tested.
Worked example — a completed systems map
This example shows the level of specificity I am aiming for. I use it as a reference, not as an answer to copy.
| Area | What currently shapes my choice? | What evidence do I have? | What can I change in 30 days? |
|---|
| Work | Defaulting to open-ended availability and taking on every extra demand because saying no feels like risking financial stability. | Rosters and time logs show operational creep; working hours expand to fill all capacity while personal development is pushed to the margins. | Define one fixed weekly boundary where availability closes, protecting dedicated non-work blocks without negotiation. |
| Money | Outflows rising alongside gross income; justifying lifestyle creep and impulse friction spending as relief from high-output work. | Monthly statements show discretionary outflow tracking upward despite income spikes; net savings remain stagnant. | Set up an automated transfer route moving a fixed percentage of income to an isolated, non-liquid account within 24 hours of pay. |
| Attention | Defaulting to algorithmic feeds and passive media during decompression windows to numb work-related fatigue. | Screen-time logs show 2–3 hours spent on low-signal apps during rest blocks; waking up feeling unrecovered. | Enforce a screen-free window for the first 45 minutes of evening wind-down, substituting physical training or study. |
| Relationships | Prioritising low-friction, surface-level exchanges because maintaining focused, demanding connections requires scarce energy. | Weeks pass between substantive conversations with key people; social interactions default to quick messaging apps. | Commit to one focused, uninterrupted call or catch-up per week without secondary tasks running in parallel. |
| Time | Treating long-term independent work as an optional secondary pursuit that only gets attention once external obligations are zeroed out. | Project repositories and drafting documents sit untouched for consecutive weeks waiting for a “free weekend.” | Protect a single 60-minute sprint daily for personal build work before opening passive entertainment apps. |
My first record
I finish this module with one dated statement:
- The arrangement I am examining.
- The constraint I will respect.
- The prediction I will test.
- The smallest action that produces new evidence.
A timestamp does not prove that my plan will work. It proves what I said I would test and when I said it. That is enough to begin comparing intention with action.
Worked example — Record 001
- Date: 23 September 2026
- The arrangement I am examining: Letting immediate operational fatigue relegate independent personal build projects to low-priority downtime.
- The constraint I will respect: Contracted employment responsibilities, baseline physical recovery, and core financial commitments must remain met.
- The prediction I will test: “If I extract 60 focused minutes every day to work on my own initiative before touching passive entertainment, my energy will drop and my baseline performance will suffer.”
- The smallest action that produces new evidence: For five consecutive days, execute a timed 60-minute build session before engaging in secondary screen use, recording task completion and end-of-day cognitive energy in a single log entry.