Skip to content

Process · ADR 006 · ADR 008

See how farpa discovers, decides, and delivers.

Six short phases, eight questions before any work begins, and nine active ADRs that record every structural decision — date, vote, paper trail.

Pipeline · 6 phases · ADR 006

How we work

DSBVLR is shorthand for discover, shape, build, verify, launch, reflect. We do not let it become ceremony.

  1. Discover

    customer weekly · live OST

  2. Shape

    boundaries · appetite · rabbit holes

  3. Build

    2-4 wk · trio · agents

  4. Verify

    LLM-as-judge · WCAG · DORA

  5. Launch

    CMO · COO · CFO · CLO

  6. Reflect

    retro · lessons · OST updated

Detail per phase

Discover (D) · A customer conversation every week (Teresa Torres) and a live Opportunity Solution Tree. Discovery is not a phase — it is a habit.

Shape (S) · One week to define boundaries, appetite, and the rabbit holes worth avoiding (Shape Up · Basecamp).

Build (B) · Two to four weeks in short waves, with an executing trio and coordinated multiple agents.

Verify (V) · LLM-as-judge against a YAML rubric, WCAG AAA contrast (ADR 004), and DORA metrics. Verify is continuous — not a final inspection.

Launch (L) · One week with CMO, COO, CFO, and CLO aligned. Ritualized deploy via farpa-push — no Friday-deploy heroics.

Reflect (R) · CHRO retro, lessons written in the moment (event-driven), and the Opportunity Solution Tree updated for the next wave.

Operationalization · ADR 008

Living Lab (F0 to F8)

For a new product or a new wave, DSBVLR runs inside a nine-phase lab (F0 to F8) with a YAML rubric for each phase. It is not an extra step — it is how the pipeline meets the ground.

Operational detail lives in farpa/01-laboratorio-vivo/. This showcase does not replicate it — knowing it exists is enough.

Before any work begins

The 8 gating questions

Every request answers these eight questions before becoming any action. They stop the kind of urgency that turns into rework.

  1. 01

    Visibility

    Who needs to see the output: detailed, executive, or by directorate?

  2. 02

    Type

    One-off execution or the full DSBVLR cycle?

  3. 03

    Depth

    Quick, consultive, or full 3-of-3 Council?

  4. 04

    LLM cost

    Zero (Cloudflare), low (Gemini), or high (Anthropic)?

  5. 05

    Time-box

    Hours, days, weeks, or open-ended?

  6. 06

    Reversibility

    Can we undo it, or is this a one-way door?

  7. 07

    Compliance

    None, personal/financial/IP data, or heavily regulated (LGPD · ANS · CVM)?

  8. 08

    Re-use

    Draw on existing memory, or start from scratch?

Structural decisions · public

10 active ADRs

Every structural decision has a public ADR — date, vote, paper trail. Ten so far. Nothing invented, nothing hidden.

  • ADR 001 · Founders Council (2-of-3 quorum).
  • ADR 002 · Cloudflare Workers-first as default infrastructure.
  • ADR 003 · Bilingual PT-BR + EN native (path prefix /pt/ + /en/).
  • ADR 004 · High contrast required (WCAG AAA · physical requirement).
  • ADR 005 · Single Design System at /produtos/_shared/ds/.
  • ADR 006 · DSBVLR pipeline as canonical method.
  • ADR 007 · Directorate-Area separation (strategy separate from execution).
  • ADR 008 · Living Lab (9 phases F0-F8) operationalizes DSBVLR.
  • ADR 009 · Hybrid Taxonomy (4 levels: Council · Directorate · Area · Cross-cutting).
  • ADR 010 · PT slug convention — natural noun, no forced morphological parity with EN.

Next steps

Read ADR 001 (2-of-3 Council) See who makes these decisions Join the Day 2 list