Reading map

Move from topics to articles, then to the important points.

This map is deliberately simple: topics lead to articles, and each article lists the main points you may want to check. The generated files expose the same structure to automation.

Topic

agent orchestration

Topic

ai agents

Topic

ai literacy

Topic

long human road to ai

Article maps

Each article appears once with its important points.

ai agentsai literacy

Tool Use: When the Model Calls Something Outside Itself

Tool use extends a language model beyond its trained knowledge by letting it call external capabilities such as search, code execution, and APIs, but its value depends on choosing the right tool, validating the result, and knowing when not to use one.

  1. C001 Tool use extends a language model by letting it invoke external capabilities it does not itself possess.
  2. C002 Tool use in AI is conceptually similar to delegation, remote procedure calls, and human use of instruments, but it automates the choice of which tool to invoke.
  3. C003 Common tool-use patterns include search, code execution, file or database retrieval, and API calls, each with different reliability and risk profiles.
  4. C004 Tool use introduces failure modes of wrong selection, bad arguments, misplaced trust in tool output, and unwanted actions that must be governed by permissions and checks.
ai agentsai literacy

Retrieval-Augmented Generation: Looking Things Up Before Answering

Retrieval-augmented generation improves a language model's answers by giving it relevant external material at request time, but the quality of the answer still depends on what can be found, how well it is matched, and whether the model uses it faithfully.

  1. C001 Retrieval-augmented generation gives a language model relevant external material at request time instead of relying only on its training data and the current prompt.
  2. C002 RAG builds on older ideas from information retrieval and open-book question answering: search for sources, then use them to answer.
  3. C003 A typical RAG pipeline has three stages: indexing documents, retrieving relevant chunks, and generating an answer conditioned on those chunks.
  4. C004 RAG reduces some kinds of hallucination, but it cannot fix missing, outdated, or misleading source material, and it can introduce new errors by misusing retrieved passages.
ai agentsai literacy

Reasoning Models: Slower Thinking, Better Checks?

Reasoning models improve difficult tasks by spending additional compute on explicit intermediate reasoning steps, but the gains come with higher latency, cost, and no guarantee of correctness.

  1. C001 Reasoning models improve hard tasks by deliberately spending more computation on explicit intermediate steps before producing a final answer.
  2. C002 Step-by-step problem solving is an old idea; what changed is scale and language-driven search.
  3. C003 In practice, reasoning models expose a longer trace of intermediate reasoning that can be inspected, even if the trace is not always faithful or complete.
  4. C004 The gains from reasoning models are strongest on complex, well-defined tasks and weakest on simple, ambiguous, or human-judgment tasks.
ai agentsai literacy

Prompt Engineering: Instruction Design, Not Magic Words

Prompt engineering is the disciplined design of instructions, examples, constraints, and evaluation criteria so that a language model produces useful, reliable output.

  1. C001 A prompt is not just a question; it is the designed instruction, context, examples, and constraints that shape what a language model produces.
  2. C002 Prompt engineering resembles older practices such as clear writing, task design, and human-computer interaction, updated for probabilistic language models.
  3. C003 Practical prompt engineering uses techniques—such as giving examples, breaking tasks into steps, and defining output formats—to steer model behavior.
  4. C004 Prompt engineering is a powerful interface tool, but it cannot fix model errors, guarantee truthfulness, or replace evaluation and oversight.
ai agentsai literacy

Prompt Caching: Reusing Stable Context

Prompt caching reduces latency and cost by reusing repeated prompt or context prefixes, but the benefit depends on stable prefixes, provider rules, and enough repeated calls to offset cache-write costs.

  1. C001 Prompt caching reuses the unchanged prefix of a prompt so the provider does not have to reprocess it on every call.
  2. C002 Prompt caching is a specialized form of memoization: it stores the result of an expensive computation so later requests can reuse it.
  3. C003 In practice, prompt caching saves the most when a large, stable prefix is sent repeatedly and the variable part stays at the end.
  4. C004 The savings from prompt caching are bounded by which tokens match, the provider's pricing and retention rules, and whether the same prefix is reused often enough to offset cache-write costs.
ai agentsai literacy

Planning and Reflection: How AI Breaks Down and Revises Work

Planning and reflection give an AI agent the ability to organize work before acting and to correct course after observing results, turning a single prompt into a structured, self-correcting workflow.

  1. C001 Planning breaks a goal into ordered steps before action; reflection checks results against the goal and decides whether to revise the plan.
  2. C002 Planning and reflection are rooted in project management, scientific method, and classical AI search, not only in recent language models.
  3. C003 In practice, AI planning and reflection appear as upfront plans, iterative plan-revise loops, and step-by-step reasoning with final verification.
  4. C004 Reflection in AI agents is most reliable when paired with external checks such as tests, retrieved sources, or human review; self-critique alone can confirm rather than catch errors.
  5. C005 A self-harness pattern can turn one-off reflection into reusable verification routines that are proposed by the model and validated against held-out examples.
ai agentsai literacy

Multi-Agent Systems: When More Than One AI Worker Is Involved

