Why an Engineering Lab Instead of a Portfolio
The organizing principle of Blueprint: show decisions and working systems.
An organizing decision
Blueprint is an engineering lab. Its approved mission is to build software, explore architecture, experiment with AI-assisted development, and document decisions behind working systems.
Builds describe substantial work. Experiments frame bounded investigations. Notes record ideas, trade-offs, failures, and lessons. These sections organize the site around engineering questions rather than employment history.
What belongs here
Original implementations, public references, and honest explanations of what is planned, what is running, and what has actually been observed. Results need evidence. Unfinished work must remain visibly unfinished.
Publication boundary
Professional repositories and confidential material are outside the lab's source context. Renaming proprietary work does not make it independent. When provenance is uncertain, the material is excluded.
This is the decision recorded in Blueprint's accepted ADRs, not a claim about past professional work.