BRADLEY
SAUCIER

VIPER1 | STAKEHOLDER BRIEFING

Verification-first engineering leadership

Business Operations Manager - Anduril Industries - USAF Combat Controller (Ret.) - Wharton MBA Program for Executives - Class 52

CALLSIGN: VIPER1 POSTURE: UNCLASSIFIED EDU: WHARTON EMBA C52 FOCUS: VERIFICATION-FIRST

Purpose: provide an unclassified, fast-read briefing on how I lead engineering delivery. Current leadership development includes Wharton's MBA Program for Executives, Class 52, San Francisco cohort. Public repos on GitHub hold the runnable artifacts and documentation.

Open GitHub Go to core capabilities How I run delivery

What I deliver: Intent translated into bounded scope, verification gates, and auditable evidence.
How I work: Testable claims. Explicit constraints. Reproducible steps from a clean environment.
Limits: Unclassified only. No proprietary, sensitive, or export-controlled technical data.

PROFILE

UNCLASSIFIED PUBLIC BRIEF

Python C++ Java Linux Docker CI Wharton EMBA

Focus

Assurance cases, durable CI gates, formal methods, software security

Leadership development

Wharton MBA Program for Executives - Class 52 - San Francisco cohort.

Privacy

No analytics by default. Static, self-contained page.

Operating model

Execution sequence

Define: State the objective, constraints, and failure modes before implementation begins.
Bound: Write acceptance criteria that are measurable inside an explicit risk envelope.
Verify: Make credibility runnable: tests, CI gates, repeatable commands, and expected outputs.
Record: Capture assumptions, trade-offs, and decision logs that survive turnover.

Stakeholder standard

Clarity: Unambiguous scope. Testable claims only.
Traceability: Evidence trails back to requirements. No slideware.
Risk framing: Unknowns are bounded. Edge cases fail during verification, not after delivery.
Routing: Work enters with repro steps, constraints, and definition of done.

Assurance

Assurance pattern I enforce

I do not treat documentation as marketing. It is the control surface for verification and audit.

Claim:
  What we assert is true (bounded and testable)

Context:
  Constraints, interfaces, assumptions, risk envelope

Evidence:
  Tests, CI gates, logs, and traceable artifacts

Verify:
  Commands and expected outputs from a clean environment

Unclassified abstract method

Describe: The class of problem and the operational constraints (not program specifics).
Show: Generic methods and verification discipline via public artifacts.
Avoid: Parameters, sensitive timelines, platform identifiers, and export-controlled technical details.

Core capabilities

Demonstrations of verification-first engineering in control systems, autonomy, and security. Each artifact emphasizes bounded claims, explicit constraints, and runnable evidence.

OpsNormal

FLAGSHIP

Local-only operator readiness tracking with five fixed sectors, three states, and a trailing 30-day signal. Built as a static PWA with no accounts, backend, telemetry, or sync layer.

Emphasis: IndexedDB persistence, export integrity checks, verified recovery paths, and CI-verified release artifacts.
CCT relevance: Clear operating boundary, durable backup discipline, and readiness signal preserved under constraint.
Link: Open repository

READOUT: REACT - TYPESCRIPT - INDEXEDDB - LOCAL-ONLY - PWA - RELEASE GATES

Robust UAV Hover Control

FLAGSHIP

Verification-focused control-system simulation benchmarking naive PID against filtered anti-windup PID under actuator saturation and seeded turbulence. Built to show bounded assurance under real hardware constraints.

Emphasis: RK4 integration, saturation limits, anti-windup control, and deterministic turbulence inputs.
CCT relevance: Failure modes defined, flight envelope bounded, and robustness verified under constraint.
Link: Open repository

READOUT: PYTHON - RK4 - PID - ANTI-WINDUP - SATURATION - SEEDED TURBULENCE

Autonomy verification limits

REFERENCE

Demonstrates why universal, unbounded autonomy verification fails in the general case, and how bounded assurance still produces usable guarantees.

Emphasis: Undecidability limits, scope reduction, and reproducible proof paths.
Link: Open repository

READOUT: REDUCTIONS - CLEAN ENV REPRO - EXPECTED OUTPUTS - BOUNDED CLAIMS

Security evidence pack

EVIDENCE PACK

Evidence-driven security posture with hardening actions, verification notes, and traceable artifacts organized for audit and reproduction.

Emphasis: Threat-to-control traceability, hardening evidence, and audit-ready verification.
Link: Open repository

READOUT: HARDENING STEPS - COMMANDS RUN - LOGS - TRACEABLE ARTIFACTS

Supporting artifacts

Academic and supporting demonstrations in deterministic behavior, test discipline, and UI-UX traceability.

Deterministic course planner

ACADEMIC

Defensive ingestion and predictable behavior under constraint. Validates prerequisites and outputs a sorted catalog deterministically.

Emphasis: Deterministic data structures, input validation, and repeatable build output.
Link: Open repository

READOUT: DETERMINISTIC OUTPUT - INPUT VALIDATION - BUILD RUN STEPS

Test discipline

REFERENCE

Deterministic services, JUnit suites, and JaCoCo enforcement used to keep claims testable and changes auditable.

Emphasis: JUnit services, coverage gates, and reproducible CI verification.
Link: Open repository

READOUT: JUNIT - JACOCO - CI GATES - REGRESSION DISCIPLINE

UI-UX evidence locker

CASE STUDY

Traceability, risk register discipline, and design tokens backed by a documented review and verification path.

Emphasis: Requirements traceability, risk registers, and documented review paths.
Link: Open repository

READOUT: TRACEABILITY - RISK REGISTER - DESIGN TOKENS - REVIEW PATH

Contact

Routing

GitHub: github.com/bradsaucier
Repo topics: Open an issue in the relevant repository with evidence and repro steps.
General: Submit queries through GitHub issue with constraints, definition of done, and verification evidence.

SOP: engagement routing

Copy this template into a new GitHub issue when the work requires review, reproduction, or follow-up.

Context:
  System:
  Environment:
  What changed:

Constraints:
  Time:
  Safety:
  Interfaces:
  Policy:
  Dependencies:

Definition of done:
  Tests:
  Checks:
  Artifacts:
  Acceptance criteria:

Evidence:
  Repro steps:
  Commands run:
  Output or logs:
  Links:

BRADLEYSAUCIER