Full Writing Portfolio | Stephen Sweeney

Start here — four genres.

Compliance narrative

Audience Regulators, compliance officers, aviation technical writers

Demonstrates Compliance narrative with verifiable authoring trail and print-ready reference layout

Project context: Flightworks Systems is building governed autonomy for FAA Part 107 operations. FAA NPRM FAA-2025-1908 proposes a BVLOS framework — this sample maps product architecture to that docket before the rule is final.
Role & process: Sole author. AI-assisted drafting under governed review; regulatory facts pinned to docket, architecture claims bound to FlightLaw SP0 + Sentinel v0.2.0.
Challenges: Standalone-readable for readers with no AgentVector prior knowledge. Frame-by-frame evidence walkthrough without certification theater.
Results: Flagship portfolio sample — demonstrates compliance narrative genre with verifiable authoring trail and print-ready reference layout.

How-to guide

Audience Developers evaluating the governance stack

Demonstrates Task-oriented procedural writing — prerequisites, steps, expected output, troubleshooting

Project context: Readers need a short path to run a local governance demo without reading the full architecture first.
Role & process: Author. Numbered steps for mock mode and local full stack; expected output called out explicitly.
Challenges: Keep invented vocabulary minimal; separate mock vs local stack requirements clearly.
Results: Strong scan sample for hiring reviewers who want procedural docs over essays.

API reference

Audience Integration engineers

Demonstrates Endpoint tables, request/response schemas, fail-closed semantics, SSE event shape

Project context: Integrators need a contract for evaluate / observability / SSE without reading the jurisdiction essay.
Role & process: Author. Reference layout bound to API_CONTRACT.md source docs.
Challenges: Document fail-closed behavior and error shapes without overstating hosted maturity.
Results: API-reference genre sample for platform / docs-engineer role reviews.

Concept essay · position paper

Audience Engineering leadership, platform architects

Demonstrates Position paper defining ten properties of a valid governed-autonomy implementation

Project context: AgentVector emerged from a practical question: why do autonomous AI agents need a constitutional control plane separate from the acting system?
Role & process: Author and architect. Position paper defining ten properties of a valid governed-autonomy implementation.
Challenges: Argue for constitutional governance without checklist theater; address the composition problem raised in academic response to v2.1.
Results: Single framework thought-leadership slot in the featured tier — not the default first read.

All writing samples.