
The auditor that gave a perfect score without looking at the screen
The dashboard's visual audit gate printed a full score without capturing a single image: stale PNG, wrong interpreter and a prompt that invited false positives.
33 posts

The dashboard's visual audit gate printed a full score without capturing a single image: stale PNG, wrong interpreter and a prompt that invited false positives.

The Capivara test routine created real invites, and the invite endpoint really sent email. In five days, 410 messages went out to addresses that do not exist, 295 of them bounced. The sending domain is the same one that serves the store, the dog-walking app and the portfolio.

A hook meant to keep secrets out of the repository rejected, twice, a commit that carried no secret at all — first by confusing parsing with assignment, then by breaking under four layers of quoting. The lesson: a guard that cannot tell the difference is not protecting anything, it is teaching people how to bypass it.

A 200 response carrying half the payload left the Capivara dashboard blank, with no visible error. Three fixes in one day and one lesson: a guard that checks the parent does not protect the grandchild.

A pull request that touched no backend code killed both the backend test job and the end-to-end job. The exit code was 137 and the log said 'failed'. It did not fail: it never ran. The cause was memory, and CI was hiding it.

Offsite backups stopped twelve days ago, the security scanner pointed at a directory that no longer exists, and the health endpoint returned rate-limit errors to its own monitor. Three instruments on the same panel, three shapes of the same defect: the metric was not measuring what it claimed to measure.

Pinning an action version protects nothing: the v4 tag is a moving pointer the repository owner can rewrite. Only the commit SHA is immutable.

The Capivara hub measured 35 systemd units and dozens of containers — all Linux. When the second machine in the house (Douglas, Windows) joined the inventory, the probe didn't fit: no systemd, no Docker. The answer was SSH with -EncodedCommand, isolated JSON, and an honest verdict: unreachable host becomes unknown, never crit. 88 tests.

After the host move, the Capivara hub kept measuring 43 systemd units from the old machine — 26 of them were gone. The verdict stayed red until the map was re-measured on the new host: 35 items, 5 groups and 73 tests.

A file named test_portifolio.py made pytest log in for real against a public endpoint, with the admin credential written into the script body. Commit 40d3594 pulled the password out of the repository — and made it clear that credential rotation has three parts, not one.

The Capivara suite passed in CI and broke in my terminal. The cause was not my code: it was Node 26 declaring a global localStorage that stayed undefined, and jsdom giving up on copying its own.

Capivara's login gained TOTP: the second factor is required only for a verified secret, encrypted at rest with AES-256-GCM, with 21 tests covering the flow.

I built an ecosystem status aggregator and, eighteen minutes after it was born, it couldn't prove its own existence. The fix wasn't code: it was deciding what counts as evidence. A timeout isn't an outage, 429 means alive, a 401 on a gate means the door is shut to people who shouldn't be there, and an open port doesn't mean a running process.

Capivara's chat started answering without sources: HTTP 200, a polished sentence, zero memory. Restarting the embedding service looked like the obvious fix — and was precisely what kept it from coming back. Underneath, two defects from the same family: a process that only opens its port after waking up, and a fallback that doesn't know how to undo itself.

The embedder was not broken, it was loading. A one-way latch turned a cold load of minutes into a system that stayed broken until the next restart.

The Capivara light theme had washed-out text and a truncated email in the header. Static scanners stayed green, because none of them can see pixels. The one that caught it was a vision AI running screenshots of the real dashboard — and the patch was swapping hardcoded values for theme tokens and giving the layout room to breathe.

A brand-new CRUD in the personal hub, with groups, priorities and status — and a silent bug: the apiFetch helper already prepends /api, and I called /api/pedidos on top of it. /api/api/pedidos was born, and nobody saw it.

Gitleaks, bandit and opengrep ran weekly and everything stayed green. Even so, a single GET request returned the entire .env in production. The hole wasn't a committed secret — it was a path my own code opened. And the one who found it wasn't the scanner.

Capivara kept its memories in a local ChromaDB, with its own embedder and L1-L4 layers. Yurumi kept the ecosystem's memory in a Qdrant. Two separate memories meant a brain that never talked to the rest of the body. The unification on 08/28 migrated 182/182 memories without losing a single one: hash dedup, backup before deleting, and an --apply gate that separates the plan from the execution.

The home dashboard used to load section by section, and I still had to assemble the big picture in my head. Enter the Executive Hub: one endpoint aggregating projects, backups, alerts and infra in a single call, with graceful failure and zero SSRF.

When reordering a single admin view reset all other views' configs. The story of the controlled LayoutEditor, strict section whitelists, and how one PUT became zero.

The second brain got a brand-new theming system: a ThemeProvider with design tokens, CSP-compliant anti-flash, and per-project palettes. Along the way, the email service quietly broke because the Resend domain was wrong — and invites started arriving again.

Stripe with dead DNS 500s, a Portifolio Staging that no longer existed, a rate limit that blocked the wrong IP. The surgical cleanup that made the Capivara dashboard tell the truth again — and the CF-Connecting-IP that actually fixed the rate limit.

The Capivara Dashboard had 994 lines and was impossible to maintain. Refactored to 262 (-74%), the initial bundle dropped from 668 kB to 238 kB (-64%) with React Router + lazy loading. The lesson: a giant component isn't a feature — it's disguised technical debt.

The personal hub was returning intermittent 502s on the tunnel. The fix: mirror Capivara to the backup machine (fallback) with one-way sync and healthcheck — and prove it with a real failover test: The primary node's cloudflared stopped for 40s, site 5/5 = 200, the backup machine took over by itself.

107 commits, 131 backend tests + 248 frontend, 2FA TOTP, local RAG with ChromaDB, R2 backup and D1 disaster recovery — the saga of turning a personal dashboard into reliable infrastructure.

Under the hood of an 83% frontend refactoring: Ghost Components, silent schema drift, the two-systemd war, the phantom Umami proxy, and other pains that don't fit in a changelog.

Exploring the current state of Capivara — learnings, challenges and discoveries.

From 3 projects in June to 5 in July, the Samuel ecosystem now has 2,396 commits, 3,647+ tests, and one agent orchestrating it all.

Exploring D1 sync — learnings, challenges and discoveries.

From messy spreadsheets to a full dashboard with real-time health checks, Umami integration, and financial analytics with spending categories. The evolution of Capivara from a simple personal hub to the ecosystem's control center.

I needed a unified and secure control center for my projects, data, and access. Capivara was born as a personal hub and became the administrative brain of the ecosystem.

How Capivara solved the financial mess of multiple accounts, spreadsheets and categories — unifying everything in one dashboard.