Founding Builders: The Engine Team Behind Bays Horizon
Most advisory firms were built for the industrial age: lots of paperwork, slow updates, and generic plans.
At Bays Horizon, we’re doing something different.
We’re building our own AI‑driven engine — private, secure, and tailored to how we serve you — so that over time your planning feels:
• More proactive than reactive.
• More personal than generic.
• More transparent and auditable than “trust us.”
We don’t bolt AI tools on top of the old machine. We:
• Build from first principles.
• Harden real systems (not toys).
• Stay conscious of human welfare and wellness as we go.
• And redesign processes to actually work as we move from scarcity thinking to an abundance mindset.
Why is there a vertical farm on an advisory firm’s website?
Because the Vertical Farm is our first proving ground.
It gives us a real, physical system — crops, sensors, partners, revenue — where we can:
• Hard‑test our data and automation engine (ingestion, digital twins, thresholds, stats, auth, tests).
• Make one small piece of the world observable and optimizable.
• And prove that our approach works before we apply the same patterns more deeply to wealth, retirement, and life planning.
Everything we learn on the farm — contracts, data models, agent workflows, documentation style — is designed to carry forward into other domains:
• Energy, housing, local production.
• And most importantly for you: advisory and retirement planning.
The goal is simple:
• More sovereignty over your time, work, and wealth.
• Systems that care about human flourishing, not just quarterly numbers.
• Engines that are transparent and auditable, so you can see why we recommend what we recommend.
Below are some of the founding builders — the advanced engineers and systems thinkers — who are designing that engine. Their work on the Vertical Farm and our internal infrastructure is what will ultimately make your advisory experience faster, clearer, and more resilient.
Advanced Builder – Integration, Logging & Builder Experience
Destiny is an advanced builder focused on integration quality, logging standards, and the overall builder experience across the Bays Horizon engine. He’s been instrumental in designing the Log Engine posture, error‑resilient scraping and ingestion flows, and the narrated build patterns that make this ecosystem auditable and teachable instead of opaque.
What he’s building at BHA:
- Robust logging and narration patterns that turn one‑off builds into reusable playbooks for every future builder.
- Integration workflows and automations that pull external intelligence into the BHA Codex safely and repeatably.
- Standards for how we document errors, fixes, and patterns so we never pay twice for the same mistake.
- Onboarding‑ready documentation and examples that help new builders plug into the engine quickly without sacrificing quality.
Advanced Builder – Automation & Error‑Intelligence Infrastructure
Ahad is an advanced builder working on the reliability layer of the Bays Horizon engine — the part most people never see, but everyone depends on. His focus is on Latenode workflows, error handling, and centralized diagnostics so our automations fail loudly, visibly, and fixably instead of breaking in the dark.
What he’s building at BHA:
- JSON‑based error logging patterns for Latenode and external API workflows.
- A unified error surface in Slack (`#bha-pipeline-errors`) where failed jobs report themselves with context instead of silently disappearing.
- Foundations for future Genie‑driven error intelligence: structured logs that an agent can analyze, summarize, and help us auto‑remediate.
- Reusable patterns for safe, observable automations that will apply far beyond the Vertical Farm.
Advanced Builder – Ingestion Engine & UX Systems
Kaiqi is an advanced builder focused on turning messy, real‑world data flows into clean, modular ingestion engines with solid UX on top. He has been central to standing up the Stage 1 ingestion application for Bays Horizon — wiring CRUD APIs, Supabase/Postgres integration, tests, and interface patterns that other builders can reuse instead of reinventing from scratch.
What he’s building at BHA:
- A modular ingestion application with Stage 1 CRUD API, Supabase integration, and server‑side tests.
- Front‑end card management UX (filters, editing flows) that lets operators and builders control ingestion pipelines without touching code.
- A catalogue of patterns for dealing with environment edge cases (sandbox permissions, cron scheduling, IPv6 DNS issues, port collisions) so future builders don’t pay the same tuition.
- Reusable engine components that will underpin future digital twin and advisory ingestion stacks.
Automation & AI Systems Builder
Hardik is an Automation & AI Systems Builder helping translate Bays Horizon’s engine work into clear, reusable systems and public‑facing narratives. He lives at the interface between architecture and storytelling: validating live behavior, shaping digital twin messaging, and making sure our progress is legible to clients, partners, and future builders.
What he’s building at BHA:
- Live validation and auditing of vFarm APIs and telemetry to ensure the JSONB twin, tests, and OTEL instrumentation are actually behaving as designed.
- Digital twin‑driven LinkedIn content that explains deep backend changes (JSONB migration, tests, OTEL, thresholds) in plain language for growers, restaurant partners, and serious builders.
- Patterns for how Genie and our twins should talk about the engine — tying hard infrastructure work directly to human and commercial outcomes.
- A bridge between the engine room and the outside world so BHA’s best work doesn’t stay invisible.
Senior Architect – Data Architecture & Backend Spine