HoloselfThese synthetic examples show how one canonical self supports different work without cloning a complete personal profile into every workspace.
A career workspace loads confirmed achievements, positioning, technical depth, and leadership stories. Company research and interviewer strategy remain project-owned.
“Prepare for an enterprise architecture interview. Use approved leadership examples and identify weak evidence.”
Career, technical, leadership, and interview lenses—with source paths and restrictions.
Corrected scope metric, linked to interview notes as evidence. Canonical self remains unchanged until approval.
A publishing workspace keeps posts, calendar, platform rules, performance, media, and prompts local while drawing on approved reusable knowledge.
“Draft a public post about regulated AI using my approved voice and public-safe stories.”
Publishing lens plus explicitly public-safe claims. Employer-confidential and career-private passages are withheld.
Reusable vocabulary or a proven story—never an automatic conversion of engagement metrics into a personal belief.
A technical project can use architecture preferences, decision principles, and known constraints while code, ADRs, incidents, and implementation artifacts stay with the project.
“Review this platform decision against my architecture principles and previous decisions.”
Technical and leadership lenses plus project-local ADRs.
New decision principle backed by accepted ADR evidence and explicit user review.
| Content | Owner |
|---|---|
| Identity, preferences, durable facts, approved stories | Canonical self |
| Applications, research, interviews, compensation strategy | Career project |
| Posts, calendar, performance, media, platform rules | Publishing project |
| Code, ADRs, incidents, delivery artifacts | Technical project |
| Reusable project discovery | Proposal to self; user decides |