BLUF | Current Focus | Evidence Locker | Capabilities | Doctrine | Intake | Background | Education | Contact | Boundaries
IDENTITY: Bradley Saucier
ROLE: Deputy Operations Manager - Anduril Industries
BACKGROUND: USAF Combat Controller (Ret.)
MISSION: Build and lead verification-first engineering teams that ship
testable claims, auditable changes, bounded risk, and
reproducible results.
OPERATING STANDARD: Deterministic where feasible - explicit bounds,
failure modes, and risk envelopes where not.
VERIFICATION SIGNAL: CI status and quality gates
tests (runnable)
traceable artifacts
decision logs (ADR)
CI STATUS:
I translate operational intent into engineering requirements and verified deliverables. If it is not testable or auditable, it is not a claim.
Standard
- Deterministic behavior where feasible.
- Explicit bounds, failure modes, and risk envelopes where it is not.
Output: Traceable requirements, CI/CD quality gates, documented risk envelopes, reproducible builds.
- Publishing repeatable assurance-case templates (claims, evidence trails, verification steps) - see autonomy-undecidability and artemis-security-evidence.
- Strengthening CI gates that survive turnover (assumptions, decision logs, reproducible runs) - see autonomy-undecidability quality-gate patterns.
- Advancing formal methods and software security through applied coursework artifacts - see Evidence Locker entries.
Each entry follows a compact assurance-case structure (CAE/GSN style): claim, context, evidence, and a verification path. Where supporting material cannot be published in full, it is mirrored as sanitized documentation in a public proxy repo and linked here.
| Project | Build |
|---|---|
| Computational Autonomy and Undecidability | |
| Artemis Security Evidence | |
| CS-300 Course Planner | |
Engineering: Mission-critical delivery, secure software practices, supply chain hygiene Tooling: C++20, Python, Java, SQL, GitHub Actions, CMake, Maven, Docker, Linux Stance: Explicit bounds, explicit failure modes, decision logs (ADR), reproducible builds
- Requirements translation - objectives into requirements, acceptance criteria, and verification methods.
- Risk-bounded delivery - define scope up front; document assumptions; ship within an explicit risk envelope.
- Decision logs - capture the why, not just the what; changes must survive turnover and audit.
- Simplicity under pressure - fewer moving parts, fewer failure modes. Hardware, software, and operator workflows are one system.
- Standards - testable claims, reproducible results, auditable changes.
Objective: [One sentence]
Constraints: [Time, tooling, platform]
Definition of Done: [Tests, docs, output artifact]
Verification: [How we will prove it works]
I apply 22 years of USAF Combat Control operational risk management to engineering work: explicit assumptions, clear acceptance criteria, and verification gates that hold up under audit. This profile focuses on personal methodology and public academic artifacts.
| Program | Institution |
|---|---|
| B.S. Computer Science (Project Management for STEM concentration) - in progress | Southern New Hampshire University |
| B.A. Economics | Columbia University |
| A.A.S. | Community College of the Air Force (CCAF) |
Primary: GitHub - https://github.com/bradsaucier Portfolio: https://viper1.me/ Preferred: open a GitHub Issue or Discussion in the relevant repo and follow the Intake Format above.
This profile reflects personal methodology and academic work only. It does not represent the views, policies, or proprietary methods of any current or former employer. No classified, controlled unclassified, or proprietary information is present. No export-controlled (ITAR or EAR) technical data is intended for publication here.