Skip to content

Now

What I'm currently focused on.

Notebook-First Restore & Truth Pass

“After six months of drift between what the site said and what was actually true, what does it take to make every live page honest again?”

infrastructure firstpublic learning philosophycompetitive advantage through infrastructure

Building & Testing

  • -Truth pass across every live surface: About, threads, the retired-methodology artifacts (Loop 1)
  • -Discovery restored: Artifacts, Trails, and Glossary back in the site nav, all nine trails reachable again
  • -Loop-based execution: each unit of work carries a goal, a deterministic gate, an iteration budget, and a receipt

Recent Progress

  • +Identity decision (2026-08-26): the notebook is back at the root URL; small-business services moved to /small-business
  • +Sitemap rebuilt from build output instead of hardcoded IDs - every submitted URL resolves again
  • +Five artifacts that had silently dropped out of the build (raw < characters read as JSX) restored to the site

Second Opinion Desk

“Can productized judgment - fixed price, fixed turnaround, verdicts in writing - work as a practice built on this knowledge base?”

theory to productionhuman in the loop governance

Building & Testing

  • -Two priced offers live at /desk, email intake first
  • -A prediction ledger design: published verdicts with skin in the game, empty until the first engagement earns an entry

Recent Progress

  • +The desk shipped (2026-08-26) after sitting fully built but undeployed since early August

KG-Combo: One Substrate

“What does a personal knowledge platform look like once every other system folds into it - instance routing, watches, scheduled tasks, governance?”

knowledge graph architecturememory architecture patternsmcp server patterns

Building & Testing

  • -A dozen knowledge-graph instances on one substrate, routed by domain instead of one big pile
  • -Watches and scheduled tasks replacing the standalone automation tools they made redundant

Recent Progress

  • +The site's knowledge-graph artifacts predate all of this - refreshing them is the next standing loop
  • +Retired systems archived rather than left half-alive: an event bus, an orchestration runtime, a mode system

Related Artifacts

Second Brain Pilot READMEContext Management Best Practices

The Loop Replaced the Methodology

“How small can a unit of execution get and still hold an agent accountable - and what happens to fifty phases of documentation when the methodology behind them retires?”

claudeops devops for aimulti agent orchestrationhuman in the loop governance

Building & Testing

  • -Loop discipline in production on this site: goal, deterministic gate, iteration budget, receipt in the repo
  • -Loop 2 next: a standing content-refresh cadence, two to three artifacts per iteration, instead of heroic batches

Recent Progress

  • +GSD retired 2026-07-06 after building this entire site; its eight artifacts now carry retirement banners instead of pretending to be current
  • +Loops 0 and 1 executed against the estate with receipts committed to the repo

Related Artifacts

GSD Planner AgentGSD Complete Command Reference