FOAAP reached ~1,700 users in its first five days.

Artificial intelligence

made remember.

AI systems architect and product engineer building stateful applications, agent workflows, structured memory, and production MVPs.

Explore the system

THE POSITION

I do not just add AI to interfaces. I design the state, tools, memory, and decisions that make the product work.

INPUTSTATEDECISIONMEMORYNEXT ACTION

SELECTED SYSTEM / FOAAP

A venture operating system that actually remembers.

Founder context gets scattered across chats, documents, and tools. FOAAP turns it into durable venture state, resolves contradictions, and exposes one high-leverage action.

INTERFACE CONCEPTS / SIX DEMO WEBSITES
Hover over a window to bring it forward. On touch, press and hold.
NNorth — Independent design studio
lLedger — Business overview
oOrbit — Product workspace
fForma — Find your practice
IIndex — Notes on modern life
rRelay — Infrastructure for builders

THE OPERATING MODEL

One continuous path from ambiguity to action.

The information often already exists. I connect it across sources and frameworks so a person can understand their position, see their options and act in time.

01

understand

Understand the person’s position inside a system: what affects them, what they can see, and where their agency is constrained.

02

structure

Build an ontology connecting people, institutions, records, obligations and deadlines. Turn isolated facts into relationships a person can reason over.

03

investigate

Cross sources and unfamiliar frameworks. Find contradictions, outdated records and information that has become relevant to a decision or deadline.

04

decide

Make an explicit assertion about the situation, grounded in evidence. Surface assumptions, weigh alternatives and keep the position open to revision.

05

produce

Assemble that reasoning into something usable: an evidence map, a decision brief or working software. Give the person a basis for action.

06

remember

Keep the sources and reasoning behind each position. Let new information update the model so insight accumulates across decisions.

07

next action

Identify the next concrete move, what it depends on and when it must happen. Make the path from understanding to agency explicit.

THE THESIS

Amplifying your cognitive repertoire through research and synthesis.

I build systems that help people investigate unfamiliar problems, connect evidence across domains, and turn that synthesis into decisions they can revisit.

Explore my GitHub ↗

Selected repositories

03 REPOSITORIES / SOURCE & DECISIONS
lib/validate_candidate.mjs
    const n = countOccurrences(rawText, q);    if (n === 0) {      errors.push(`quote_not_found: evidence_quotes[${i}] ${JSON.stringify(q.slice(0, 60))}`);    } else if (n > 1) {      errors.push(`ambiguous_quote: evidence_quotes[${i}] occurs ${n}+ times ${JSON.stringify(q.slice(0, 60))}`);    } else {      const start = rawText.indexOf(q);      spans.push({ start, end: start + q.length, text: q });    }

Trace every claim to its source.

I keep model extractions as candidates. In anchorQuotes, a quote must occur exactly once in the original text before the validator accepts its source span. Missing or ambiguous evidence produces an explicit error.

The model supplies the quote. Deterministic code derives its position.

An exact match establishes provenance; it does not establish that the claim is true.

02 / Bicis SapiensPostgreSQL / RLS
supabase/migrations/0001_init.sql
alter table notification_settings enable row level security;···-- notification settings: only selfdrop policy if exists "settings_self" on notification_settings;create policy "settings_self" on notification_settings  for all using (auth.uid() = user_id) with check (auth.uid() = user_id);

Put ownership in the database.

For requests subject to RLS, notification settings belong to the signed-in user. USING checks which existing rows they can access; WITH CHECK constrains the values they can write. The migration enables RLS before defining the policy.

Authorization is enforced by Postgres, beyond what the interface chooses to show.

Service-role access bypasses RLS and must stay on the server. This excerpt documents the migration, not a live database audit.

03 / FOAAP EnginePostgreSQL / PL/pgSQL
supabase/engine-schema.sql
  select v.version into cur_version from public.venture_models v    where v.user_id = p_user and v.venture_id = p_venture for update;···  if p_base = -1 or cur_version = p_base then    update public.venture_models set model = p_model, version = cur_version + 1      where user_id = p_user and venture_id = p_venture;    return query select 'ok'::text, cur_version + 1, p_model, now(); return;  end if;  return query select 'conflict'::text, v.version, v.model, v.updated_at    from public.venture_models v    where v.user_id = p_user and v.venture_id = p_venture;end $$;revoke all on function public.save_venture_model(uuid, text, jsonb, int) from public, anon, authenticated;

Make stale writes explicit.

A row lock serializes updates to an existing model. The caller supplies a base version; a stale save returns a conflict and the current server state so the application can reconcile it.

Concurrency is part of the persistence contract.

The force-save path (p_base = -1) is explicit. Public, anonymous and authenticated roles are denied direct execution of this RPC.

Exact excerpts from the linked revisions. Gaps indicate omitted lines. Private repositories require access; the selected code is readable here.

OWNED END TO END

01

Product

Problem framing, ontology, interaction model, and the operating loop.

02

Engineering

React, Vite, Supabase, Postgres, OpenAI, Anthropic, and deployment.

03

Judgment

State invariants, failure analysis, observability, retries, and the next hardening move.

Paulo Villalobos speaking

THE BUILDER

I seek difficult systems, not safe tasks.

I deliberately compound intellectual, technical, physical, social, and economic capacity. The point is greater agency: the ability to understand difficult systems, act under uncertainty, and build useful things.

I am especially drawn to problems where software meets real operations, institutions, and consequential users.

PORTO / REMOTE

Give me the hard part.

paulo@foaap.app