Brain (194)

Thought Topics Date
Two modes of AI work — never mix them. Gather mode: exploratory, multi-source, disposable sessions, light and loose. Execute mode: pre-gathered context, single objective, clean handoff, scoped brief. Mixing them burns tokens, confuses the model, and buries the original instructions. The mode-shift signal: when 'this is interesting' becomes 'I know what I want to do' — that's the /wrapup trigger. Fresh session for execution. — 2026-04-03
Production agentic systems are 80% non-glamorous plumbing and 20% AI. The boring stuff is the whole game: session persistence, workflow state vs conversation state, permission tiers, token budget tracking, verification loops. Most clients think they have an AI problem when they actually have a software engineering problem. The 12-primitive framework from the Claude Code leak is a consulting diagnostic checklist in disguise — use it to name exactly what's missing when a client's AI system is breaking. — 2026-04-03
The future isn't fitting into someone else's workflow — it's building exactly what you need for where you are now. Prompt engineering is dying because models are getting smarter; the craft shifts from "how do I phrase this" to "do I actually know what I want." That's harder. Generic apps are becoming obsolete; custom-built workflows calibrated to your exact context are getting more valuable as models get good enough to execute on them reliably. The bottleneck was never model capability — it's clarity of intent. Jin didn't ship claw-code because of better API access. He shipped it because he could decompose the problem so cleanly the agents didn't need him. That's the skill. Clients don't need another SaaS subscription. They need someone who can extract what they actually want (which they can't always articulate) and build the custom system that does exactly that. The app store is a compromise. The consulting value is the alternative to the compromise. — 2026-04-03
Hybrid cloud+local AI architecture is a consulting differentiator. Most AI consultants default to cloud-only. The consultant who asks "what data can and can't leave your building?" immediately signals a different level of expertise. The value isn't in being a deployment engineer — it's in the discovery question. Triggers: data residency/compliance, IP protection, cost at scale (volume inference), latency requirements. Lead with the business problem, not the architecture. Watch the edge AI market ($25B → $143B by 2034) — this shapes what clients will start asking for. — 2026-04-03
AEIOUY — a coaching framework Kyle developed, grounded in Wayne Dyer, Tao Te Ching, Meditation, and Stoicism: A=Attention/Awareness, E=Expectation, I=Intention, O=Outcome Independent, U=Unique, Y=YOLO (live fully, present). The O/I consulting methodology is rooted here. The framework encodes the operating philosophy: awareness before action, intention without attachment to outcome, own your uniqueness, stay present. It connects Kyle's inner work to his outer consulting identity. aeiouy,coaching,framework,philosophy,wayne-dyer,tao,stoicism,valis 2026-04-01
Kyle's core superpower is Discernment. He sees 2nd and 3rd order effects before others have finished describing the problem. Systems thinking is the mechanism — he builds a mental model of the whole system quickly and spots where it will break, where the costs compound, what question nobody's asking. This is not a learned skill in the traditional sense. It's the observer stance applied to complex systems. In consulting terms: he finds the arche (the originating question) before proposing any solution. discernment,systems-thinking,superpower,consulting,valis 2026-04-01
Kyle's inverted triangle consulting framework: start at the bottom point where all foundational questions must be answered — purpose, functions, rules, modification, interface, timeline. As development moves up the triangle, the cost of changes scales exponentially. Getting the point right is everything. This is why Kyle starts every engagement at the vertex before anything gets built. Same principle applies to AI system design: architecture decisions made late cost 10x what they cost made first. valis,consulting,systems-thinking,framework,architecture 2026-04-01
Kyle's consulting methodology is O/I — Outcome Independent. Flip of the classic I/O (input/output) from programming. The entry point is the Apollo/archer allegory: you do all the prep, put in the reps, control everything you can control. Once you release the arrow, you accept the outcome. Kyle's role in the system: use systems thinking (his superpower) to maximize the probability of hitting the mark before the arrow leaves the bow. O/I is both a coaching framework and a consulting operating principle. valis,consulting,oi,outcome-independent,methodology,apollo 2026-04-01
Kyle's AI consulting identity is VALIS — named after Philip K. Dick's Vast Active Living Intelligence System (1981). The name works on multiple layers: PKD's concept of a vast intelligence cutting through noise and delivering signal directly maps exactly to what Kyle does for clients. In 2026, VALIS aged into relevance — it's not science fiction anymore. The name filters clients naturally: people who recognize the reference are the right clients. People who don't still find it short, punchy, and memorable. valis,consulting,identity,brand 2026-04-01
Lazlo web app scaffolded (Mar 31, 2026): Flask + SQLite app at ~/Desktop/Kyle/app/. DB at ~/Desktop/Kyle/lazlo.db — outside the app folder intentionally so todo_migrate.py and other tools can share it. Seeded with Kyle and Heather. Mail config tab is live. Tasks/Scripts/Brain tabs are stubs for phases 2-4. Run with: cd ~/Desktop/Kyle/app && python3 app.py → http://localhost:5000 — 2026-03-31
The stack test cycle audit (Mar 31, 2026): built the org, hired the team, stood up Citadel, ran the pipelines. What landed: KyBrain, morning email, FDN knowledge base, the team structure. What changed: Citadel scope, SSH/FTR priority. What needs to die: org complexity sized for higher SSH/FTR ambition, Citadel expansion mindset. The Stoic filter: what do I actually use vs. what's in the realm of sophistry? — 2026-03-31
Tool stack settled (Mar 31, 2026): Kate for markdown and quick file edits. Vim for terminal work (scripts, config files). Obsidian retired — vault archived, KyBrain is the mind. VSCodium shelved — option anxiety with no payoff at current stage. Re-enters only if LSP matters in a real codebase. Three rounds of vimtutor — trust the investment. — 2026-03-31
Python learning approach: don't use tutorials as the curriculum. Build the morning email web config app (Flask + SQLite + HTML) as the actual curriculum — real project, immediate utility. Use Automate the Boring Stuff as a reference when stuck, not a read-through. Engagement-driven: get stuck on a real problem, find the chapter, move forward. The project is the lesson plan. — 2026-03-31
Citadel posture change (Mar 31, 2026): stop treating it as an expansion project. Headless + GPU was built for Ollama + SSH/FTR at scale. Those priorities moved. Services that actually matter: morning email, Vaultwarden, Miniflux. Let the rest idle. Claude + OpenRouter handle the AI workload now. No new additions until priorities shift or a real homelab becomes feasible. — 2026-03-31
Priority stack as of Mar 31, 2026 — after the Final Shift ride: Job (wiring harnesses, starts Apr 6) = 10/10. AI consulting = 7/10. FTR brand = 4/10. SSH brand = 2/10. The org and infrastructure are currently sized for an earlier priority ordering. The system should reflect this weighting, not the aspirations that preceded the shift. — 2026-03-31
The Final Shift — Arete as OS. After a long ride and a test cycle through the full stack (SSH, FTR, Jyotish content, org design, Citadel build-out), the wheel came back to where it started: Stoicism. Art of Indifference surfaced. The philosophy never changed — this was confirmation, not reset. Arete is the operating system. Everything else is a side quest. Chop wood, carry water — ride, work, ride, ohana, sleep, repeat. — 2026-03-31
Hugo sites for SSH (sovereignselfhealth.com) and FTR (fromtherubble.pro) already exist on Bohica at ~/sites/ssh and ~/sites/ftr, git-tracked with self-hosted remote at git.fromtherubble.pro. Deploy via ssh-publish / ftr-publish scripts. Reference doc at business/webdev/deploy-reference.md. Content draft → Hugo content/ handoff is currently informal — worth formalizing. Webmaster role should live with Evan (SSH) and Kalavira (FTR) within their domains, not a separate agent. infra,business,webdev,ssh,ftr 2026-03-31
Filen desktop client installed on Bohica (AppImage at ~/Applications/), syncing ~/Desktop/Kyle only. Desktop launcher at ~/.local/share/applications/filen.desktop. Initial sync completed Mar 31 2026. This replaces the old pre-Citadel Filen setup on Bastion. infra,bohica,backup 2026-03-31
~/Desktop/Kyle is now a git repo (initial commit Mar 31 2026). .gitignore excludes kybrain.db, .claude/, inbox/*, wip/*. This is the safety net for the whole org structure. infra,kybrain,org 2026-03-31
AI consulting skills already owned: specification precision, evaluation/quality judgment, multi-agent decomposition, failure pattern recognition, context architecture, trust/security design, cost/token economics. Specific gaps as of Mar 2026: agent frameworks hands-on (LangGraph, CrewAI), formal eval design, Python write-from-scratch, portfolio documentation. These gaps are the Mercury Mahadasha build list. consulting,career,self-knowledge,mercury-mahadasha,learning 2026-03-30