jdpolasky (ChasingGnosis) · GitHub
Skip to content
View jdpolasky's full-sized avatar

Block or report jdpolasky

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
jdpolasky/README.md

I'm a management consultant. JD/MBA. Experience with M&A, turnarounds, operations, marketing, and cross-sector work in energy, edtech, manufacturing, and services.

A few years back I started using AI seriously. I have no tech background, AI just fit the way my brain works. I'm twice-exceptional (2E) with strong pattern recognition, weak working memory, and generally poor exec function related to organization, time management, etc. Every productivity system I've ever tried has failed to mitigate my ADHD.

So I built my own.

Everything below is one body of work. chief-of-staff-2 is the system. ai-chief-of-staff-engine is its machinery. bloatbot and buildbot are the tools that keep it lean. ai-chief-of-staff is where it began.

A personal operating system for a chaotic professional life, in plain markdown in an Obsidian vault. It triages, tracks, briefs, and remembers. Model agnostic, ADHD-first, open to anyone. This is the current version, so start here.

New to it? The Obsidian setup guide wires your vault to an AI in a few minutes, and works with Claude Code, Codex, Gemini, and any other MCP agent.

The original. Version one kept growing until it had to be torn down and rebuilt as the repo above. It still works and shows where the ideas came from. The architecture converged independently with Andrej Karpathy's LLM Wiki, MemPalace, and Nous Research's Hermes Agent, all in a two-month window.

Also public

  • bloatbot. An auditor for your AI workspace. Finds the bloat, proposes the cuts, touches nothing.
  • buildbot. Its sibling, the builder. Interviews you, blueprints, builds only what you ratify, proves it while you watch.
  • ai-chief-of-staff-engine. The machinery behind the system: a memory engine and the operating loop built on it, eight staged releases, runnable and tested.
  • Notion vs Obsidian. Everything you need to know about using Notion and Obsidian with an LLM. Last verified August 2026.

What I'm doing

Independent consulting and fractional work across operations, marketing, and small-business builds, with AI as my operating layer. Writing and creating as ChasingGnosis on TikTok. Open to operator roles at AI-native companies, or enterprise engagements helping teams actually use AI.

Get in touch

Pinned Loading

  1. chief-of-staff-2 chief-of-staff-2 Public

    An AI Chief of Staff in plain markdown, in an Obsidian vault. Version two: torn down, rebuilt smaller, works better. Model agnostic, ADHD-first, open to anyone.

    22

  2. ai-chief-of-staff ai-chief-of-staff Public

    The original AI Chief of Staff built on Claude Code and Obsidian. ADHD prosthetic, open to anyone. Superseded by chief-of-staff-2.

    Python 98 15

  3. bloatbot bloatbot Public

    An auditor for your AI workspace. Finds the bloat, proposes the cuts, touches nothing.

    3

  4. ai-chief-of-staff-engine ai-chief-of-staff-engine Public

    A working, tested memory engine and operating loop for an AI chief of staff: bitemporal memory, session commands, enforcement hooks, incident logbook, self-tending rituals, capability registry, mod…

    Python 2

  5. buildbot buildbot Public

    A builder for your AI workspace. Interviews you, blueprints, builds only what you ratify, proves it while you watch.

    1