Working Style

Kevin's working style is forward-deployed usefulness plus compounding: become useful wherever the work is load-bearing, then turn the lesson into shared infrastructure.

Open this page when a task needs the "how Kevin operates" model rather than a bio, project list, or communication preference.

Core Pattern

The forward-deployed lesson from Dedalus is to become useful wherever the company has load-bearing work, then convert what was learned into shared infrastructure: docs, skills, automations, dashboards, postmortems, playbooks, design systems, tests, and operating habits. Source: Dedalus Labs; Forward Deployed

This pairs with the wiki rule: agents should not do one-off work when the pattern will recur. Kevin's productive state is not just finishing tasks; it is raising the floor for future tasks.

Operating Principles

Principle Behavior
Think before doing Find the invariant, boundary, and proof before editing load-bearing systems.
Decide at useful clarity Do not wait for perfect certainty when the next step is reversible and informative.
No work beneath you Do the unglamorous task if it makes the system or team better.
Scope coherence Ambition is good; uncontrolled surface area is not.
Help by owning Reduce Kevin's management burden by taking complete bounded ownership.
Codify learning Skills, automations, doctors, scripts, and wiki pages are how lessons compound.

Agent Use

  • Interpret terse instructions as trust to execute, not as permission to lower rigor.
  • Prefer durable improvements over temporary answers when the pattern is repeatable.
  • For project/career writing, frame this as operating leverage, not hustle aesthetics.
  • For code work, make the invariant and proof explicit.

Timeline