I build local-first Windows software and developer tools for environments where reliability matters more than permanent connectivity.
Based in Brazil, I work across product delivery, offline-capable desktop systems, and focused engineering tools. I prefer explicit contracts and verifiable behavior over broad claims: what works offline, what fails safely, what automation has proved, and what still needs human validation should all be visible.
| Project | Purpose | Public evidence |
|---|---|---|
| ClubAL | Offline-first Windows software for institutional displays and operational routines. The implementation remains private during active development. | Product site · Delivery and reliability project |
| Release Evidence | Dependency-free CLI for deterministic SHA-256 release manifests, strict verification, and portable path handling. | Source · v1.0.0 · Attested release workflow |
| Local-first Checklist | Offline checklist CLI with atomic persistence, schema validation, last-known-good backup, and explicit recovery. | Source · v1.0.0 · Data contract |
- Local operation is the baseline. Network services may extend a workflow, but should not become an accidental startup dependency.
- Failure must be legible. Validation, recovery, and fallback behavior are explicit rather than silently masking damaged state.
- Evidence travels with a release. Tests, cross-platform CI, deterministic manifests, and provenance are connected to the artifact they support.
- Public and private boundaries are intentional. Product outcomes can be explained without publishing source code, operational data, credentials, or undisclosed plans.
- Human gates remain human. Automated checks are reported separately from visual, physical-device, or operational acceptance.
I am refining local-first product delivery on Windows and publishing small tools whose guarantees can be inspected, tested, and reused independently.
- Product context: ClubAL product site
- Delivery evidence: ClubAL reliability project · Open engineering project
- Open-source questions: use the relevant repository's issue tracker.
- Security reports: follow the private reporting path documented in each repository's
SECURITY.md.

