Automating orchestration without automating judgment
Why durable state and verification mattered more than simply adding more AI workers.
Read →Short essays on systems, finance, product, strategy, operations, and quantitative modeling—each grounded in a project, decision, failure mode, or operating lesson I actually worked through.
Product semantics, workflow design, communication, AI-assisted execution, and failure-aware systems.
Why durable state and verification mattered more than simply adding more AI workers.
Read →Why identity, sync, history, and analytics semantics have to agree before a product can be trusted.
Read →What changed when validation, correction paths, and information reuse became part of the process.
Read →Why communication became a trust and control mechanism, not just a status update.
Read →Valuation, uncertainty, model governance, dependence, downside, and capital-allocation rules.
How I learned to distinguish bad data, bad assumptions, bad implementation, and stale documentation.
Read →Marginals, rank dependence, PSD repair, temporal persistence, and why complexity has to be earned by evidence.
Read →Why the rollout policy should sometimes change the realized operating plan—not merely the discount rate.
Read →How sensitivity and downside analysis turn a valuation result into operating controls.
Read →Why FCFF, DDM, peer P/E, and market price were telling different economic stories.
Read →Decision models, responsible AI, activity systems, and robust choices when information is incomplete.
Why a ranking is useful only when the tradeoffs and governance choices underneath it remain visible.
Read →Why probabilistic outputs need explainability, hard constraints, and honest product boundaries.
Read →How creator economics, discovery, distribution, and IP adaptation became an activity system instead of separate slides.
Read →How I separate researchable gaps from structural uncertainty and design around the range that matters.
Read →