The Human Stack: Why Your AI Doesn't Know You Yet
You open a new AI chat. You type a task. You get something back that could have been written by anyone, for anyone.
So you try again. You rephrase. You add detail. You paste in some context you had to dig up from three different places. Three rounds later you have something passable. Multiply that by every interaction, every day, across every tool you use.
The problem is not the AI. The problem is what you are giving it.
Most people hand over a task and expect quality. But quality comes from context: who you are, how you think, what you have built, where you are heading. Without that, the machine is guessing. And it guesses average.
Eight Years of Searching
I spent the better part of a decade trying to find the right system for organising my thinking and my work. I tried everything. Notebooks, apps, second brain methodologies, digital gardens. Some of them were elegant. Some of them were genuinely well designed.
None of them stuck.
The friction was always the same. I would sit with a piece of information and ask myself: where does this go? Is this an area or a resource? Is this a project or a reference? The taxonomy made sense on paper but never became muscle memory. It felt like I was serving the system instead of the system serving me.
Then something shifted. AI stopped being a chat window and started becoming an operating environment. Agents that could read files, follow instructions, and maintain context across sessions. And I realised the question had changed completely.
The question was no longer: how do I organise my files so I can find them later?
The question was: how do I organise myself so an AI agent can do its best work?
That is a fundamentally different design problem. I was not looking for a better filing system. I wanted my knowledge and AI to work from the same sources. I could bring my judgment, and AI could help me develop the work. Amplified Intelligence in practice, not theory.
The Insight
Everyone builds a tech stack. Nobody builds a Human Stack.
A tech stack is layers of technology that work together. The Human Stack is layers of you. Your identity, your methodology, your active projects, your current priorities, your flowing thinking. Structured so any AI agent can read them, in the right order, at the right depth.
Different parts of your knowledge change at different speeds. Your identity changes slowly. Your priorities may change this week. Keeping them separate helps you update what changed.
The pyramid shows Identity as a foundation for your methods and work. Start with a short identity file and one useful task. You can add context as the work shows a need.
An identity document gives AI your voice, values and boundaries. It still needs accurate facts and a clear brief for the task. Check the result against your sources and expectations.
Five Layers, From Lasting Knowledge to Daily Thinking
The Human Stack is a pyramid. Five layers, from lasting identity to daily thinking.
Identity sits at the base. Who you are. This changes slowly, with your agreement. It is the foundation that everything else builds on.
Systems is your methodology. Frameworks, intellectual property, standard processes. This evolves as your methods develop.
Projects captures what you are actively building. Goals, constraints, stakeholders, current phase. This shifts as the work changes.
Pulse is your live state. This week's priorities, recent decisions, what is blocked. Updated weekly, sometimes more.
Thinking is the surface layer. Journal entries, meeting notes, captured insights, raw ideas. This changes daily. You do not load it every session. It is the living stream that feeds the other layers over time.
Together, the layers form a second brain: somewhere to capture experience, connect ideas and develop knowledge you can use again. AI can help retrieve and apply it. You decide what becomes established knowledge.
The full framework and implementation details live here.
The Engine Under the Layers
In my implementation, the layers hold files. AGENTS.md tells AI what to read and how to work. ME.md, INDEX.md and NOW.md provide a starting brief. Further sources are loaded when needed.
Each layer has a system file: ME.md (Identity), INDEX.md (Systems), CONTEXT.md (one per Project), and NOW.md (Pulse). The Thinking layer has no single file. It is folders of journal entries, insights, and meeting notes, mined when needed.
Every session follows the same cycle. The agent loads your identity, your routing table, and your current pulse. It checks what type of work is being done and loads the relevant frameworks. If the work is project-specific, it loads that project's briefing. Then the session happens. At the end, the agent updates whatever changed: shifted priorities, new decisions, captured insights.
This is the part that makes it alive. The AI does not just receive your context. It participates in maintaining it. Updates need review. Stale notes can mislead AI, so current summaries need to agree with their sources.
I asked my AI what it actually sees when it reads the stack. Its answer: "Identity gives me your voice. Systems gives me your methodology. Projects gives me your world. Pulse gives me your week. Thinking gives me your raw material." And when a layer is missing: "Skip Identity and I sound like a different person every session. Skip Pulse and I suggest the wrong priorities."
The full mechanical architecture, session flow, and AI perspective are on the Human Stack page.
Why AI Loads Selected Context
Your knowledge can be much larger than the brief for one task. AI has a limited active context, so it needs the relevant parts.
For a workshop revision, that might mean the learning objective, your teaching standards and the current material. It can retrieve an earlier decision if needed. Unrelated journals and client histories do not belong in that brief.
Persistent notes help later sessions recover decisions. This aligns with Anthropic's context engineering guidance on focused context, retrieval and notes across sessions. It supports the mechanism, without proving this particular five-layer model.
What Changed
Before the Human Stack, every AI session started with re-explaining. Who I am, what I sound like, what I am working on, what matters this week. I was spending the first ten minutes of every interaction just getting the machine up to speed.
With the files connected, a session starts with selected context. The AI reads my identity document, checks the routing table for the relevant frameworks, loads my current priorities. That gives the AI a brief about my work, voice and current priorities. It can retrieve further sources when needed.
The shift is not incremental. It is categorical. The AI went from a capable tool I had to manage to a thinking partner that operates inside my world. It stopped producing generic output and started producing work that sounds like me, references my frameworks, and fits my current priorities without being told.
I still check the work and correct what AI gets wrong.
Refined: Two Stacks. One Interface.
The Human Stack and Capability Stack sit within Amplify OS, short for The Amplified Operating System. Human Stack holds knowledge and context. Capability Stack includes AI, technology, tools and workflows. Prompts, skills, plugins and schedules are useful forms within it. Human-First and the two circles lead: Why and Who, with How in the overlap. The stacks make that direction practical.
The Interface tells a connected AI tool what to read. It uses AGENTS.md, ME.md, INDEX.md and NOW.md, plus CONTEXT.md for the relevant project. Keep the knowledge somewhere you control. Each tool needs a tested way to access it, with appropriate permissions.
The Human Stack holds the knowledge. The Capability Stack includes the AI, technology, tools and workflows used to act on it. The Interface connects them.
Keep the main working instructions in one file. If a tool expects a different filename, use a short file that points to those instructions.
The full framework on the Human Stack page explains the roles and how to use them.
Where to Start
Build Identity first. One focused session. One document: ME.md.
Write down who you are, what you do, how you sound, what you will not compromise on. Include examples of your real voice, not descriptions of it. Add the constraints that matter: words you never use, patterns you want to avoid, the line between your authority and your humility.
Use the file with a real task. Check whether AI follows your voice and boundaries, and correct what it misses.
Once Identity is solid, add your Systems routing table. Then project briefings. Then your weekly Pulse. Build the pyramid from the base, not the tip.
Once it is built, turn it over. The same five layers work like a funnel. What you capture and create each day lands at the top, in Thinking, and the best of it settles down slowly to who you are. You build it from the bottom up. You keep it alive from the top down.
Not sure where you stand? Take the 60-second diagnostic to find your level and your next step.
The full framework and implementation architecture are on the Human Stack page. Start there.