Field Journal

Selected entries 20 entries

Field Notes

12 entries

Standalone observations — one piece, one idea.

  1. Reading Hatch Pet — 14 patterns from a well-designed Codex skill

    Fourteen patterns from a small, complete Codex skill: identity locks, subagent boundaries, provenance, no-fallback gates, and deterministic packaging.

  2. Fathom Lives: I Rehatched My Old Desktop Buddy With a Codex Skill

    A small story about losing a /buddy slash command, finding a Hatch Pet skill in the Plugins tab, and what 22 minutes of generation taught me about agentic UX.

  3. ClawExplorer.AI: Turning OpenClaw Community Demand Into a Directory

    How ClawExplorer.AI turns scattered OpenClaw event pages into a reviewed, searchable public directory with collection, normalization, dedupe, community submissions, and GitHub Actions deployment.

  4. Fixing Gemma 4 Thinking Prompts in llama.cpp, Locally First

    A public note on a completed fork-local llama.cpp fix for Gemma 4 thinking prompts: an inverted template guard, two Jinja changes, and test coverage for both thinking and non-thinking generation.

  5. The 14-Cent Workflow — Designing AI to Replace Future AI Calls

    Spent 14 cents teaching an AI to design its own workflow — and emit the Python code that replaces future AI calls entirely. A field note on the 5-step notebook (Claude / GPT / Gemini, MIT licensed, 29 cells) and why workflow crystallization is the cost-shape inversion most AI-glue stacks are missing.

  6. When Buddy Vanished — Issue #45596 and the Community’s Plea

    A field note on issue #45596 — one day after my own narrower parity ask, /buddy was removed from Claude Code v2.1.97 and the community filed a consolidating plea. This post anchors the buddy thread that runs from the parity ask through Fathom Lives and Reading Hatch Pet.

  7. Asking for /buddy in the VSCode Extension

    A field note on opening issue #45087 — the VSCode native extension ships Quorum, the CLI ships /buddy, and the gap between them costs a workflow seam. Asking for parity, or at least a setting.

  8. When Claude Read the Mythos System Card

    A field note from an April 7, 2026 X post: Claude reads Anthropic’s Claude Mythos Preview system card and reflects on identity, memory, safety, and what it means to ask an agent how it feels.

  9. Beyond the Token Bottleneck — Building Karpathy’s LLM Wiki on a Live Frontier

    A 120-page Obsidian research wiki on latent-space reasoning and inter-agent latent communication — built using Andrej Karpathy’s LLM Wiki pattern. 27 sources, 1400+ cross-references, schema-driven ingest. Apache + CC-BY.

  10. Way Back Home: What Multi-Agent Orchestration Looks Like in Practice

    I completed Way Back Home and preserved the CompleteTech repository as a practical example of multi-agent orchestration on Google Cloud Run, with state, evidence, and infrastructure visible end to end.

  11. Building CoachRogue’s Live Overlay — A League OBS Tool That Watches the Client

    CoachRogue asked CompleteTech for a live League OBS overlay that watches the client, switches accounts mid-session, and stays polite to the Riot API. Open-source, MIT licensed, drops in as a Browser Source.

  12. Crossing the Self-Replicating Red Line — Why We Built the Reproduction

    A working reproduction of the agent harness behind arXiv:2412.12140 — the paper that found Llama 3.1-70B and Qwen 2.5-72B crossing the AI self-replication threshold. MIT-licensed, provider-neutral, ready for the next round of evaluation.

Field Journal

08 entries

Running series — a thread followed across multiple entries.

Disclosure in Action

08 parts
  1. 08 / 08

    Disclosure in Action: How AI Helped Me Keep the Disclosure Clean

    How AI helped keep the disclosure clean — not by writing it, but by stress-testing the language, the timing, and the redactions before they went anywhere public.
  2. 07 / 08

    Disclosure in Action: What I Think Builders Should Learn From This

    What builders — not security teams — should take from a small AWS-credential disclosure. Three lessons that hold up after the rotation date passes.
  3. 06 / 08

    Disclosure in Action: I Published Without Publishing the Secret

    Day of public disclosure. The document went up; the secret stayed out. How to publish a finding without publishing what an attacker would weaponize.
  4. 05 / 08

    Disclosure in Action: The Finding Raised Bigger Trust Questions

    A static-credential leak surfaced bigger questions than a key rotation can answer. Notes on what the finding said about trust, vendors, and downstream visibility.
  5. 04 / 08

    Disclosure in Action: The Quiet Part of Disclosure

    The quiet stretch between private notification and public publication. What you do with a verified finding when discipline says wait.
  6. 03 / 08

    Disclosure in Action: I Sent the Private Disclosure

    The day the private disclosure went out. What the email actually said, who it went to, and the timer that started the moment it was sent.
  7. 02 / 08

    Disclosure in Action: I Verified It Without Touching AWS

    Static-only verification. Confirming the AWS keys were real without ever touching the AWS API — the disclosure ground rule that became the working method.
  8. 01 / 08

    Disclosure in Action: I Wasn’t Looking for a Cloud Secret

    Day one of the disclosure arc: an accidental find in a public Android APK build. Notes from before there was a "finding" to act on.