{
  "author": {
    "id": "person:tony-malott",
    "name": "Tony Malott",
    "url": "https://malott.ai/"
  },
  "canonicalWorkId": "work:the-bottleneck-moved",
  "classification": {
    "publicSafe": true,
    "workType": "shareplane-thesis"
  },
  "discovery": {
    "abstract": "Software engineering was built around the assumption that implementation was scarce. It isn’t anymore.",
    "card": {
      "kicker": "SharePlane Thesis",
      "orientation": "As implementation gets cheaper, rigor migrates upward.",
      "visual_motif": "the-bottleneck-moved"
    },
    "format": {
      "depth": "Complete Work",
      "interaction": "Seven-image infographic gallery",
      "label": "SharePlane Thesis"
    },
    "kind": "SharePlane Thesis",
    "thesis": "Software engineering was organized around implementation scarcity. As implementation becomes abundant, value migrates upward toward judgment, context, verification, authority, and systems thinking.",
    "topics": [
      "AI-native software engineering",
      "organizational design",
      "systems architecture",
      "autonomy",
      "knowledge systems"
    ]
  },
  "evidence": [
    {
      "caveat": "Survey-based organizational research does not prove the article’s broader forecast about team size or role displacement.",
      "id": "source:dora-2025",
      "locator": "https://dora.dev/research/2025/dora-report/",
      "role": "DORA characterizes AI as an amplifier of an organization’s existing strengths and weaknesses, with the largest returns coming from the underlying organizational system rather than the tool alone.",
      "title": "DORA 2025: State of AI-assisted Software Development",
      "type": "Independent industry research"
    },
    {
      "caveat": "Observed tradeoffs across organizations are not a universal causal law.",
      "id": "source:dora-2026-tensions",
      "locator": "https://dora.dev/insights/balancing-ai-tensions/",
      "role": "DORA reports that AI accelerates initial code generation while time savings are often reallocated to auditing and verification; higher AI adoption is associated with greater throughput and greater instability.",
      "title": "DORA: Balancing AI tensions",
      "type": "Independent industry research"
    },
    {
      "caveat": "METR warns against generalizing the result to most development, and the tested tools reflect early-2025 capabilities.",
      "id": "source:metr-2025-rct",
      "locator": "https://metr.org/blog/2025-07-10-early-2025-ai-experienced-os-dev-study/",
      "role": "In a randomized trial of 16 experienced developers completing 246 tasks in mature repositories, early-2025 AI tools increased completion time by 19 percent.",
      "title": "METR: Early-2025 AI and experienced open-source developers",
      "type": "Counterevidence / randomized trial"
    },
    {
      "caveat": "The follow-up does not establish a reliable universal speedup estimate.",
      "id": "source:metr-2026-update",
      "locator": "https://metr.org/blog/2026-02-24-uplift-update/",
      "role": "METR says it is likely developers were more accelerated by AI in early 2026 than in early 2025, but calls the magnitude weakly evidenced because of selection effects.",
      "title": "METR: Developer productivity experiment design update",
      "type": "Capability-change evidence"
    },
    {
      "caveat": "This is a measurement framework, not direct proof of the article’s role-compression thesis.",
      "id": "source:metr-2026-task-substitution",
      "locator": "https://metr.org/blog/2026-05-08-task-substitution-and-uplift/",
      "role": "METR argues that AI productivity depends partly on which tasks people choose once AI is available, so speed on old tasks and value from new tasks are not the same measure.",
      "title": "METR: Task Substitution and Uplift",
      "type": "Measurement nuance"
    },
    {
      "caveat": "Vendor engineering guidance is experience-based and not an independent productivity study.",
      "id": "source:anthropic-context",
      "locator": "https://www.anthropic.com/engineering/effective-context-engineering-for-ai-agents",
      "role": "Anthropic frames context as a critical finite resource and context engineering as curating the high-signal state, tools, and information required for effective long-horizon agents.",
      "title": "Anthropic: Effective context engineering for AI agents",
      "type": "Primary technical guidance"
    },
    {
      "caveat": "Supports system architecture claims, not the employment implications of the thesis.",
      "id": "source:anthropic-tools",
      "locator": "https://www.anthropic.com/engineering/writing-tools-for-agents",
      "role": "Anthropic argues that agent effectiveness depends strongly on tool design, meaningful returned context, evaluations, and clear functionality boundaries.",
      "title": "Anthropic: Writing effective tools for agents",
      "type": "Primary technical guidance"
    },
    {
      "caveat": "Provider evidence does not independently validate productivity or labor-market predictions.",
      "id": "source:openai-agents-api-2026",
      "locator": "https://openai.com/index/introducing-the-agents-api/",
      "role": "OpenAI says useful long-running agents need a harness that manages context, tools, and subagents, plus persistent environments where agents can work with files, run code, and save intermediate results.",
      "title": "OpenAI: Introducing the Agents API",
      "type": "Primary platform evidence"
    },
    {
      "caveat": "NIST provides a voluntary risk framework, not a prescriptive architecture for autonomous software engineering.",
      "id": "source:nist-ai-rmf",
      "locator": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/",
      "role": "NIST calls for testing before deployment and during operation, rigorous performance assessment, documented measurement, independent review, and risk-response controls.",
      "title": "NIST AI RMF Core: Measure and Manage",
      "type": "Standards / risk framework"
    }
  ],
  "lineage": {
    "relationship": "successor-version-of-same-work",
    "predecessorReleaseRunId": 38008560312
  },
  "provenance": {
    "frozenSourceManifestSha256": "346fe482e942501463ce8aeb54f0411407ae69a1c31c3ff82e9bbefd332328de",
    "frozenSourceZipSha256": "f4dcdb7e24cc671fcde257dd7010770deed9835c6026be713bc3db92be433cdd",
    "governingIssue": 1403,
    "sourcePortableWorkSha256": "d3f864cad9ee386530fdd7f3494acaee0cc94e1142146d58adc0cb72c5fbb07d",
    "acceptedUatRequestId": "ouat-1450-dadf56c3d10474b0e6270bdb",
    "acceptedUatSourceHead": "1f5a50f4a0800f6fc57701c4fa6c48079bba2d1d",
    "protectedReaderSha256": "63104930433c77a1c36fcd4ac101db95fa9f448428dfe314c2867f13ac5553ef",
    "originalSourceZipSha256": "f4dcdb7e24cc671fcde257dd7010770deed9835c6026be713bc3db92be433cdd"
  },
  "relationships": [],
  "schemaVersion": "shareplane.work-portable-view.v1",
  "sourceRelationshipDecisions": {
    "decisions": "relationship-graph.json",
    "standing": "source-declared-pending-public-v3-readers"
  },
  "subtitle": "Software engineering was built around the assumption that implementation was scarce. It isn’t anymore.",
  "title": "The Bottleneck Moved",
  "workId": "artifact:the-bottleneck-moved"
}
