>_ Verification-first engineering - testable claims, auditable changes, bounded risk.
Deputy Operations Manager - Anduril Industries - USAF Combat Controller (Ret.)
CLASSIFICATION: UNCLASSIFIED // PUBLIC RELEASE
OWNER: SAUCIER, BRADLEY // VIPER1
Important
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. Where not feasible - explicit bounds, failure modes, risk envelopes.
Output - Traceable requirements, CI quality gates, documented risk envelopes, reproducible builds.
Identity block (YAML)
SYSTEM : viper1.me
PROFILE : Operator mindset applied to engineering (verification-first)
NAME : Bradley Saucier
ROLE : Deputy Operations Manager - Anduril Industries
SERVICE : USAF Combat Controller (Ret.)
MISSION : Build and lead verification-first engineering teams that ship
testable claims, auditable changes, bounded risk, and
reproducible results.
STANDARD : Deterministic where feasible.
Where not feasible - explicit bounds, failure modes, risk envelopes.
SIGNALS : CI status and quality gates
runnable tests
traceable artifacts
decision logs (ADR)- Publishing repeatable assurance-case templates (claims, evidence trails, verification steps).
- Hardening CI gates that survive turnover (assumptions, decision logs, reproducible runs).
- Building public, scrubbed evidence artifacts aligned to coursework and professional practice.
Each entry follows a compact assurance-case structure (CAE or GSN style): claim, context, evidence, verification path.
Evidence format (CAE or GSN style)
CLAIM : What is asserted (testable statement).
CONTEXT : Assumptions, environment, constraints.
EVIDENCE : Artifacts (docs, logs, reports, test outputs).
VERIFICATION: Steps to reproduce and validate evidence.
RISK : Explicit envelope, failure modes, residual risk.
| Project | Focus | Gate |
|---|---|---|
| bradsaucier/autonomy-undecidability | Assurance-case templates for computational autonomy |  |
| bradsaucier/artemis-security-evidence | Security evidence trails and verification steps |  |
| bradsaucier/CS300-CoursePlanner | Algorithmic planning structures (academic artifact) |  |
| bradsaucier/test-discipline | Deterministic services, JUnit suites, JaCoCo enforcement (CS-320) |  |
| bradsaucier/cct-ui-evidence-locker | UI-UX evidence locker: traceability, risk register, design tokens (CS-319) |  |
| Domain | Capability |
|---|---|
| Engineering | Mission-critical delivery, secure software practices, supply chain hygiene |
| Verification | Unit and integration testing, deterministic seams, CI gate enforcement, regression discipline |
| UI-UX | Constraint-first interface design, traceability from requirements to screens, accessibility posture |
| Tooling | C++20, Python, Java, SQL, GitHub Actions, CMake, Maven, Docker, Linux |
| Operating stance | Explicit bounds, explicit failure modes, decision logs (ADR), reproducible builds |
- Requirements translation - Objectives into requirements, acceptance criteria, 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, operator workflows are one system.
Preferred format for collaboration requests. Expand for the full template.
INTAKE REQUEST TEMPLATE
================================================================================
INTAKE REQUEST
--------------------------------------------------------------------------------
Objective : [One sentence]
Constraints : [Time, tooling, platform, security constraints]
Definition of Done: [Tests, docs, output artifact]
Verification : [How we will prove it works]
Risk Envelope : [What can fail, what is acceptable, what is not]
--------------------------------------------------------------------------------
Links : [Repo, issue, docs]
Attachments : [Logs, screenshots, repro steps]
================================================================================
Background
I apply 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.
Education
| 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) |
| Method | Detail |
|---|---|
| Preferred | Open an Issue or Discussion in the relevant repo and use the Intake Format above |
| Web | https://viper1.me/ |
Caution
BOUNDARIES 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 information (CUI), or export-controlled (ITAR or EAR) technical data is intended for publication here.
// END TRANSMISSION
// VERIFICATION HASH: 90ba5e401f43634423d8a62e19165a6f1c04ed8e6b500e4fc238b8789ebd4f37