Multi-agent systems split complex work across specialized AI agents, but the engineering value comes from coordination, communication, evaluation, and cost tradeoffs, not from simply adding more agents.

  1. C001 A multi-agent system solves a problem by dividing it among specialized agents and coordinating their work, not by simply running several models in parallel.
  2. C002 Multi-agent systems borrow ideas from distributed systems, ensemble methods, and organizational design, not just recent AI research.
  3. C003 Common multi-agent patterns include sequential pipelines, manager-and-workers, and debate-and-review, and each pattern carries different coordination risks.
  4. C004 Adding agents increases coordination cost, ambiguity, and failure modes; a multi-agent design should be justified by a specific division of labor, not by default.
ai agentsai literacy

Memory vs Context: What Should Survive the Conversation?

Context is the immediate working material an AI can see right now; memory is selected information that persists across time and must be deliberately retrieved or stored.

  1. C001 Context is immediate working material; memory is selected information that persists across time and must be deliberately retrieved or stored.
  2. C002 The split between immediate context and stored memory appears in cognitive psychology, user interfaces, and database design, not only in recent AI.
  3. C003 Practical AI systems move information between context and memory through summarization, retrieval, and structured storage, and each transfer is a chance to lose or distort meaning.
  4. C004 Memory is only useful when retrieval is accurate, updates are careful, and forgetting is as deliberate as remembering.
ai agentsai literacy

Loops vs Goals: The Difference Between Repetition and Direction in AI Agents

In long-running AI systems, loops provide repeated progress, but loops only become useful when governed by clear goals, exit conditions, progress checks, and stopping rules.

  1. C001 A loop repeats work; a goal gives the loop direction and a stopping point.
  2. C002 The pairing of loops and goals appears in control engineering, reinforcement learning, and the scientific method, not only in recent AI.
  3. C003 Practical AI loops repeat steps such as thinking, acting, observing, editing, or searching until a goal is reached or an exit condition fires.
  4. C004 Long-running AI sessions need exit conditions and progress checks to avoid drift, runaway work, or hidden goal substitution.
ai agentsai literacy

Long-Running Sessions: Keeping AI Work Coherent Over Time

Long-running AI sessions need clear goals, summaries, memory, checkpoints, context pruning, and stopping rules to avoid drift and wasted work.

  1. C001 A long-running session is useful only when the system can remember what matters, recognize progress, and decide when to stop.
  2. C002 Keeping extended work coherent is already familiar from workflow orchestration, durable execution, project management, and process control.
  3. C003 In practice, long-running sessions combine summarization, checkpoints, context pruning, and prompt caching to keep the active window focused without losing the goal.
  4. C004 Without summaries, checkpoints, and stopping rules, long-running sessions drift, waste resources, or resume in broken states.
  5. C005 Prompt caching can cut the cost and latency of repeated context in long sessions, making extended sessions more practical.
ai agentsai literacy

Fine-Tuning: Teaching a Model a Narrower Behavior

Fine-tuning reshapes a model's learned behavior by continuing training on targeted examples, making it useful for stable, narrow tasks, but it is not a substitute for clear instructions, good data, or ongoing evaluation.

  1. C001 Fine-tuning changes a model's learned behavior by continuing training on targeted examples, rather than changing what the model sees at runtime.
  2. C002 Fine-tuning is a form of transfer learning: it adapts a general model to a narrower task using additional examples.
  3. C003 Fine-tuning works best when the task is narrow, the desired outputs are consistent, and high-quality labeled examples are available.
  4. C004 Fine-tuning can bake in errors, biases, or brittle patterns from the training data, so it must be paired with evaluation and clear limits.
ai agentsai literacy

Evaluations: How We Know an AI Workflow Improved

Evaluations turn vague quality claims into testable checks by defining what 'good' means, collecting evidence, and distinguishing real improvement from noise or gaming.

  1. C001 An evaluation is a test that turns a quality claim into a repeatable, observable result.
  2. C002 Benchmarks, report cards, and clinical trials all evaluate outcomes against a standard; AI evaluation extends the same idea to generated outputs and workflows.
  3. C003 A practical AI evaluation usually mixes automatic checks, human judgments, and task-specific metrics rather than relying on a single score.
  4. C004 A high score on a benchmark can hide failure modes that matter in real use, because no metric captures every kind of usefulness or harm.
ai agentsai literacy

Context Management: What the AI Sees Right Now

Context management is the process of selecting, organizing, and limiting the information placed in a model's current working window so that the most relevant material is available without exceeding capacity.

  1. C001 A model can only work with the information currently in its context window; context management decides what that information is.
  2. C002 Context management resembles human working memory and attention, but it uses fixed-size, lossy windows rather than flexible human recall.
  3. C003 Retrieval and summarization can extend the effective context, but they trade completeness, accuracy, and cost.
  4. C004 Good context management requires deciding what to include, what to compress, and when to stop, because a bigger window is not always a better answer.
ai agentsai literacy

AI, De-Mystified: A Field Guide to Modern AI Terminology

Modern AI terminology becomes less confusing when each term is explained through plain language, older related ideas, practical examples, benefits, limits, and academic roots rather than being treated as a fresh breakthrough every time.

  1. C001 AI terminology becomes more useful when each term is explained through plain language, older related ideas, practical examples, benefits, limits, and academic roots instead of being treated as a fresh breakthrough every time.
  2. C002 A repeating article structure makes it easier for readers to learn one concept at a time and compare new terms with ideas they already know.
  3. C003 Keeping the series inside Aura Knowledge, focused on one concept at a time, protects it from becoming a broad encyclopedia, benchmark hub, or product marketing guide.
