Patrick Duchesneau is founder and principal architect at Bookiji Inc. He designs multi-product boundaries, platform standards, and release gates — then directs a fleet of AI coding and ops agents to implement inside those rails.
This page shows how work is designed, delegated, verified, and kept under human authorization. It is a curated public view, not a claim that every control is finished everywhere.
3-minute tour
Step 1 of 3
Architecture, agent orchestration, and verification — each with one concrete example from the Bookiji operating model.
One company hub, many product repos, shared platform spine
Bookiji Inc at www.bookiji.com is the company portfolio hub. Each sibling product ships from its own repo and deploy. Shared Postgres (per environment tier) uses schema isolation — platform, jobhunt, kinetix, and other product schemas — rather than one monolithic database per app.
Shared Supabase spine (ADR-001 pattern)
Verified practice
Products own migrations in their repos. The platform schema holds cross-product concerns; product tables live in product schemas with row-level security enabled in the same migration that creates them.
Public company scope — PRODUCT_SCOPE.md and README describe www vs app.bookiji.com and N/A Supabase on this deploy.
Engineering handbook (prior) — Public /engineering copy documents fail-closed migration apply gate and per-product schema policy.
Architecture explorer
Select a product to see platform services it consumes, repo boundaries, and integrations — grounded in the public catalog and handbook.
Kinetix
Shipped
Performance and coaching for runners and coaches — kinetix.bookiji.com. Product data stays in the kinetix schema; not mixed with booking or career CRM tables.
Shared platform services
Shared Supabase project (product schema)
Platform auth identity patterns (Standard 03)
Vercel-hosted web app
Optional Sentry / health endpoints (Standard 12)
Integrations & boundaries
Curated Help with operator-reviewed knowledge reinjection (v1)
AI coaching layered on interpretable measurement signals
Public catalog — Company product grid lists Kinetix as Beta with performance market focus.
Help loop — Public engineering copy cites Kinetix Help curated reinjection as implemented control.
Global Fair Pricing is a shared platform resolver products can adopt — local market ladders with economic guardrails and provider-safe fallback. See the homepage block or umbrella docs for policy detail; adoption is per product rollout.
Case studies
Shared platform architecture
Verified practice
Problem
Seven sibling products would duplicate auth, migrations, billing policy, and ops hygiene — or drift apart with incompatible assumptions.
Patrick's decision
Adopt one Supabase project per environment tier with per-product schemas, numbered umbrella standards, and explicit www vs app.bookiji.com boundaries.
Agent contribution
Agents implement migrations and product features inside schema boundaries, run migration status gates, and update docs — without cross-repo drive-by changes unless the task requires it.
Verification
RLS enabled with table creation; optional rls:verify from umbrella; /api/health on deployable surfaces; migration gate before schema-dependent diagnosis.
Limitations: This company deploy (bookiji-www) intentionally has no Supabase runtime. Not every product has adopted every platform capability (e.g. Global Fair Pricing rollout is per product).
ADR-001 pattern (public refs) — README points to umbrella PLATFORM_ARCHITECTURE and EXPLICIT_EXCEPTION for company portal.
Agent-directed delivery
Implemented control
Problem
Fast AI-generated diffs without gates create unreviewable change, secret risk, and “shipped” language that outruns evidence.
Patrick's decision
Agents open PRs; merges require review, pasted check output, passing preview build, and founder OK for migrations and production deploy batches.
Agent contribution
Implementation, test runs, evidence gathering, issue updates, and preview deploy preparation — coordinated by a PM-style dispatch model with GitHub Issues as system of record.
Verification
Lint, type-check, test suite, next build; PR template traceability; work reconciliation against Bookiji Delivery; NOT_RUN when a check did not execute.
Limitations: Prompteus adaptive routing and full portfolio automation are not claimed live. GitHub Actions is not release authority for Bookiji Inc.
Direct CI/CD policy — Public copy states GitHub is source/review; Vercel Git deploy on product repos.
Curated AI support
Implemented control
Problem
Support bots that invent answers or auto-ingest tickets into FAQ erode trust and leak unreviewed content into customer-facing Help.
Patrick's decision
Standardize Help as curated knowledge plus controlled escalation; reinject resolved tickets only after operator review (JobHuntrX reference, Kinetix v1).
Agent contribution
Draft help articles, retrieval wiring, and product-local support flows — under Help Center standard and Maia persona boundaries.
Verification
Product-local support queues; Ops Center federated index holds redacted pointers only; public maturity labels (Beta / Internal) on grid.
Limitations: Not a company-wide single RAG product. Portfolio-wide Help loop rollout is in progress. Ops Center does not store conversation bodies.
Prior /engineering — Documented curated retrieval vs auto-FAQ reinjection and Ops Center pointer-only index.
Agents accelerate implementation. Patrick keeps authorization for scope, public claims, production schema apply, production deploy batches, and sensitive configuration.
Try a sibling product
JobHuntrX remains a controlled Beta preview — useful for seeing structured workflow and Help patterns, not for revenue or launch claims.