뇌는 4배를 저장합니다: AI에서 맥락이 누락된 기본 요소인 이유

Agents as Labor A Foundational Economics and Market Design Framework for the Agent Era Why Agent Markets Will Converge on Labor Market Structures And How to Build the Infrastructure That Wins Executive Summary The AI agent market is experiencing a fundamental pricing miscategorization. Current commercialization models treat agents as software (priced by tokens, seats, or API calls), yet agentic systems exhibit economic characteristics that map directly to labor markets: variable performance, quality heterogeneity, task-specific matching requirements, and outcome uncertainty. This category error leaves significant value on the table and creates misaligned incentives across the value chain. This document presents a first-principles framework demonstrating why agent markets will converge on labor market primitives. The analysis draws on Nobel Prize-winning economic theory (Akerlof on information asymmetry, Holmstrom on moral hazard, Rochet-Tirole on two-sided markets) and validates predictions against empirical market data from gig economy platforms, enterprise AI adoption surveys, and emerging outcome-based pricing models. Core Thesis: Agents satisfy four defining characteristics that distinguish labor from software: (1) variable performance across tasks and contexts, (2) matching requirements based on capability fit rather than availability, (3) compensation that should reflect value created rather than effort expended, and (4) accountability structures with consequences for failure. Organizations that recognize this structural reality and build the corresponding infrastructure (capability taxonomies, evaluation standards, reputation systems, outcome contracts) will capture the durable value in this market. 1. The Category Error: Why Current Pricing Models Fail 1.1 Software Economics: The Default Mental Model Software has traditionally exhibited specific economic characteristics that justify standard pricing models: Deterministic behavior: Given identical inputs, software produces identical outputs, enabling regression testing and quality guarantees Near-zero marginal cost: Once developed, each additional unit costs essentially nothing to produce Feature-based differentiation: Value is captured through capability lists and version tiers Uptime as the primary SLA: Availability, latency, and security define service quality These characteristics support per-seat, per-usage, and tiered subscription pricing. The SaaS model that Salesforce pioneered works because the relationship between payment and value is relatively stable: you pay for access to capabilities, and the software delivers those capabilities consistently. 1.2 Agent Economics: A Structural Departure Agentic systems break from software economics in ways that are not incremental but categorical. Analysis of agent behavior reveals four defining characteristics: Characteristic 1: Variable Performance Two implementations of “the same” agent can differ dramatically across tool competence, refusal patterns, hallucination rates, domain grounding, and edge case handling. This mirrors labor market dynamics: two accountants are not interchangeable despite holding identical credentials. Benchmark saturation (where multiple models score 90%+ on standard tests) obscures real-world performance variance that enterprises experience in production. Characteristic 2: Output Uncertainty Even with identical prompts, agents can vary due to stochastic decoding, tool latency, retrieval differences, and context drift. This is not a bug to be fixed; it is intrinsic to how these systems function. The implication is fundamental: you cannot treat agent outputs as deterministic deliverables. You must manage agents the way you manage workers, with oversight, performance measurement, and escalation paths. Characteristic 3: Asymmetric Failure Costs A 2% hallucination rate in marketing copy is tolerable. A 0.2% error rate in payroll, compliance, or hiring decisions can be existential. This drives the need for risk-tiered capabilities, compliance-aware routing, and contracts that incorporate downside exposure. Software SLAs built around uptime cannot capture this domain-specific risk asymmetry. Characteristic 4: Value at Resolution The critical distinction is that agents create value when they resolve outcomes, not when they run. A chatbot produces text. An agent changes state: files tickets, updates records, routes cases, reconciles data, triggers workflows, and escalates when needed. This is the economic signature of labor, not software. 1.3 Quantifying the Mismatch 2. Theoretical Foundations: Why Labor Economics Applies The argument that agent markets will converge on labor market structures is not speculative. It follows directly from established economic theory that has been validated across multiple domains. Three theoretical frameworks are particularly relevant. 2.1 Asymmetric Information and the Lemons Problem Theory: George Akerlof’s 1970 paper “The Market for ‘Lemons’“ demons