Search the Practicum

Type two letters · ↑↓ select · Enter open · Esc close

Type at least two letters.

Tools map by layer

Practicum for Chapter 6, "The Human as a System." Version: 2026-06-11. Update this page when new evidence appears. The selection principles stay stable, while examples change.

Important: Chapter 6 avoids naming specific tools because they change quickly. This page is the living version. It gives selection principles for each layer and dated examples. The examples show a class of tools and are not recommendations. The Tools Map lists concrete options for every layer, and the card for your profession lists tools for that role in the catalog.

How to read this map

Each layer of the personal AI system has one selection question, a short set of criteria, and dated examples of a tool class.

Ask three questions before adding anything to your system:

  1. Can I explain this tool's role in the system?
  2. Does it solve a task I have already identified in the TOM?
  3. Will I use it regularly, at least once a week?

If the answer is no, you do not need the tool now.

Layer 1: Thinking

Selection question: Does the tool help me think with AI while keeping my own judgment active?

Criteria:

  • Supports a conversation instead of one request followed by one answer.
  • Holds a long context without losing the thread.
  • Lets you ask follow-up questions and change direction.

Tool class (examples, 2025-2026):

  • Long-context chat: Claude, GPT-4o, Gemini Advanced for iterative reasoning.
  • Conversation workspaces: Claude Projects and ChatGPT Projects for persistent topic context.
  • Native voice mode when thinking on the move matters more than typing.

Sign of a weak Thinking layer: you ask AI one question, copy the answer, and stop.

Layer 2: Knowledge

Selection question: Can I give the AI tool enough task context within two minutes?

Criteria:

  • Stores notes in a form you can copy into an AI chat.
  • Searches content rather than only tags.
  • Keeps data somewhere you control, including outside company systems.

Tool class (examples, 2025-2026):

  • Searchable personal knowledge bases: Obsidian, a personal Notion space, Bear.
  • Vector search across your documents: NotebookLM and Mem.ai for questions about your own corpus.
  • Structured notes with backlinks: Logseq and Roam Research for nonlinear connections.

Sign of a weak Knowledge layer: every AI task starts with more than 20 minutes of searching for the right material.

Layer 3: Tools

Selection question: How many tools do I use actively, and can I explain the role of each one?

Criteria for every tool:

  • I use it at least once a week.
  • I can explain why it is better than an alternative for a specific task.
  • It saves at least 30 minutes a week or makes something possible that I could not do before.

Basic roles, meaning functions rather than products (2025-2026):

  • Capable chat and reasoning for difficult analysis, synthesis, and planning.
  • Search with summaries for research, such as Perplexity or Gemini with search.
  • A specialist agent for recurring work in code, law, finance, or another field.
  • Workflow automation that connects tools when a task repeats more than five times a week.

Sign of a weak Tools layer: you pay for more than 15 subscriptions and still keep looking for something new.

Layer 4: Proof

Selection question: Where can someone outside my team see my work?

Criteria:

  • The artifact is available without registration or behind only a small barrier.
  • It shows your way of thinking as well as the final result.
  • You updated it within the past six months.

Tool class (examples, 2025-2026):

  • Public writing: Substack, Medium, or a Telegram channel with an archive.
  • Professional portfolios: LinkedIn with cases rather than only job titles, and GitHub.
  • Video and audio: short explanations of difficult ideas through YouTube Shorts or podcasts.
  • Repositories and templates: open materials that other people use.

Sign of a weak Proof layer: only people who worked with you directly know about your expertise.

Layer 5: Trust

Selection question: Does the process include a consistent review before the result moves forward?

Criteria:

  • Review is part of the workflow, not something you do "when there is time."
  • It checks the mistakes that AI tends to make in your field.
  • It takes less than 15% of the task's total time.

Verification principles (2025-2026):

  • Check numbers and statistics manually against a primary source rather than through AI.
  • Check legal and financial conclusions against current rules, not the model's training data.
  • For professional recommendations, ask what has changed since 2024. Many models have a knowledge cutoff.

Sign of a weak Trust layer: you pass along the AI result without reading or checking it.

Layer 6: Outcome

Selection question: Is my work connected to a measurable result for the customer?

Criteria:

  • I know the metric that should change for the customer after my work.
  • I learn whether the customer used the result.
  • One month later, I can say what changed.

Measurement tools (examples, 2025-2026):

  • Direct metrics: OKRs or KPIs in a personal tracker, Notion, or a quarterly results table.
  • Indirect metrics: customer feedback and links to your work in other people's documents.
  • Portfolio tracking: compare tasks in the TOM after three months and see what changed in the "next level" column.

Sign of a weak Outcome layer: you can describe what you did but cannot say what changed.

How to update this map

  • Review named tools every six months.
  • Keep the principles and criteria stable unless the nature of a layer changes.
  • Update the version date whenever the examples change.
  • Do not add a tool until you have tested it in a real work task.

For examples of personal AI system levels and skills, see Examples by Level.

For the full Chapter 6 bibliography with verified links, see Volume 1 sources.

Tools map by layer