Gydos.org small tools · deep practice · local-first software
Public workbench

Plain text, local tools, versioned learning, and creative systems that can be understood.

Gydos.org is a growing public workspace for Android-on-Android development, text-first computing, small reproducible environments, local-first document tools, Codex workflows, and scriptable sound-and-reading systems for study, focus, prayer, recovery, and creative work.

View GitHub profile View this site repository

Current public projects

Some work is already public. Some work is still being cleaned up before it deserves a full release. The common thread is reducing friction between thought, text, command, memory, and publication — while keeping the tools small enough to understand, repair, and teach.

Android-on-Android Development Toolchain

A reproducible Termux-based Android app development workflow that builds real APKs directly on an Android phone, using OpenJDK, Gradle, Android SDK command-line tools, Kotlin/Java, and aapt2.

Demonstrated targets include Falling Blocks, Pong Invaders, KJVOnTap experiments, and the planned Android port of Meditation Soundbox.

  • Current status: successfully building toward local APK generation from Android itself.
  • Best use cases: education, prototyping, phone-native development, and reproducible public documentation.
  • Production note: Google Play production readiness requires API 35+ targeting.
  • Known blocker: the available Termux aapt2 package links API 34 but appears to fail against Android 35/36 platform jars, so Play-compliant builds require further aapt2 / toolchain work.
Termux Android SDK Gradle OpenJDK Kotlin / Java aapt2 APK builds
Document the toolchain →

Smellinux + vishgit

The cornerstone environment concept: a small Linux learning and working system built around a plain, memorable discipline — edit with vim, execute with sh, and remember with git. The public repository is not rushed yet; the project is being shaped carefully so the first committed version can be readable, reproducible, and worth teaching from.

pre-public cornerstone vim POSIX sh git Alpine Linux CSV literacy
See where it fits →

InfoCodex

A lean local knowledge pack for becoming sharper with Codex, especially on storage-constrained Android / Termux setups. It collects power-user paths, prompting patterns, config and permissions notes, AGENTS.md / skills guidance, lean-stack habits, tooling pairings, and reusable playbooks.

Codex Termux AGENTS.md workflows templates
Open repository →

Verse of the Day

A platform-neutral Rust command-line application that selects one KJV passage for the current local calendar day. The order is deterministic by year, while a separate POSIX /bin/sh implementation keeps the idea close to the vishgit path.

Rust POSIX sh KJV Meta-V daily CLI
Open repository →

Meditation Soundbox

A Windows-first, local-first console instrument for generated meditative/electronic soundscapes, live frequency changes, rhythm and synthesis variation, Piper text-to-speech, pasted readings, and KJV / Meta-V scripture loading. The Android 16 port is a serious future target for the Android-on-Android toolchain.

C# audio Piper TTS KJV / Meta-V scriptable sessions
Open repository →

Siftlog Cathedral

A local-first C# application for gathering scattered writing and documents into a uniform, reverse-chronological HTML reading surface. This repository is public, but still being cleaned up: the next pass is about a proper .gitignore, clearer boundaries, and a more deliberate push history.

C# .NET local web Markdown personal knowledge
Open repository →

whatif

A seed-stage project for a free-of-cost, manifest-driven creative toolchain: music, spoken word, Scripture-aware text workflows, attribution tracking, and local-first experiments. There is not a build to present yet; the purpose is to give the idea a public name and a careful place to grow.

seed-stage manifest creative tooling music local-first
Open repository →

The practice

This work is not only about apps. It is about building an understandable way to work: readable text, repeatable commands, visible history, and tools that can be explained line by line.

Edit Use plain text as the common surface for notes, code, data, documentation, and reflection.
Execute Prefer small shell scripts and transparent command-line flows over hidden machinery.
Remember Let git preserve the work as history: drafts, changes, experiments, and decisions.
Publish Use public repositories and simple pages to turn learning into shared artifacts.

Near-term direction

The immediate goal is to make the public work easier to enter without pretending every project is finished. The Android-on-Android toolchain deserves a reproducible guide and repository, with KJVOnTap, Falling Blocks, Pong Invaders, and the Meditation Soundbox Android 16 port documented as concrete proof of the workflow. Smellinux should become a first-class public project when it is ready; Siftlog Cathedral needs cleanup; InfoCodex and Verse of the Day need useful examples; whatif needs a careful first build.

$ next

  1. Keep github.gydos.org readable, current, and honest about project status.
  2. Document the Android-on-Android development toolchain as a reproducible public project.
  3. Add review pages for KJVOnTap, Falling Blocks, Pong Invaders, and the Meditation Soundbox Android 16 port.
  4. Prepare Smellinux / vishgit as a first-class repository with scripts, lessons, and logs.
  5. Clean up Siftlog Cathedral: .gitignore, generated files, README, and push history.
  6. Expand InfoCodex with concise field-tested Codex workflows for Windows and Termux.
  7. Make Verse of the Day easy to install, run, and compare across Rust and POSIX sh.
  8. Let whatif remain seed-stage until it has a minimal, attribution-aware first build.
  9. Grow Meditation Soundbox toward mixer buses, logs, scripts, voice selection, and smoother sessions.
  10. Keep everything small enough to read, run, explain, and version.

Leadership

My Chief Technology Officer for my startup gydos-dot-org and myself.

A playful photo of the site owner beside a gold humanoid robot figure.
A playful nod to the abstraction layer of aggregate AIs, software, tools, and search technologies that help make the work referenced on this page possible.

Contact and links

The best public entry point is the GitHub profile and the project repositories. For project-related contact, use the public Gydos.org email listed with the repositories.

github.com/gydos-dot-org paul@gydos.org