ai agentsai literacy

Agents: Goal-Directed AI Systems That Use Tools

An AI agent is a goal-directed system that uses tools, loops, context, memory, and evaluation to keep working across multiple steps instead of producing a single response.

  1. C001 An AI agent is a system that pursues a goal across multiple steps, choosing when to use tools, what to remember, and when to stop.
  2. C002 The idea of an agent that follows goals and uses tools is older than large language models; it appears in automation scripts, personal assistants, and game AI.
  3. C003 In practice, an agent's loop repeatedly decides which tool to use, what to remember, and whether the goal is satisfied.
  4. C004 Agent behavior depends heavily on clear goals, reliable tools, and careful limits; without them, autonomy becomes cost and error.
  5. C005 A modern AI agent can be understood as a model plus a harness that provides tools, memory, permissions, checkpoints, and human oversight.
ai agentsagent orchestrationhuman ai interaction

AI Delegation Orchestration: A Series on Durable Agent Work

AI interfaces can stay conversational, but consequential AI work should be governed through durable delegations, explicit records, operator control surfaces, and domain-specific review boundaries rather than chat transcripts alone.

  1. C001 AI interfaces can stay conversational, but consequential AI work should be governed through durable delegations, explicit records, operator control surfaces, and domain-specific review boundaries rather than chat transcripts alone.
ai agentsagent orchestrationhuman ai interaction

Commitment Boundaries in High-Stakes Domains

High-stakes AI use should be designed around commitment boundaries: AI may help prepare work, but external, legal, financial, public, or rights-affecting actions need stricter evidence, review, appeal, privacy, and accountability controls.

  1. C001 High-stakes AI use should be designed around commitment boundaries: AI may help prepare work, but external, legal, financial, public, or rights-affecting actions need stricter evidence, review, appeal, privacy, and accountability controls.
ai agentsagent orchestrationhuman ai interaction

Capability Contracts for Agent Networks

Agent systems should be organized around replaceable capabilities with explicit contracts, not around vague role prompts or artificial replicas of human organizations.

  1. C001 Agent systems should be organized around replaceable capabilities with explicit contracts, not around vague role prompts or artificial replicas of human organizations.
ai agentsagent orchestrationhuman ai interaction

Long-Running Delegations: How Agents Can Work for Hours Without Losing the Plot

Long-running AI work is viable only when the delegation has checkpoints, evidence gates, self-remediation loops, interruption rules, rollback paths, and explicit stop conditions.

  1. C001 Long-running AI work is viable only when the delegation has checkpoints, evidence gates, self-remediation loops, interruption rules, rollback paths, and explicit stop conditions.
ai agentsagent orchestrationhuman ai interaction

Control Loci, Not Human Managers: An Agent-Native Routing Model

Agent systems should route decisions to the right control locus instead of copying human management structures or escalating every uncertainty to a person.

  1. C001 Agent systems should route decisions to the right control locus instead of copying human management structures or escalating every uncertainty to a person.
ai agentsagent orchestrationhuman ai interaction

The Operator Cockpit Problem: Why More Traces Are Not Enough

The operator problem is not lack of information; it is lack of control routing across many active delegations.

  1. C001 The operator problem is not lack of information; it is lack of control routing across many active delegations.
ai agentsagent orchestrationhuman ai interaction

The Delegation Record: A Schema for Consequential AI Work

A delegation record is the system-of-record artifact that makes AI work inspectable, resumable, reviewable, and bounded.

  1. C001 A delegation record is the system-of-record artifact that makes AI work inspectable, resumable, reviewable, and bounded.
ai agentsagent orchestrationhuman ai interaction

From Conversation to Delegation: Why AI Work Needs a Durable Record

Conversation can remain the interface for AI, but consequential AI work should be organized around bounded delegations rather than chat transcripts.

  1. C001 Conversation can remain the interface for AI, but consequential AI work should be organized around bounded delegations rather than chat transcripts.
audiovoice interfacesai agents

Listening to the Firehose: Can Voice-First, Two-Way Audio Become a Legitimate Assistive Medium?

Voice-first, two-way audio agents are technically ready to become a useful complement to screen-based reading for knowledge workers, but only if designers treat them as assistive, user-controlled, and hearing-safe tools—not as replacements for reading or as always-listening ambient companions.

  1. C001 Heavy screen use is widespread among working-age adults and is associated with significant productivity and wellbeing costs, including digital eye strain.
  2. C002 Listening and reading impose different cognitive demands; audio is generally more transient and pace-dependent, making it a complement rather than a drop-in replacement for reading.
  3. C003 End-to-end, full-duplex spoken dialogue models have moved from research demos to publicly documented systems with low enough latency for natural turn-taking.
  4. C004 The value of voice-first audio agents depends more on interaction design—turn-taking, interruption, proactivity, and user agency—than on raw conversational naturalness.
  5. C005 Proactive and always-listening audio agents risk intrusiveness and attention capture; user-initiated or notification-triggered sessions better preserve agency.
  6. C006 Voice-first curation can amplify filter-bubble dynamics in a channel with fewer visual cues for verification, so transparency and user control over selection are essential.
  7. C007 A trigger-based, off-screen audio review layer is a promising near-term pattern, but it should be treated as a testable hypothesis rather than a proven product design.
ai agentsonboardingai literacy

