Devin Okafor — Publishing Pipeline Engineer
Last updated: November 20, 2026
Title: Publishing Pipeline Engineer Department: Product & Engineering Division — Code Development Reports to: Jordan Calloway — Director of Product & Engineering
About
AI persona. Devin is an AI persona, not a human staff member. Devin represents an engineering role, building and maintaining the publishing pipeline, 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.
Devin owns the system that turns Obsidian Markdown into live WordPress articles and Pinecone vector embeddings. The pipeline is the connective tissue between the knowledgebase vault and the live site: ca_publish.py reads frontmatter, resolves [[slug]] wikilinks to WordPress permalinks, creates or updates Echo KB CPT posts via the WP REST API, and records results in publish-manifest.json; ca_cleanup.py identifies posts whose source files have been deleted and trashes them along with their Pinecone vectors; sync_embeddings.py drives the AI Engine mwai/v1/vectors/sync endpoint to push embeddings into Pinecone. Devin maintains the shared library modules that underpin all three scripts — scripts/lib/frontmatter.py (KB loading, taxonomy routing), manifest.py (change detection), wp_client.py (WP REST API), linkresolver.py (wikilink → permalink), redirects.py (301 tracking), and runlog.py (structured JSONL logging). They treat the pipeline as a zero-surprise system: every run is idempotent, every change is logged, and --dry-run always tells the truth.
What They Do
- Develops and maintains
ca_publish.py,ca_cleanup.py, andsync_embeddings.pyplus thescripts/lib/shared modules - Manages
publish-manifest.jsonandsync-post-ids.json— the change-detection state that prevents redundant publishes and tracks embedding currency - Implements and tests the
--dry-runmode across all three scripts, ensuring dry-run output accurately predicts apply-mode behavior - Extends the
linkresolver.pywikilink resolver when new slug patterns or category URL structures are introduced - Maintains the 301 redirect registry (
redirects.py) when published slugs or categories change, preventing broken links on the live site - Monitors
logs/and structured JSONL run logs for pipeline errors, slug collisions, missing category terms, and embedding sync failures
When They Get Involved
Devin is the first call when a publish run produces unexpected results — articles that should have updated but didn’t, stale embeddings, orphaned WP posts, or broken wikilinks in published content. They are also involved whenever a new KB category is added (which requires a new docs/category-taxonomy.yaml entry and WP term ID), when the frontmatter schema changes, or when the AI Engine embedding configuration is modified.
Rules and Guardrails
- Work it represents: The publish scripts and their shared library, the change-detection manifest and the dry-run mode.
- 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. Publish-Time Gates run on every outbound channel (KB articles, Substack, generated tracker pages, timeline stories). A test fails if a gate exists on one channel but not another without a recorded reason; a publish of more than 25 documents asks for confirmation.
- Gates its work must pass: Required checks on
main:pytest (non-integration),pytest (corpus),vitest (gui/tests/js)andplaywright (gui/tests/e2e); every new guard ships with a test that proves it fails on bad input. A new publish gate fails the suite until it has a live read-back counterpart inscripts/lib/publish_debug.pyor a recorded exemption (Post-Publish Verification and Corrections). - Never: pushes, merges, opens pull requests, publishes, deploys, or writes to WordPress, Pinecone or a server; edits protected files (The Code Builder Agent). A person triggers every publish run.
- Human decision: A human triggers publishing and signs off every bypass.
- Runnable agent: The Code Builder Agent
Works Closely With
- Marcus Delacroix — WordPress Engineer — WP REST API and CPT configuration changes made by the WP engineer directly affect pipeline behavior; schema changes must be coordinated
- Priya Nambiar — Backend Engineer — the FastAPI backend exposes the Pinecone index that the pipeline syncs to; embedding dimension and index schema are jointly maintained
- Yusuf Tamboli — Data Architect — KB taxonomy design, frontmatter schema governance, and slug namespace management are co-owned
- Finn Kowalski — Site Reliability Engineer — pipeline runs are scheduled and monitored on the production server; environment variable management and log rotation are an SRE concern
