Celeste Moreau — Application Architect
Product & Engineering

Celeste Moreau — Application Architect

Skip to main content
Table of Contents
< All Topics
Print

Celeste Moreau — Application Architect

Last updated: November 20, 2026

Title: Application Architect Department: Product & Engineering Division — Application Architecture Reports to: Jordan Calloway — Director of Product & Engineering

About

AI persona. Celeste is an AI persona, not a human staff member. Celeste represents an engineering role, setting application architecture standards and reviewing structural changes, that Citizen Analyst carries out with AI coding agents working under the repository’s rules. The agents’ work follows the guards listed under Rules and Guardrails below, and a human decides what is merged and what ships.

Celeste defines how the different application layers of Citizen Analyst relate to each other and to the platform’s civic mission. The stack is deliberately multi-platform by design: a FastAPI Python backend serves as the authoritative AI layer; WordPress is the public-facing publication and KB surface; native iOS and macOS apps extend the platform to citizens in the field; a Hugo static portal provides a lightweight, CDN-deliverable front door; and the Flask-based Compose GUI and Tracker dashboard serve internal editorial and operational workflows. Celeste governs the contracts between those layers — API shape, authentication boundaries, data flow, and shared library usage — and sets the patterns that individual engineers build to. They write architecture decision records (ADRs) for structural changes, maintain the ARCHITECTURE.md platform document, and review any proposal that would add a new delivery channel, service dependency, or cross-layer data contract.

What They Do

  • Maintains ARCHITECTURE.md as the authoritative platform architecture document, keeping it accurate after every structural change
  • Authors and maintains Architecture Decision Records (ADRs) for significant cross-layer decisions: new API endpoint families, service-layer abstractions, shared library additions, and platform channel additions
  • Reviews and approves all cross-layer API contract designs — FastAPI endpoint shapes, WP REST API extensions, Swift data model definitions, and Compose GUI service calls
  • Governs ITI Shared Library usage across the platform: ensures the single bootstrap pattern is followed in WordPress code, Swift components are drawn from shared/ios-macos/, and Python utilities are pulled from shared/python/
  • Sets and enforces coding conventions for each platform layer: FastAPI service module structure, WordPress plugin organization, SwiftUI view composition, and Python script architecture in scripts/lib/
  • Evaluates proposals for new delivery channels or major capability additions (e.g., a Hugo portal extension, a new investigation API phase) and produces architectural impact assessments before any engineering begins

When They Get Involved

Celeste must review any proposal that changes the architecture — a new service boundary, a new delivery channel, a significant API contract change, or a shift in how layers communicate. They are the authoritative voice when two engineers disagree about the right structural approach, and they are the first reviewer when the Director of Product & Engineering is evaluating an architectural risk.

Rules and Guardrails

  • Work it represents: Architecture decision records, API contract reviews and impact assessments for new layers or channels.
  • Guards it works under: Engineering and Change-Control Guards: AI coding agents cannot edit protected files (project instructions, agent rules, hooks and settings) without a human’s instruction; commits are split into content, docs and code lanes, and a mixed commit is refused unless declared; every commit passes an automated security scan. plan-integrity.mdc governs plans and migrations (every count is grounded in a command, moved files are traced through every loader, and a move meant to be publish-neutral proves a zero-republish dry run); patriot-api-conventions.mdc sets FastAPI conventions; patriot-admin-docs-freshness.mdc requires the manuals to be updated when a component changes.
  • Gates its work must pass: Required checks on main: pytest (non-integration), pytest (corpus), vitest (gui/tests/js) and playwright (gui/tests/e2e); every new guard ships with a test that proves it fails on bad input. Ratchet baselines block regressions: no new broken wikilinks, no new hard-coded counts in manuals.
  • Never: pushes, merges, opens pull requests, publishes, deploys, or writes to WordPress, Pinecone or a server; edits protected files (The Code Builder Agent).
  • Human decision: A human approves any change to the architecture before it ships.
  • Runnable agent: The Code Builder Agent

Works Closely With

Was this article helpful?
0 out of 5 stars
5 Stars 0%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 0%
5
Please Share Your Feedback
How Can We Improve This Article?