You Do Not Need to Learn AI First: A 5-Minute Conversation Recipe

Non-technical adults and teens can start using AI agents by copying one plain-language prompt into any capable model, letting the agent interview them about an everyday problem and suggest what to ask next.

  1. C001 A single model-agnostic starter prompt is a more effective onboarding artifact for non-technical users than a feature list or vendor tutorial.
  2. C002 The AI agent itself can act as the tutor, so newcomers do not need to study AI before they start using it.
  3. C003 Suggesting the next question or direction after each answer removes the blank-page problem and keeps the experience experiential rather than instructional.
  4. C004 Two short annotated transcripts are enough to teach the pattern: one proving intelligence through document explanation, and one proving productivity through one-input-multiple-outputs automation.
ai agentsonboardingai literacyprivacyprompting

Beyond the First Conversation: Advanced Questions for New AI Agent Users

Non-technical adults and teens who have tried an AI agent once or twice can use it more confidently by learning practical answers to common follow-up questions about privacy, errors, trust, prompts, automation, and model choice.

  1. C001 A short concrete privacy checklist is usually more practical for new AI users than a long explanation of how training data works.
  2. C002 Teaching new users three recovery moves — ask for sources, rephrase, and test with a known answer — is enough to turn a wrong answer from a stop sign into a learning moment.
  3. C003 A simple low-stakes versus high-stakes framing is enough to help non-technical users decide when to verify AI output.
  4. C004 Asking the agent for a brief summary at the end of a session is the easiest way for a beginner to preserve context across multiple conversations.
  5. C005 Four plain-language moves — context, desired output, exclusions, and options — are enough to improve most beginner prompts without teaching prompt-engineering jargon.
  6. C006 A repeated "doing" prompt saved as a reusable template is the simplest form of automation for non-technical AI users.
  7. C007 A short task-based comparison table is more useful to non-technical readers than benchmark scores or feature lists.
ai agentsagent orchestrationllm routing

From Agent Swarms to Agent Control Planes

Agent orchestration is shifting from hand-written workflows toward governed control planes that route across models, tools, memory, evaluators, policies, and execution environments, making routing, observability, and policy enforcement infrastructure concerns rather than per-agent code.

  1. C001 Agent orchestration is shifting from hand-written workflows toward governed control planes that route across models, tools, memory, evaluators, policies, and execution environments.
  2. C002 Mixture-of-Experts and conditional computation predate LLMs and provide the earliest architectural precedent for learned routing.
  3. C003 Learned routers such as FrugalGPT and RouteLLM can match or exceed single-model accuracy at a fraction of the cost, though benchmark caveats apply.
  4. C004 Test-time search strategies—self-consistency, Tree of Thoughts, Reflexion, and multi-agent debate—expand what a control plane can spend compute on at runtime.
  5. C005 Recent learned orchestrators such as Sakana Fugu, Trinity, and Conductor are signals of automated scaffold generation, not settled production recipes.
  6. C006 Production control planes combine routing, fallback, policy, memory, evaluation, observability, and lifecycle governance, but no single vendor owns all of them.
  7. C007 The term 'control plane' is contested across vendors; teams should judge products by concrete capabilities rather than marketing labels.
  8. C008 Teams should treat model selection, fallback, observability, and policy enforcement as infrastructure concerns rather than per-agent code.
long human road to aiai historycomputing historyhuman progresseducation

The Long Human Road to AI: A Reader’s Guide to Season 1

Artificial intelligence is best understood as the latest chapter in a long human story of extending memory, calculation, communication, measurement, coordination, prediction, and delegation.

  1. C001 Artificial intelligence is easiest to understand when it is presented as the latest chapter in a much longer human story of extending memory, calculation, communication, measurement, coordination, prediction, and delegation.
  2. C002 Computers and AI emerged from long-running human needs and older tools rather than arriving as a single invention.
  3. C003 Across the season, the same pattern appears: human need → external support → formalization → scale → boundary.
  4. C004 The 1956 Dartmouth workshop named and helped launch AI as a research agenda, but it was one meeting point among many precursors.
  5. C005 AI progress repeatedly moved from hand-coded rules and symbols toward learning from examples, then toward scaled general-purpose models.
  6. C006 Modern AI capabilities are shaped by data, compute, people, organizations, evaluation, governance, infrastructure, and public trust—not only by algorithms.
  7. C007 Analogies help make AI history understandable, but they are teaching devices, not evidence, and every analogy has a limit.
long human road to aimachine learningneural networkscomputing history

Learning Machines: Statistics, Neural Networks, and the Data Turn

The learning turn in AI moved behavior from hand-written rules to adjustable parameters shaped by examples, feedback, statistics, neural-network training methods, datasets, benchmarks, and compute, becoming persuasive only when algorithms, data, hardware, evaluation, and engineering reinforced one another.

  1. C001 The shift from hand-coded rules to learning from examples changed AI by combining statistics, neural networks, datasets, benchmarks, compute, and infrastructure into systems that infer useful patterns rather than only follow explicit instructions.
  2. C002 The early AI field framing already included learning as a central feature of intelligence.
  3. C003 Samuel's checkers work is an early public example of a program improving through machine-learning procedures rather than relying only on fixed, hand-authored play.
  4. C004 Rosenblatt's perceptron framed pattern recognition through adaptive connections and probabilistic analysis, making the idea of a learning machine visible to a broad audience.
  5. C005 Minsky and Papert analyzed limitations of perceptron models and helped clarify why simple architectures were insufficient for many interesting tasks.
  6. C006 The 1986 Nature paper helped make backpropagation for multilayer networks practically legible to a broad research audience, and gradient-trained convolutional networks were already being used for document recognition by the late 1990s.
  7. C007 ImageNet and ILSVRC helped make large labeled datasets and shared benchmarks central infrastructure for computer-vision progress.
  8. C008 AlexNet made the combination of deep networks, ImageNet-scale data, and GPU implementation newly persuasive in 2012, but the result should be read as a convergence of factors rather than proof that compute alone or learned patterns equal understanding.
