Stephen Sweeney · Systems Architecture & Technical Writing

Technical documentation for systems where ambiguity is expensive.

I turn complex software, autonomous systems, and regulated workflows into architecture docs, API references, compliance narratives, and operator guidance that engineers can implement and reviewers can trust.

25+ years engineering · Aviation · AI governance Architecture · APIs · Compliance · Docs-as-code
AgentVector proof chain Five layers from Elements of Coherence down to Verdict, with authority flowing downward and a coherence verification loop tracing each verdict back up to its source. Elements of coherence Definitions, postulates, propositions grounds The Codex Eleven Laws, four groups defines Enforcement kernels SwiftVector, TSVector, RustVector composed into Domain jurisdictions Flight, desktop, chronicle produce Verdict Allow, deny, escalate Coherence verifier Replay and audit Solid path: authority flows down. Dashed path: every verdict is traced back to its source. Full framework reference →

Framework reference (secondary) — samples first.

Governance defined

Governance defines what the agent may do, what it may never touch, what requires human escalation, how evidence is recorded, and how decisions are replayed and audited. It is not a behavioral prompt. It is a structural constraint — enforced before execution, not after.

The framework

Four Law groups. Eleven Laws in the Codex. Language-specific enforcement kernels. Domain jurisdictions that apply the Laws to specific operational contexts.

AgentVector Codex
Constitutional framework for governed AI systems

Eleven Laws in four groups. The reducer pattern, evidence chain structure, and composability rules for jurisdiction design.

Full Codex specification →
Enforcement Kernels
Web overview · language-specific runtime guarantees

SwiftVector · TSVector · RustVector. Each kernel compiles Laws into language-specific guarantees — actor isolation, pure functions, ARC memory management.

Framework overview (web) →
Composable Laws
Policy primitives that adapt by operational domain

Observation, Resource, Spatial, Authority — domain-agnostic primitives that compose differently per jurisdiction while remaining architecturally identical.

Law registry →
Why governance-first

The governance layer is not an afterthought bolted onto an existing AI system. It is the foundation on which the AI system is built. Policy is defined before the first agent call. Every action is evaluated before execution. The constitutional architecture means the system can demonstrate compliance on demand — not merely claim it.

The same Laws.
Different operational contexts.

The constitutional architecture composes differently across aviation, desktop agents, and narrative AI. Same kernel pattern. Replayable evidence in every jurisdiction. Writing samples indexed at /portfolio →

FlightLaw · SwiftVector + RustVector
Flightworks Sentinel

AI can propose. Flightworks Sentinel decides. The record proves it. Sits between your AI layer and your autopilot — governing what AI is permitted to propose, issuing typed verdicts, and preserving replayable evidence of every decision.

Active development
Vigil · SwiftVector
Light Station

Operator console for governed AI systems. Persistent operating picture of agent proposals, policy verdicts, evidence chains, and human escalations — across any AgentVector jurisdiction.

Reference implementation · v0.2.0
Chronicler · SwiftVector
Chronicle Quest

Human authorship protected as a formal governance constraint. AI may draft prose; it cannot decide fate.

Active development

Where to start.

Stephen Sweeney is a principal systems architect and technical writer with 25+ years in software engineering. His work spans production software for business aviation, consumer-scale search and geospatial platforms, autonomous systems, and deterministic AI governance. This site presents the documentation evidence behind that work; framework research appears under Field Operations.

Architecture · documentation · governed autonomy

Need a systems-minded technical writer?

For architecture, technical leadership, developer documentation, regulated-system writing, or consulting, get in touch.