01
Decision boundaries
What may proceed, what requires judgement and how uncertainty stops action.
Traceable work
Architecture changed because the problem changed.
Five project histories, from the initial condition to the resulting system. Each separates the decision, the work performed and the evidence that can responsibly be shown.
Code snapshot · 12 Sep 2026 Public, sanitised and private evidence are separated
Architecture across projects
Five responsibilities, applied in different systems.
Projects are the evidence. The recurring architecture is how decisions, information, work, economics and trust are designed across them.
02
Information and context
Sources, state, provenance and change remain traceable.
03
Operating model
Work is assigned across people, processes and agents without hiding responsibility.
04
Economics and measurement
Cost, value, baselines and stopping criteria belong to the design.
05
Trust and compliance
Access, evidence, audit and regulatory limits are encoded into the system.
Evolution by project
Five systems, five lines of evolution
Each case connects the starting point, the decision that changed the system and the capability that exists now.
Asset development
Residential rehabilitation and exit · Lisbon
Fragmented rehabilitation → documented exit decision
Architecture question
How can rehabilitation be governed as one investment system without presenting sale value as total return?
Starting condition
A residential asset combined physical works, supplier choices, capital allocation and exit timing, but those decisions did not yet share one explicit model.
Circumstance and problem
Treating scope, contracting, cost and sale as separate tasks could optimise one part while weakening the investment as a whole.
Decisions that connect the path
2023Private project documentation
The asset became one bounded decision
The work was framed as a connected system of scope, capital, suppliers and exit rather than as an isolated renovation.
2023Private contracts and invoices
Contracting remained close to execution
Direct supplier coordination kept scope and cost decisions connected to what was physically being delivered.
2023–24Private cost record
Inputs were separated from return
Documented labour and material inputs were recorded independently from acquisition and from the eventual sale value.
Feb 2024Private transaction record
The exit completed the case
The sale closed the operating sequence and created a final transaction record without, by itself, proving return on total capital.
Current architecture
- Investment thesis and constraints
- Rehabilitation scope and supplier control
- Documented execution inputs
- Exit coordination and evidence boundary
A completed case with costs, responsibilities and evidence boundaries documented separately from the sale value.
Evidence map
Visual
Physical transformation
Before-and-after images document the change to the asset.
Private
Cost and transaction record
Invoices, contracts and completion evidence require an authorised review.
Bounded
Financial claim
Sale value and documented inputs are disclosed separately; total return is not claimed.
Published evidence
These notes document decisions and failures that shaped this project. The same note may support more than one story.
Evidence-led publishing
Questions outside. Experience inside.
Articles begin where a real question overlaps with work I have actually done and evidence I can publish responsibly.
Observe demand
Map recurring questions in Google, Reddit and relevant professional communities.
Match experience
Connect the question to a decision, failure or result documented in one of these projects.
Publish the useful layer
Answer with enough evidence to be useful, while protecting client and business information.
A weekly review chooses the strongest evidence-backed question; frequency never replaces substance.