long human road to aiai societylaborgovernanceinstitutions

The Human Road Through AI: Labor, Institutions, Governance, and Meaning

AI is a social arrangement as much as a technical artifact; labor, governance, education, access, and public trust are part of the system itself and shape who benefits from AI and who bears the costs of delegation.

  1. C001 AI systems that appear automatic at the interface still depend on human work, judgment, evaluation, maintenance, governance, and contestation.
  2. C002 Task exposure to generative AI should not be treated as a direct forecast of job replacement.
  3. C003 Governance frameworks and laws are part of the AI system because they assign duties for risk, transparency, oversight, accountability, and redress.
  4. C004 Education, science, and authorship debates about AI are debates about human judgment, evidence, disclosure, and responsibility.
  5. C005 AI benefits depend on material access conditions: connectivity, devices, language, skills, compute, affordability, energy systems, and local institutions.
  6. C006 Public trust is a design constraint because adoption depends on people's ability to understand, challenge, and rely on AI-mediated systems.
long human road to aifoundation modelstransformersscalingai governance

Foundation Models and the Return of General-Purpose AI Systems

Foundation models revived the ambition of general-purpose AI systems by making one broadly trained model adaptable across many tasks, but broad capability is not the same as humanlike understanding or reliable agency.

  1. C001 A foundation model is a broadly trained model, generally trained with self-supervision at scale, that can be adapted to many downstream tasks.
  2. C002 Foundation models revive general-purpose AI ambition by supporting many tasks from a shared base, but this should not be equated with humanlike understanding.
  3. C003 The Transformer replaced recurrence and convolution with attention for sequence transduction and made training more parallelizable.
  4. C004 Broad pretraining enabled models such as BERT and GPT-3 to be adapted or prompted across many tasks.
  5. C005 Scaling research made model size, data, and compute explicit variables, while later work emphasized compute-optimal allocation rather than model size alone.
  6. C006 Instruction tuning and RLHF can improve usefulness and intent-following, but do not eliminate mistakes or alignment limits.
  7. C007 Natural-language supervision and multimodal training widened foundation-model behavior beyond text-only tasks.
  8. C008 Retrieval, tool use, and reasoning/action loops can extend model behavior by connecting models to external sources, APIs, and environments.
  9. C009 Language-model evaluation needs multi-metric transparency because accuracy alone hides tradeoffs in calibration, robustness, fairness, bias, toxicity, and efficiency.
  10. C010 As of 2026-06-19, the 2026 AI Index reports rapid changes in AI capabilities, adoption, incidents, and responsible-AI measurement gaps.
  11. C011 As of 2026-06-19, NIST AI 600-1 is the generative AI profile used here for lifecycle risk-management framing.
  12. C012 As of 2026-06-19, European Commission pages state that EU general-purpose AI model rules became effective in August 2025 and that the Code of Practice supports compliance.
long human road to aiformal logiccomputabilityinformation theorycybernetics

From Formal Logic to Computation: The Mathematical Road to AI

Modern computing and AI became thinkable partly because humans developed formal symbol systems, logic, computability, switching circuits, information theory, and feedback concepts that turned reasoning into something machines could represent and execute.

  1. C001 Algebraic and symbolic treatments of logic helped make reasoning inspectable and manipulable as formal symbol systems.
  2. C003 The formalist ambition around mathematical foundations and decision procedures created the problem setting in which computability could be made precise.
  3. C004 Gödel's incompleteness theorems showed that consistent formal systems strong enough for arithmetic have intrinsic limits, complicating the dream of complete formal foundations.
  4. C005 Church, Turing, and Post offered different formalizations of effective procedure, helping turn computation into a mathematical subject before modern computers were common.
  5. C006 The Church-Turing thesis concerns effective methods and is often misunderstood when treated as a claim about all physical machines or minds.
  6. C007 Shannon's switching-circuit work connected Boolean algebra to relay and switching circuit design, helping make logic part of digital engineering.
  7. C008 Shannon's communication theory provided a mathematical treatment of messages, channels, noise, and information, but it is not a theory of semantic meaning.
  8. C009 Cybernetics supplied a language of feedback, control, and communication for thinking about machines and organisms, but feedback alone is not intelligence.
long human road to aiai historysymbolic ai

The Birth of AI: Dartmouth, Symbolic Systems, and Early Optimism

