Conduit
Organizational intelligence for preserving intent across meetings, tickets, repositories, and decisions.
AIknowledge graphsengineering systems
The identity
Fosterman is not a costume.
It is the survival identity I built inside systems that repeatedly tried to define, discard, or simplify me. Over time, that identity became a philosophy of self-authorship, technical leverage, mentorship, and institutional accountability.
“Sirrele. Fosterman. The black wolf. The version of me that learned how to survive before he learned how to rest.” Even Better If: The Gospel of Fosterman
Identity architecture
Sirrele is the person. Fosterman is the operating identity.
Sirrele Steinfeld is the engineer, father, founder, writer, and human being.
Fosterman is the name for the part of me that learned how to survive systems, study them, challenge them, and eventually build alternatives.
Even Better If is the doctrine and reflection method that turns lived experience into rules, receipts, and usable maps.
Alter ego
Built for survival
Fosterman began as a self-authored identity powerful enough to survive environments that kept trying to reduce me to a file, diagnosis, statistic, or problem.
Philosophy
Built for interpretation
It became a way to think about abandonment, power, code, mentorship, leadership, boundaries, responsibility, and what institutions owe the people inside them.
Body of work
Built to leave maps
The writing, systems, products, reflections, and experiments are all attempts to leave behind something other people can navigate without needing me to rescue them.
Core definition: Fosterman is the survival identity Sirrele Steinfeld
built inside failed systems—and the philosophy he now uses to build better ones.
Part I · The black wolf is born
The origin story
The site should not flatten the story into inspiration. These are the chapters that explain how the identity formed, what it protected, and what it cost.
Chapter 1
The Concrete Bed & The Fireworks
Psychosis. Juvenile jail. Fourth of July. The night the world forgot me, and I started remembering myself.
Chapter 2
Meth, Montana & The Mirror
Racism, bruises, silence, cold benches, and learning how survival can split a person into versions.
Chapter 3
The Mercedes Thief
Being loved by Charles, testing the boundaries of love, and learning what “Dad” really means.
Chapter 4
Ed's Office
The moment someone said “I love you” and a different future became imaginable.
Chapter 5
UCLA and the Lost Prophet
Brilliance, instability, collapse, code-switching, ambition, and reinvention.
Chapter 6
Coding While Homeless
A laptop, a floor, and the discovery that software could become agency, structure, and a way out.
Chapter 7
Fosterman Is Born
Not a name. A philosophy. A challenge to God, government, and every system that pretends it cares.
About
The throughline
At fifteen, I began asking why people fall through systems that are supposed to help them. Software became the discipline through which I learned to model complexity, build leverage, test hypotheses, and create systems that can be held accountable.
“I want to validate what I say with data. I don’t want to just say fluffy things.” Foster Tales, 2022
Engineering
Build from napkin to production
I translate ambiguous ideas into software systems, technical architecture, operating models, and measurable outcomes.
Leadership
Turn reflection into operating change
I am documenting how technical strength can create unnecessary organizational conflict—and how to become more effective without becoming less exacting.
Mission
Increase institutional capability
The long-term goal is to reinvest technical, financial, and organizational capability into foster care and other systems with high human stakes.
Part II · Even Better If
The rules, receipts, and maps
Even Better If is the doctrine at the center of Fosterman: part memoir, part manifesto, part curriculum, and part operating system for becoming more honest, capable, and self-authored.
Rule 1
All systems are built to abandon you.
But I do not have to abandon myself.
Rule 2
You can love people who hurt you and still walk away.
Love and boundaries can exist in the same sentence.
Rule 3
Code or die.
Programming gave me structure, leverage, language, and a way to build a future.
Rule 4
Mentor without permission.
The title is optional. Showing up is not.
Rule 5
There is no such thing as a bad kid.
There are only systems that ran out of language and blamed the child.
Rule 6
Burn the cape. Keep the map.
Stop trying to save everyone. Leave behind something usable.
Rule 7
You do not have to forgive to be free.
Freedom does not require fake peace.
Editorial principle: every major claim should eventually connect to
a story, a rule, a receipt, a system, or a reflection.
Selected work
Systems I have built, led, or shaped
These are the systems built from the philosophy. Each project answers: what failed, what I observed, what I built, what the evidence showed, and what I would change.
GitFitCode
A professional community treated as infrastructure rather than as a networking group.
communitymentorshipleadership
Larger-role preparation
The roles I am preparing to hold
The immediate objective is not a title upgrade for its own sake. It is to prove I can carry broader technical scope, organizational influence, and executive accountability.
Immediate
Staff / Principal Engineer
High-leverage technical leadership across architecture, execution, standards, reliability, and cross-team coordination.
- System design depth
- Influence without authority
- Cross-org technical strategy
- Hands-on implementation credibility
Current readiness 78%
Parallel
Engineering Director / CTO
Build the operating system around engineering: roadmap quality, team design, architecture, accountability, and executive translation.
- Org design
- Portfolio prioritization
- Manager development
- Business and technical alignment
Current readiness 66%
Longer horizon
Founder / Institutional Builder
Turn Conduit and related systems into measurable proof that complex organizations can preserve intent and improve execution.
- Product-market fit
- Capital formation
- Team building
- Institutional governance
Current readiness 58%
Becoming
Preparing for greater technical authority
The Staff+ and Principal journey is part of the story, not a résumé sidebar. This is the public record of how I am preparing to hold more technical authority without repeating the leadership patterns that previously created unnecessary friction.
Preparation principle: fewer generic problems, more high-fidelity
practice under the constraints of the actual role.
Principal Engineer plan
Architecture, influence, and interview execution
Coding
Timed implementation, data structures, graph traversal, concurrency reasoning, debugging, and clean communication under pressure.
System design
Requirements, architecture, scale, consistency, reliability, security, observability, cost, migration, and failure-mode analysis.
Leadership evidence
Stories of influence, conflict, failure, repair, ambiguity, prioritization, mentoring, executive communication, and organizational impact.
Becoming · Leadership receipts
Engineering my leadership
I am developing a body of work about how technically strong people become organizationally effective—especially when they are comfortable operating in conflict.
The core realization
I had a no-drama policy in my personal life but did not apply it consistently in my professional life. Because I could perform in conflict, I sometimes treated conflict as less costly than it was.
The old framing
“I am unwilling to work with bad leaders” protected standards but also gave me permission to classify people, retain judgment, and create tension that did not always improve the outcome.
The new framing
Truth must be paired with timing, relationship, proportionality, repair, and a distinction between a correctable mistake and a dangerous pattern.
The public series
Interview former managers, peers, and collaborators. Ask where my strengths became liabilities, when trust declined, what conflict was unnecessary, and what changed afterward.
Questions I am willing to ask publicly
When did my technical strength become an organizational liability?
What truth was I right about but ineffective at delivering?
When did I create conflict that was not necessary?
When did you stop trusting my judgment or approach?
What would make you trust me with greater authority today?
What should I preserve rather than “fix” about myself?
Describe behavior without turning it into identity
Separate diagnosis from judgment.
Optimize for changed outcomes
Being correct is not the same as being effective.
Treat conflict as a scarce resource
Escalation has organizational cost and must be proportional.
Make repair observable
A trustworthy record includes what changed after failure.
Trajectory
The next five and ten years
The path is sequenced around four forms of capital: capability, credibility, financial independence, and public trust.
0–2 years Carry Staff+ scope Secure Staff+/Principal scope. Build interview strength. Publish technical and leadership work.
1–3 years Make Conduit falsifiable Produce measurable evidence that organizational intent and work can be preserved across tools.
3–5 years Build institutional receipts Build revenue, a durable team, foster-care pilots, and institutional receipts.
5–7 years Shift to owned leverage Move from labor income toward owned leverage, investments, and advisory influence.
5–10 years Build civic credibility Build a governance record through boards, commissions, policy pilots, or local and state initiatives.
8–10 years Evaluate national scope Consider national office only with a constituency, a record, a coalition, and a defensible theory of governing.
Core trajectory: foster care is both the origin and the destination.
Engineering, leadership, Conduit, capital, and possible public office are the
capability-building path between them.
Now
The current work
Daily and weekly notes from the Staff+ journey, Conduit, leadership repair, and institutional thinking. Written as it happens, not reconstructed afterward.
Building the Fosterman publishing system
Turning the website from a static artifact into a daily operating system.
websitepublishingsystems
Artifacts
The raw proof behind the work
This is not a generic blog. It is an archive of letters, receipts, field notes, maps, technical papers, reflections, transcripts, and selected raw material that proves the work has been lived—not merely branded.
Receipts
Claims paired with proof
Job losses, product decisions, leadership mistakes, repairs, code, outcomes, and the evidence beneath the narrative.
Letters
Writing that became a way to heal
Letters to Skylar, letters to younger versions of myself, and writing that helped make difficult thoughts speakable.
Field Notes
What the systems reveal
Observations from engineering teams, foster care, healthcare, community building, leadership, and institutional failure.
Maps
Models for navigating complexity
System diagrams, knowledge graphs, mind maps, decision frameworks, organizational traces, and the geometry of Conduit.
Reflections
The person inside the system
Conflict, protectors, identity, ambition, fatherhood, self-loyalty, regulation, and becoming worthy of greater authority.
Technical Papers
The engineering body of work
Conduit, Staff+ preparation, architecture reviews, reliability analysis, AI systems, and implementation case studies.
Burn the Cape. Keep the Map.
The difference between saving people and leaving behind something they can navigate.
mentorshipleadershipFosterman
Digital identity
One site, two doors
The site is deployed once and reachable through both the public brand and the personal identity. The domains reinforce each other rather than splitting the audience or the search authority.
Primary
iamfosterman.com
The canonical public site and content brand. Videos, essays, foster-care work, leadership reflections, Conduit, and the broader trajectory all live here.
Social convention: @iamfosterman wherever available.
Personal continuity
sirrele.com
The personal domain resolves to the same site, preserving my name as a permanent professional entry point.
Behavior: 301 redirect sirrele.com → iamfosterman.com, while keeping Sirrele prominent in page titles and structured metadata.
Contact
Build, challenge, or collaborate with me.
I am interested in technically ambitious software roles, institutional design, organizational intelligence, foster-care systems, and conversations that make the work more rigorous.
Good reasons to reach out
Staff+ or Principal engineering roles
Technical leadership and architecture
Conduit design partners
Foster-care systems and pilots
Leadership interviews and candid feedback
Find the work:
iamfosterman.com — primary public brand
sirrele.com — personal and professional domain
@iamfosterman — preferred social handle
iamfosterman.com — primary public brand
sirrele.com — personal and professional domain
@iamfosterman — preferred social handle