c68e1d2394
The /simplify triage produced two live debts, and both are about the same pair of functions the B34+ plan already names in F3, so they landed as F10 of that plan rather than as an escala-dry-pos-b37: the município-side batch actions write one município at a time (findByID + update each — ~870 round trips at the 435 ceiling B37 itself raised, but ~52 at the largest real TI, and no test above a batch of 2), and the two are twins at 2 call sites, one short of the bar. The common trigger is a "select all"/multi-TI affordance or a third batch on that side, and F10 records why the bulk-SQL rewrite is not obviously the answer: it would hand back the scope check that overrideAccess: false gives for free. This delivery also closed B34+ phases outright, which is worth reading in the plan rather than inferring from a diff. F2 is done and its prediction was wrong in a way worth keeping: it stated "o B37 não retira este débito", and B37 read the same evidence the other way — the ~165 measured lines were not deduplicated into useChipRowOverflow, they were deleted when both cells became wrappers of one engine. F9 is done via scopedPortfolioIndex. Half of F3 is done (the three single-id deltas), and the half that stayed out — the set-with-floor form — stayed out because seeing the collapsed code confirmed the plan's own inverted recommendation. F5 and two F6 bullets shrank for the same reason: "written twice across the two surfaces" stopped having two surfaces. Also corrects a comment I got wrong in the previous commit: the batch's sort does not carry the deadlock-avoidance guarantee, since acquireTextAdvisoryLocks sorts its own keys (C8 batched them into one round trip); it only makes the apply order stable. |
||
|---|---|---|
| .agents/skills | ||
| .cursor | ||
| .github/workflows | ||
| .husky | ||
| .impeccable | ||
| .vscode | ||
| .zed | ||
| docker/postgres/init | ||
| docs | ||
| public | ||
| scripts | ||
| src | ||
| tests | ||
| .env.example | ||
| .env.test | ||
| .gitignore | ||
| .npmrc | ||
| .prettierignore | ||
| .prettierrc.json | ||
| .yarnrc | ||
| AGENTS.md | ||
| components.json | ||
| DESIGN.md | ||
| docker-compose.yml | ||
| Dockerfile | ||
| eslint-legacy-ignores.mjs | ||
| eslint-local-rules.mjs | ||
| eslint.config.mjs | ||
| knip.json | ||
| next.config.mjs | ||
| package.json | ||
| playwright.config.ts | ||
| pnpm-lock.yaml | ||
| postcss.config.mjs | ||
| PRODUCT.md | ||
| README.md | ||
| skills-lock.json | ||
| tailwind.config.ts | ||
| test.env | ||
| tsconfig.json | ||
| vercel.json | ||
| vitest.config.mts | ||
| vitest.setup.ts | ||
| vitest.unit.config.mts | ||
Teqo
Teqo starts as the official digital platform for deputado Jorge Solla and evolves into a white-label civic engagement platform for politicians in Brazil.
The goal is to help political teams build direct, durable relationships with their base without depending on Big Tech social platforms as the primary channel.
Mission
- Strengthen direct communication between representatives and citizens.
- Reduce platform dependency risk by owning audience and data channels.
- Provide reusable building blocks so each political team can launch quickly.
Product Direction
Phase 1: Jorge Solla Website
Initial delivery focuses on Jorge Solla's public website, editorial CMS, and the internal /campanha tool:
- Public-facing content and updates (news/
post+taglive) - Institutional pages and biography (still pending a
Pagescollection) - Internal campaign operations: electoral nuclei, leaderships, estimates, updates, WhatsApp invites
- Editorial operations through Payload CMS
Phase 2: White-Label Platform
Teqo then becomes a configurable base product for other politicians in Brazil:
- Multi-tenant and reusable architecture
- Brand and content customization per mandate/campaign
- Shared core modules for communication and engagement
- Operational autonomy with self-hosted owned channels
Local Development
Production safety: the production database is a live Neon Postgres holding real citizens' data. Local development and tests run against a local Postgres and must never point at production.
pnpm devrefuses to start against a non-local database, and the test suite refuses any database whose name doesn't end in_test.
First-time setup
- Install dependencies:
pnpm install - Create your env file:
cp .env.example .env.local - Start Docker, then start the local database:
pnpm db:start- This runs Postgres 17 (matching production) and auto-creates a
teqo_testdatabase for the test suite.
- This runs Postgres 17 (matching production) and auto-creates a
- Make sure
DATABASE_URLin.env.localpoints at local:DATABASE_URL=postgresql://teqo:teqo@localhost:5432/teqo - Load a schema + content into the local database — pick one:
- Mirror production content (recommended):
PROD_DATABASE_URL="<unpooled Neon URL>" pnpm db:pullCopies production's schema and content into local. It only reads production and excludes supporter PII (contact/signature/subscriptiondata). - Empty schema from migrations:
pnpm migrate
- Mirror production content (recommended):
- Start the dev server:
pnpm dev - Open:
http://localhost:3000
Useful scripts: pnpm db:start / pnpm db:stop (local Postgres), pnpm db:pull (refresh local content from prod), pnpm db:seed:posts (import news posts/tags fresh from the live jorgesolla.com.br site into the local db; idempotent by slug, refuses a non-local database), pnpm db:seed:tse (import TSE 2014/2018/2022 Bahia election results into the local db; idempotent per year/office/turn scope, refuses a non-local database), pnpm build:election-aggregates (regenerate the committed TSE aggregate artifact in src/lib/electionAggregates/ from locally seeded data).
Content & cache revalidation
Public news pages (/[type], /[type]/[category], articles, and the home news list) are cached under a shared posts tag. Editing a post or tag in the deployed admin self-revalidates via afterChange hooks. Any write that bypasses the deployed runtime — a direct-DB seed (pnpm db:seed:posts), SQL, Onda 0 migrations, or a restore — does not bust production's cache, so afterwards call the secured endpoint:
# News (default tag: posts)
curl -X POST "https://<prod-domain>/api/revalidate" -H "x-revalidate-secret: $REVALIDATE_SECRET"
# Privacy policy after Onda 0 provision (tag: global_privacy-policy)
curl -X POST "https://<prod-domain>/api/revalidate?tag=global_privacy-policy" -H "x-revalidate-secret: $REVALIDATE_SECRET"
REVALIDATE_SECRET must be set in the Vercel production env (see .env.example). See the "Posts & Tags" section of AGENTS.md for the full model.
Database migrations
Schema is managed by committed Payload migrations (src/migrations/); push is disabled everywhere.
To change the schema:
- Edit the collection/global/field config.
- Generate a migration:
pnpm migrate:create <name> - Review and commit the generated files in
src/migrations/(both.tsand.json, plusindex.ts). - Apply it locally:
pnpm migrate(check status anytime withpnpm migrate:status).
Deploying to production: pnpm build runs payload migrate before building, so every Vercel deploy automatically applies pending migrations to the production database. Do not run migrations against production by hand.
Running tests
Tests use the isolated teqo_test database (config in .env.test). Prepare its schema once with:
DATABASE_URL=postgresql://teqo:teqo@localhost:5432/teqo_test pnpm migrate
Then run:
pnpm test— unit + integrationpnpm test:e2e— Playwright (requires the test DB schema and a free port)pnpm test:all— unit + integration + E2E
Quality gates (also enforced by CI on the GitHub mirror): pnpm lint (zero warnings — --max-warnings=0), pnpm typecheck, and pnpm exec knip (dead files/dependencies fail; delete what your change orphaned). Standards: .cursor/rules/engineering-standards.mdc.
Tech Stack
- Payload CMS
- Next.js
- PostgreSQL (via
@payloadcms/db-postgres) - TypeScript
Campaign (/campanha)
Internal campaign tool for electoral nuclei, local leaderships, vote estimates, field updates, and WhatsApp invites. Authenticated separately from /admin via the campaignUser collection (geral / coordenador / lideranca). Operational status and decisions: .cursor/rules/projects/nucleos-eleitorais.mdc. Conventions and deploy checklist: AGENTS.md (“Campaign auth” / “Campaign nuclei MVP”).
Production blocker: do not load real leadership data or enable invites until counsel-approved Consent.key = 'lideranca-autopreenchimento' exists. Absolute invite URLs require NEXT_PUBLIC_SITE_URL as an exact HTTPS DNS origin in production.
Roadmap
Backlog and future plans live in docs/roadmap.md (blockers, public site, /campanha next cycles, admin RBAC, white-label).