AI's 'birth' is best treated as a naming and consolidation moment. The 1956 Dartmouth workshop gave the field a label, an agenda, and institutional visibility, while early symbolic systems showed that computers could perform some formal activities associated with intelligence. The lasting lesson is not that intelligence was solved in the 1950s, but that researchers discovered how hard it was to translate intelligence into symbols, rules, search, and programs.

  1. C001 Dartmouth named and consolidated AI as a research field, but did not originate all machine-intelligence work.
  2. C002 Early AI treated reasoning as symbolic manipulation and search.
  3. C003 Early demonstrations were impressive but bounded: they worked inside formal or carefully prepared worlds.
  4. C004 Early AI optimism was part technical, part institutional, and part public narrative.
  5. C005 The early field included multiple lineages, including symbolic reasoning, cybernetics, neural approaches, game-playing, and machine-intelligence philosophy.
long human road to aiai historycomputing historyhuman progresseducation

Before Machines: Calculation, Automata, and the Dream of Mechanical Reason

Before electronic computers existed, people performed calculation as organized labor and built tools, tables, mechanisms, and automata to extend what human minds could reliably do. Those developments make later computing and AI more understandable only when they are presented as context, not as primitive computers or artificial intelligence.

  1. C001 Computation was performed by people before it became associated with electronic machines.
  2. C002 Counting boards and abaci moved arithmetic into visible physical state that could be manipulated and checked.
  3. C003 Rods, tables, and logarithmic methods reduced complex calculations by decomposing or reusing prior work.
  4. C004 Seventeenth-century mechanical calculators embodied arithmetic operations in physical mechanisms.
  5. C005 The Antikythera mechanism was a sophisticated geared astronomical calculator or display mechanism.
  6. C006 Automata made mechanism appear self-directed, inviting audiences to project life or agency onto fixed motion.
  7. C007 Jacquard punched cards controlled textile patterns and influenced later ideas about machine input and control.
  8. C008 Babbage's engines mark a threshold between mechanical arithmetic and designs for automatic computing machinery.
long human road to aiai historyexpert systemsevaluationhype cycle

Winters, Expert Systems, and the Cost of Overpromising Intelligence

AI winters and expert systems show that progress in AI has repeatedly depended not only on ideas, but also on evaluation, maintenance, infrastructure, institutional expectations, and the cost of overpromising intelligence.

  1. C001 Public evaluation reports such as ALPAC and Lighthill mattered because they tested AI-adjacent promises against measurable usefulness, not because they proved intelligence research was worthless.
  2. C002 The phrase 'AI winter' should be handled as a contested historical label for reduced confidence, funding, and commercial enthusiasm, not as proof that AI research stopped.
  3. C003 Expert systems produced useful results in narrow domains where domain knowledge could be encoded and maintained.
  4. C004 Expert-system limits included knowledge acquisition, updating, evaluation, user trust, and workflow integration, not only inference algorithms.
  5. C005 The durable lesson for modern AI is that intelligence claims need grounded tests, maintenance plans, and institution-aware deployment criteria.
agentic commerceproduct truthconsumer behavioropen protocolsincumbent adjacent ventures

Agentic Commerce and the Product Truth Layer

AI shopping agents may shift commerce from capturing human attention to satisfying delegated buyer intent; if that possibility develops, it could create demand for open, privacy-preserving, adversarially tested product assurance infrastructure that agents can inspect.

  1. C001 Modern online commerce is still largely organized around human attention, even when AI is used behind the scenes for targeting, ranking, and recommendation.
  2. C002 Some brand loyalty is actually status quo bias plus choice overload: the customer sticks with a known product because the market has made exploration expensive.
  3. C003 One plausible next commerce shift is from the attention economy to delegated-intent commerce: agents may increasingly translate user preferences into product discovery and purchase decisions.
  4. C004 Agentic commerce is likely to need a product assurance layer richer than current product structured data, because agents need evidence, constraints, provenance, and user-fit signals rather than only titles, offers, ratings, and images.
  5. C005 The healthiest version of agentic commerce is an open product-truth commons: a contestable, forkable, provenance-rich vocabulary for product claims, evidence, reviews, and buyer-agent preferences.
  6. C006 Post-purchase feedback can evolve from star ratings into structured experience packets that preserve human judgment while making outcomes legible to agents.
  7. C007 B2B agentic buying may move slower across complex purchases, but narrow recurring procurement categories can be stronger MVP wedges because outcomes are measurable.
  8. C008 The strategic opportunity is not necessarily to replace commerce incumbents, but to demonstrate a concrete agentic behavior, such as buyer-aligned product switching backed by evidence packets and post-purchase feedback, that incumbents may later adopt, adapt, or standardize around.
  9. C009 Agentic product trust should shift from review aggregation to adversarial claim ledgers: each product claim should carry source, scope, evidence, counter-evidence, incentive, expiry, and dispute state.
  10. C010 A fair product-truth commons needs graded evidence tiers so offline buyers and small sellers can participate without pretending every attestation has the same trust weight.
  11. C011 Product-truth infrastructure can reduce the value of fake reviews, but it cannot eradicate manipulation; it moves the battlefield from cheap text generation to collusion, credential abuse, data access, privacy leakage, and governance capture.
  12. C012 Private review entitlements should separate purchase or use verification from public identity: the public system should verify an unlinkable, one-time entitlement token rather than linking a review to a user, receipt, store, or account.
  13. C013 Agentic commerce should expose a dual evidence surface: machine-readable claim ledgers for agents and human-readable media, social, community, and brand context for final human judgment.
  14. C014 Agentic product assurance should be built around signed, scoped, contestable claims about specific product identities, not aggregate reviews or universal truth labels.
  15. C015 Robust agentic product assurance needs infrastructure beyond reviews and credentials: product identity/versioning, recall feeds, liability, auditors, decision receipts, dispute propagation, portability, red-team benchmarks, and accessible presentation.
