Writing Portfolio

Documentation samples.

Technical writing portfolio for governed AI systems — each sample labeled by genre, audience, and what it demonstrates as a writing artifact. Start with the four featured samples below; the full index is tiered beneath.

For authoring process and review workflow, see the process page. For framework context, see home and Field Operations.

Contact for roles → How I write →
Featured samples

Start here — four genres.

01
Compliance narrative

Part 108 BVLOS Scenario

Audience Regulators, compliance officers, aviation technical writers
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.
Read sample →
02
Concept essay · position paper

The Agency Paradox

Audience Engineering leadership, platform architects
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
Foundation essay for the framework — cited across Agency Papers and Agent Statecraft series.
Read sample →
03
Governed architecture overview

AgentVector Architecture Overview

Audience Framework newcomers, technical writers, engineering managers
Project context
AgentVector spans philosophical foundation, constitutional specification, kernels, and domain jurisdictions — readers need a single governed doc that ties the layers together.
Role & process
Author. Source-bound technical writing with verdict contract, flow diagram, illustrative code, and authoring trail.
Challenges
Explain a multi-layer framework without collapsing layers; show governed authoring process, not just the architecture.
Results
Reference doc for framework onboarding — demonstrates docs-as-code with explicit source binding.
Read sample →
04
Architecture overview

Light Station Architecture

Audience Platform engineers, ops leads
Project context
Light Station is the desktop governance control plane — Vigil enforces AgentVector Laws for shell, browser, and filesystem scope on macOS.
Role & process
Author. Architecture overview with system boundaries, fail-closed UX tables, and honest shipped-vs-roadmap split.
Challenges
Document a living product where spec and code diverge; surface what ships vs what is planned without misleading readers.
Results
Runnable demo references and jurisdiction tags — shows product architecture doc genre at production fidelity.
Read sample →
Full portfolio 10 additional samples by genre
Product specification
Light Station Spec
Audience PMs, engineers implementing against a contract
Demonstrates Personas, invariants, Vigil HTTP contract summary, explicit non-goals
Read sample →
How-to guide
Light Station Quickstart
Audience Developers evaluating the governance stack
Demonstrates Task-oriented procedural writing — prerequisites, steps, expected output, troubleshooting
Read sample →
API reference
Vigil HTTP API
Audience Integration engineers
Demonstrates Endpoint tables, request/response schemas, fail-closed semantics, SSE event shape
Read sample →
Reference
Terminology Glossary
Audience Any reader new to the framework
Demonstrates Terminology management — invented terms mapped to industry equivalents
Read sample →
Architecture overview
Flightworks Architecture
Audience Systems architects, UAS engineers
Demonstrates Two-runtimes-one-kernel framing, MAVLink edge enforcement, hash-chained evidence
Read sample →
Constitutional specification
AgentVector Codex
Audience Framework implementers
Demonstrates Formal specification writing — Laws, kernels, conformance criteria
Read sample →
Research synthesis
Empirical Grounding for the Agency Paradox
Audience Engineering leadership, academic reviewers
Demonstrates Claim-traceability table mapping v2.3 amendments to documented research with evidence boundaries
Read sample →
API reference
AgentVector Law Registry
Audience Framework implementers, jurisdiction architects
Demonstrates Per-Law registry — purpose, primitives, composition, jurisdictions, verdict examples
Read sample →
Concept essay
Law at the Edge
Audience Safety-critical systems engineers
Demonstrates Regulatory framing without checklist theater
Read sample →
Architecture overview
Vigil Jurisdiction
Audience Desktop agent governance engineers
Demonstrates Cross-domain proof of the same constitutional pattern in production
Read sample →
For hiring teams

Recommended reading order.

Part 108 for compliance narrative · Agency Paradox for thought leadership · AgentVector Architecture for governed docs-as-code · Light Station for product architecture. Process and vocabulary are documented at /process.

For consulting engagements, see macsweeney.llc ↗.

Part 108 scenario → Agency Paradox → Contact for roles →