Independent researcher and open-source systems designer building calm, privacy-first infrastructure.
I work on local-first software, proof systems, behavioral infrastructure, and public-interest tools that help people keep agency over records, routines, decisions, and evidence. The common thread is restraint: software should be legible, durable, exportable, and useful without turning attention or trust into a growth surface.
- Proof-of-existence and receipt infrastructure for timestamping local file hashes with minimal disclosure.
- Behavioral finance systems for capital separation, timed locks, and calmer decision boundaries.
- Local-first personal tools for documents, budgeting, care routines, language practice, and game preservation.
- Repository standards, release discipline, and research publication workflows for a coherent open-source ecosystem.
| Project | Area | Status | Role |
|---|---|---|---|
| Elora Vault | Behavioral finance | Active prototype | Self-custodied vault mechanics, protected capital states, and Base-native financial infrastructure. |
| OpenProof | Proof systems | Active prototype | Local file hashing, onchain proof registration, receipts, and verification workflows. |
| ecosystem-standards | Governance | Canonical | Repository, documentation, security, publication, and agent-operation standards. |
| PDFReader by Sparsh | Local documents | Maintained | Desktop PDF reading, search, annotation, diff, merge, split, and release engineering. |
| Chess by Sparsh | Local games | Maintained | Browser chess with accurate rule validation, portable game records, and local-first play. |
| Hiss-Tastic | Preservation | Maintained prototype | Snake-inspired Python/Pygame prototype with deterministic replay and browser modernization work. |
| Area | Repository | Purpose |
|---|---|---|
| Builder operations | builder-journal | Public command center for project direction, decisions, maintenance, and repo health. |
| Plant care | OpenSprout | Privacy-first plant care records for schedules, logs, and long-running stewardship routines. |
| Personal finance | QuietLedger | Local-first budgeting and financial records with exportable personal data. |
| Language practice | WordWise | Reflective word-of-the-day practice with definitions and optional media backgrounds. |
| Civic integrity | SheSafe | Early-stage safety mapping concept for careful public-interest records. |
- Prefer clear records over opaque automation.
- Prefer exportability over lock-in.
- Prefer calm defaults over engagement loops.
- Prefer verifiable claims over persuasive language.
- Prefer long-term stewardship over novelty.
| Layer | Tools |
|---|---|
| Frontend | TypeScript, React, Next.js, Vite, Tailwind CSS |
| Local-first apps | Python, PySide6, PyMuPDF, SQLite, browser storage |
| Web3 / proof | Solidity, Base, Base Sepolia, viem, wagmi, RainbowKit |
| Data and backend | Supabase, PostgreSQL, serverless APIs where needed |
| Delivery | GitHub Actions, Vercel, PyInstaller, release checklists |
| Governance | README standards, security policies, contribution guides, changelogs, release notes |
My work sits between applied software engineering, protocol design, local-first computing, and behavioral infrastructure. I am especially interested in systems that are inspectable, self-custodial, emotionally quiet, and maintainable by small teams or individual users over long periods.
Current research themes:
- Calm software and non-extractive interfaces.
- Ownership without surveillance.
- Proof, receipts, and public verification with minimal disclosure.
- Local-first personal records and exportable data.
- AI-assisted software preservation and responsible agent workflows.
- Ecosystem narrative
- Research outputs
- Philosophy of calm infrastructure
- Publication roadmap
- Repository taxonomy
- ORCID and DOI strategy
- ORCID: 0009-0007-1585-6927
Not every system in the ecosystem is public. Some work remains private when it involves proprietary workflows, sensitive operational logic, or business-specific infrastructure. Public references describe purpose and boundaries only; implementation details stay private.
This profile is an independent research and open-source systems record, not startup positioning. The goal is to make small, durable systems that can be inspected, cited, forked, self-hosted, and maintained over time.