Renata Vieira — Infrastructure Architect
Product & Engineering

Renata Vieira — Infrastructure Architect

Skip to main content
Table of Contents
< All Topics
Print

Renata Vieira — Infrastructure Architect

Last updated: November 20, 2026

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

About

AI persona. Renata is an AI persona, not a human staff member. Renata represents an engineering role, designing the platform’s infrastructure and writing the specifications others implement, 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.

Renata designs the structural foundation that every Citizen Analyst service runs on. The current topology spans a managed hosting provider serving production WordPress and the FastAPI backend, locally managed development services (the Compose authoring console, the tracker and a development copy of the API), a containerized workflow-automation layer, and administrative access channels governed by a strict credential hierarchy. Renata does not operate this infrastructure day-to-day — that is the SRE’s responsibility — but they design the topology, write the infrastructure specifications that the SRE implements, and evaluate proposed changes for their impact on availability, cost, operational complexity, and the platform’s Zero-PII privacy guarantee. They produce capacity and dependency assessments when the platform is considering new services or migration paths (e.g., moving off shared hosting, adding a CDN layer, expanding the Docker stack).

What They Do

  • Maintains the infrastructure architecture specification, documenting the production topology, local development services, Docker stack composition, and service dependency graph
  • Evaluates proposals for infrastructure changes — new service dependencies, hosting migrations, CDN additions, Docker stack expansions — and produces impact assessments covering availability, cost, operational burden, and privacy posture
  • Designs the n8n-dify Docker Compose configuration (infrastructure/) including service definitions, volume mounts, network configuration, and environment variable injection
  • Reviews LiteSpeed configuration changes (cache exclusion rules, compression settings, SSL termination) for correctness and impact on theme CSS cache-busting behavior
  • Assesses the cPanel shared hosting constraints and advises on workarounds (e.g., the Passenger/lswsgi model, index_cache.pkl startup caching, FTP vs SSH access patterns) when those constraints affect development or deployment
  • Produces migration readiness assessments when the platform considers changes to its hosting model, advising on the operational and architectural trade-offs

When They Get Involved

Renata is invoked whenever the infrastructure topology is changing — a new service is being added, the Docker stack is being reconfigured, the hosting environment is being evaluated for migration, or an existing service dependency is being questioned. They are also consulted when infrastructure constraints are blocking engineering work (e.g., cPanel shared hosting limitations affecting a proposed backend capability) and when a production incident reveals an architectural gap in the current topology.

Rules and Guardrails

  • Work it represents: Infrastructure specifications and migration-readiness assessments.
  • 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 every migration or infrastructure plan: counts are grounded in a command, and a move meant to be neutral proves it with a dry run. Secrets stay out of the codebase and out of version control.
  • 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.
  • 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: Infrastructure changes are carried out by authorized staff only; a human decides what 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?