Selected work

Selected Strategic Work

Sanitized public evidence across defense technology strategy, mission systems, modernization, capture, transition, and governed autonomy.

Explore capabilities Profile

Enterprise policy

DoD Software Policy and Enterprise Governance

From PDFs to Pull Requests Profile

Mission problem

Defense software guidance often lands as static compliance language instead of execution-ready architecture, controls, acquisition choices, and delivery practices.

My role

Served in senior technical-strategy and solution-architecture roles supporting DoD CIO software modernization, policy drafting, DevSecOps guidance, AI4SDLC governance, and policy-to-execution translation.

Practical value

Helps senior leaders turn policy into executable modernization systems that can be governed, assessed, and improved over time.

Approach

  • Connected software modernization, cloud, DevSecOps, cyber, acquisition, and enterprise governance communities.
  • Translated policy intent into architecture patterns, implementation guardrails, and delivery-system expectations.
  • Used direct technical experience to keep enterprise guidance grounded in how teams actually build, secure, and ship software.

Transition

Technology Insertion and Mission Discovery

Technology insertion note Capability: Technology Insertion

Mission problem

Emerging technology demonstrations can create excitement without producing operational adoption, transition ownership, integration paths, or scale decisions.

My role

Supported modernization and emerging-technology strategy across mission systems, cloud, software, data, AI, and operational-transition contexts.

Practical value

Turns technical access into transition discipline so promising capability has a path from discovery to funded operational use.

Approach

  • Start with program immersion and operational problem framing before solution advocacy.
  • Design transition pathways around owners, funding options, integration constraints, acceptance criteria, and delivery evidence.
  • Use evidence to decide when to scale, reshape, or stop an insertion effort.

Growth

Defense Growth and Technical Capture

Defense growth note Capability: Technical Capture

Mission problem

Capture teams can gain customer access without converting it into differentiated technical positions, executable solution architecture, and credible proposal evidence.

My role

Provides solution architecture, technical capture, proposal solutioning, white-paper development, emerging-technology assessment, and strategic opportunity shaping support.

Practical value

Improves the path from opportunity identification to capture strategy, proposal architecture, and executable delivery posture.

Approach

  • Sense demand signals across programs, policy, budget, operational pain, industry days, and delivery evidence.
  • Shape solution architecture around mission truth, technical feasibility, transition constraints, and partner alignment.
  • Turn discriminators into claims that can survive proposal review and delivery execution.

Mission systems

Digital and Mission Engineering

Digital engineering note Capability: Mission & Digital Engineering

Mission problem

Systems engineering, digital engineering, software, data, architecture, acquisition, and operational feedback often live in separate decision loops.

My role

Worked across Navy and Marine Corps contexts spanning PEO Digital, NAVAIR, mission engineering, systems engineering, cloud, software, data, and modernization.

Practical value

Creates a shared decision system for technical teams, mission owners, and acquisition stakeholders.

Approach

  • Frame architecture around mission threads and decision points rather than artifact production alone.
  • Connect model-informed engineering, software delivery, data strategy, and acquisition evidence.
  • Use integration constraints and operational feedback to keep engineering decisions tied to mission outcomes.

AI governance

Governed AI and Autonomy

ACP-RA CAF-RA The Next AI Bottleneck Is Delegated Authority

Mission problem

AI and autonomy can move faster than existing authority, assurance, and accountability systems, especially in contested or degraded environments.

My role

Develops control-plane, continuous-assurance, trust-scope, and delegated-authority patterns for high-consequence defense AI and autonomy.

Practical value

Keeps autonomy a governed mission capability instead of an isolated model, demo, or tool integration.

Approach

  • Separate signal, trust, control, and assurance concerns so authority can be bounded and audited.
  • Design policy gates, operator override paths, telemetry, rollback, and evidence into the architecture.
  • Account for degraded connectivity, contested operations, and multi-agent coordination.