Skip to content
View gmdr2022's full-sized avatar
💭
Building reliable local-first systems
💭
Building reliable local-first systems

Block or report gmdr2022

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
gmdr2022/README.md

Guilherme M. Rocha

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.

Selected work

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

Engineering principles

  • 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.

Current focus and contact

I am refining local-first product delivery on Windows and publishing small tools whose guarantees can be inspected, tested, and reused independently.

Popular repositories Loading

  1. learning-archive learning-archive Public archive

    Frozen archive of early GitHub profile experiments and study notes.

  2. gmdr2022 gmdr2022 Public

    GitHub profile for Guilherme M. Rocha — local-first software and developer tooling.

  3. local-first-checklist local-first-checklist Public

    Offline-first Python CLI with atomic local persistence, validation, and explicit recovery.

    Python

  4. release-evidence release-evidence Public

    Generate and verify deterministic SHA-256 manifests for release directories.

    Python