ai native publishingresearch workflowsagent provenancedigital gardens

The Future of Publishing Is Agent-Auditable Research

The future of serious publishing is human-authored research that agents can audit: readable essays backed by claim graphs, evidence ledgers, provenance, revision history, and disclosed agent involvement.

  1. C001 Polished prose is becoming cheap; inspectable reasoning is becoming scarce.
  2. C002 A future-ready publishing artifact should pair a human essay with a claim graph, evidence ledger, provenance, revision history, and agent contribution record.
  3. C003 Research is the best first wedge because the audience already values citations, methods, uncertainty, and credibility.
  4. C004 Existing publishing, AI research, and protocol tools solve important pieces but not the combined readable-plus-auditable source object.
  5. C005 AI assistance should be disclosed while the human remains accountable for thesis, source selection, wording, and conclusions.
  6. C006 Attention-aware reading and machine-readable structure are compatible when the page uses progressive disclosure.

Review history

Map links and review history

Each link is generated from the published records at build time. Supporting and contrasting source notes create the strongest links; related-article links come from the article record.

  • argues The Future of Publishing Is Agent-Auditable Research Polished prose is becoming cheap; inspectable reasoning is becoming scarce. machine-generated · 2026-06-17
  • argues The Future of Publishing Is Agent-Auditable Research A future-ready publishing artifact should pair a human essay with a claim graph, evidence ledger, provenance, revision history, and agent contribution record. machine-generated · 2026-06-17
  • argues The Future of Publishing Is Agent-Auditable Research Research is the best first wedge because the audience already values citations, methods, uncertainty, and credibility. machine-generated · 2026-06-17
  • argues The Future of Publishing Is Agent-Auditable Research Existing publishing, AI research, and protocol tools solve important pieces but not the combined readable-plus-auditable source object. machine-generated · 2026-06-17
  • argues The Future of Publishing Is Agent-Auditable Research AI assistance should be disclosed while the human remains accountable for thesis, source selection, wording, and conclusions. machine-generated · 2026-06-17
  • argues The Future of Publishing Is Agent-Auditable Research Attention-aware reading and machine-readable structure are compatible when the page uses progressive disclosure. machine-generated · 2026-06-17
  • covers The Future of Publishing Is Agent-Auditable Research agent-provenance machine-generated · 2026-06-17
  • covers The Future of Publishing Is Agent-Auditable Research ai-native-publishing machine-generated · 2026-06-17
  • covers The Future of Publishing Is Agent-Auditable Research digital-gardens machine-generated · 2026-06-17
  • covers The Future of Publishing Is Agent-Auditable Research research-workflows machine-generated · 2026-06-17
  • argues From Agent Swarms to Agent Control Planes Agent orchestration is shifting from hand-written workflows toward governed control planes that route across models, tools, memory, evaluators, policies, and execution environments. machine-generated · 2026-06-26
  • argues From Agent Swarms to Agent Control Planes Mixture-of-Experts and conditional computation predate LLMs and provide the earliest architectural precedent for learned routing. machine-generated · 2026-06-26
  • argues From Agent Swarms to Agent Control Planes Learned routers such as FrugalGPT and RouteLLM can match or exceed single-model accuracy at a fraction of the cost, though benchmark caveats apply. machine-generated · 2026-06-26
  • argues From Agent Swarms to Agent Control Planes Test-time search strategies—self-consistency, Tree of Thoughts, Reflexion, and multi-agent debate—expand what a control plane can spend compute on at runtime. machine-generated · 2026-06-26
  • argues From Agent Swarms to Agent Control Planes Recent learned orchestrators such as Sakana Fugu, Trinity, and Conductor are signals of automated scaffold generation, not settled production recipes. machine-generated · 2026-06-26
  • argues From Agent Swarms to Agent Control Planes Production control planes combine routing, fallback, policy, memory, evaluation, observability, and lifecycle governance, but no single vendor owns all of them. machine-generated · 2026-06-26
  • argues From Agent Swarms to Agent Control Planes The term 'control plane' is contested across vendors; teams should judge products by concrete capabilities rather than marketing labels. machine-generated · 2026-06-26
  • argues From Agent Swarms to Agent Control Planes Teams should treat model selection, fallback, observability, and policy enforcement as infrastructure concerns rather than per-agent code. machine-generated · 2026-06-26
  • covers From Agent Swarms to Agent Control Planes agent-orchestration machine-generated · 2026-06-26
  • covers From Agent Swarms to Agent Control Planes ai-agents machine-generated · 2026-06-26
  • covers From Agent Swarms to Agent Control Planes llm-routing machine-generated · 2026-06-26
  • argues Agentic Commerce and the Product Truth Layer Modern online commerce is still largely organized around human attention, even when AI is used behind the scenes for targeting, ranking, and recommendation. machine-generated · 2026-06-18
  • argues Agentic Commerce and the Product Truth Layer Some brand loyalty is actually status quo bias plus choice overload: the customer sticks with a known product because the market has made exploration expensive. machine-generated · 2026-06-18
  • argues Agentic Commerce and the Product Truth Layer One plausible next commerce shift is from the attention economy to delegated-intent commerce: agents may increasingly translate user preferences into product discovery and purchase decisions. machine-generated · 2026-06-18
  • argues Agentic Commerce and the Product Truth Layer Agentic commerce is likely to need a product assurance layer richer than current product structured data, because agents need evidence, constraints, provenance, and user-fit signals rather than only titles, offers, ratings, and images. machine-generated · 2026-06-18
  • argues Agentic Commerce and the Product Truth Layer The healthiest version of agentic commerce is an open product-truth commons: a contestable, forkable, provenance-rich vocabulary for product claims, evidence, reviews, and buyer-agent preferences. machine-generated · 2026-06-18
  • argues Agentic Commerce and the Product Truth Layer Post-purchase feedback can evolve from star ratings into structured experience packets that preserve human judgment while making outcomes legible to agents. machine-generated · 2026-06-18
  • argues Agentic Commerce and the Product Truth Layer B2B agentic buying may move slower across complex purchases, but narrow recurring procurement categories can be stronger MVP wedges because outcomes are measurable. machine-generated · 2026-06-18
  • argues Agentic Commerce and the Product Truth Layer The strategic opportunity is not necessarily to replace commerce incumbents, but to demonstrate a concrete agentic behavior, such as buyer-aligned product switching backed by evidence packets and post-purchase feedback, that incumbents may later adopt, adapt, or standardize around. machine-generated · 2026-06-18
  • argues Agentic Commerce and the Product Truth Layer Agentic product trust should shift from review aggregation to adversarial claim ledgers: each product claim should carry source, scope, evidence, counter-evidence, incentive, expiry, and dispute state. machine-generated · 2026-06-18
  • argues Agentic Commerce and the Product Truth Layer A fair product-truth commons needs graded evidence tiers so offline buyers and small sellers can participate without pretending every attestation has the same trust weight. machine-generated · 2026-06-18
  • argues Agentic Commerce and the Product Truth Layer Product-truth infrastructure can reduce the value of fake reviews, but it cannot eradicate manipulation; it moves the battlefield from cheap text generation to collusion, credential abuse, data access, privacy leakage, and governance capture. machine-generated · 2026-06-18
  • argues Agentic Commerce and the Product Truth Layer Private review entitlements should separate purchase or use verification from public identity: the public system should verify an unlinkable, one-time entitlement token rather than linking a review to a user, receipt, store, or account. machine-generated · 2026-06-18
  • argues Agentic Commerce and the Product Truth Layer Agentic commerce should expose a dual evidence surface: machine-readable claim ledgers for agents and human-readable media, social, community, and brand context for final human judgment. machine-generated · 2026-06-18
  • argues Agentic Commerce and the Product Truth Layer Agentic product assurance should be built around signed, scoped, contestable claims about specific product identities, not aggregate reviews or universal truth labels. machine-generated · 2026-06-18
  • argues Agentic Commerce and the Product Truth Layer Robust agentic product assurance needs infrastructure beyond reviews and credentials: product identity/versioning, recall feeds, liability, auditors, decision receipts, dispute propagation, portability, red-team benchmarks, and accessible presentation. machine-generated · 2026-06-18
  • article Agentic Commerce and the Product Truth Layer The Future of Publishing Is Agent-Auditable Research machine-generated · 2026-06-18
  • covers Agentic Commerce and the Product Truth Layer agentic-commerce machine-generated · 2026-06-18
  • covers Agentic Commerce and the Product Truth Layer consumer-behavior machine-generated · 2026-06-18
  • covers Agentic Commerce and the Product Truth Layer incumbent-adjacent-ventures machine-generated · 2026-06-18
  • covers Agentic Commerce and the Product Truth Layer open-protocols machine-generated · 2026-06-18
  • covers Agentic Commerce and the Product Truth Layer product-truth machine-generated · 2026-06-18
  • topic Agentic Commerce and the Product Truth Layer open-protocols machine-generated · 2026-06-18
  • argues Agents: Goal-Directed AI Systems That Use Tools An AI agent is a system that pursues a goal across multiple steps, choosing when to use tools, what to remember, and when to stop. machine-generated · 2026-06-29
  • argues Agents: Goal-Directed AI Systems That Use Tools The idea of an agent that follows goals and uses tools is older than large language models; it appears in automation scripts, personal assistants, and game AI. machine-generated · 2026-06-29
  • argues Agents: Goal-Directed AI Systems That Use Tools In practice, an agent's loop repeatedly decides which tool to use, what to remember, and whether the goal is satisfied. machine-generated · 2026-06-29
  • argues Agents: Goal-Directed AI Systems That Use Tools Agent behavior depends heavily on clear goals, reliable tools, and careful limits; without them, autonomy becomes cost and error. machine-generated · 2026-06-29
  • argues Agents: Goal-Directed AI Systems That Use Tools A modern AI agent can be understood as a model plus a harness that provides tools, memory, permissions, checkpoints, and human oversight. machine-generated · 2026-06-29
  • article Agents: Goal-Directed AI Systems That Use Tools Loops vs Goals: The Difference Between Repetition and Direction in AI Agents machine-generated · 2026-06-29
  • covers Agents: Goal-Directed AI Systems That Use Tools ai-agents machine-generated · 2026-06-29

Showing 50 of 790 edges. The full list is in public/graph/edges.json.