Skip to content
View bradsaucier's full-sized avatar
🫡
∀x ∈ MissionSpace, ∃ logic(x)
🫡
∀x ∈ MissionSpace, ∃ logic(x)

Block or report bradsaucier

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don't include any personal information such as legal names or email addresses. Markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
bradsaucier/README.md 
CLASSIFICATION: UNCLASSIFIED // PUBLIC RELEASE
OWNER: SAUCIER, BRADLEY // VIPER1

Bradley Saucier

>_ Verification-first engineering - testable claims, auditable changes, bounded risk.

Deputy Operations Manager - Anduril Industries - USAF Combat Controller (Ret.)

GitHub profile Portfolio

BLUF IDENTITY FOCUS EVIDENCE CAPABILITIES DOCTRINE INTAKE CONTACT BOUNDARIES
autonomy-undecidability quality-gate artemis-security-evidence docs-ci CS300-CoursePlanner ci

Bottom Line Up Front (BLUF)

Important

BOTTOM LINE UP FRONT I translate operational intent into engineering requirements and verified deliverables. If it is not testable or auditable, it is not a claim.

Standard

  1. Deterministic behavior where feasible.
  2. Where not feasible - explicit bounds, failure modes, and risk envelopes.

Output

  1. Traceable requirements.
  2. CI quality gates.
  3. Documented risk envelopes.
  4. Reproducible builds.

Identity

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)

Current Focus

  1. Publishing repeatable assurance-case templates (claims, evidence trails, verification steps).
  2. Hardening CI gates that survive turnover (assumptions, decision logs, reproducible runs).
  3. Building public, scrubbed evidence artifacts aligned to coursework and professional practice.

Evidence Locker

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.

Status Board

Project Focus Gate
bradsaucier/autonomy-undecidability Repeatable assurance-case templates for computational autonomy quality-gate
bradsaucier/artemis-security-evidence Security evidence trails and verification steps docs-ci
bradsaucier/CS300-CoursePlanner Algorithmic planning structures (academic artifact) ci

Capabilities

Domain Capability
Engineering Mission-critical delivery, secure software practices, supply chain hygiene
Tooling C++20, Python, Java, SQL, GitHub Actions, CMake, Maven, Docker, Linux
Operating stance Explicit bounds, explicit failure modes, decision logs (ADR), reproducible builds
Languages Tooling
Python C++20 Java SQL Docker Linux GitHub Actions CMake Maven

Doctrine

Principle Description
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
Standards Testable claims, reproducible results, auditable changes

Intake Format

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 and Education

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)

Contact

Method Link
GitHub https://github.com/bradsaucier
Portfolio https://viper1.me/
Preferred Open an Issue or Discussion in the relevant repo and use the Intake Format above

Boundaries

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

@bradsaucier's activity is private