Research · preprint · 0.3
Defining the Boundaries Before Bringing AI Capability into an Engineering Organization
A position paper based on the author's experience driving AI infrastructure and pilots in a real engineering organization: it proposes four kinds of boundaries—context, responsibility, authorization, and measurement—and offers a falsifiable pilot protocol plus a minimal harness as a demonstration of putting them into practice.
- 1The Five Lenses: Connection-Oriented Problem LocationDeep research · 19 min read
- 2Data Measurement as Organizational Protocol: Definitions, Measurement, Tiering, and RetrospectivesDeep research · 11 min read
- 3Developer Productivity Is Not a Tool Catalog, but a Feedback SystemDeep research · 9 min read
- 4Defining the Boundaries Before Bringing AI Capability into an Engineering OrganizationDeep research · 9 min readThis chapter
- 5When AI Lowers Workflow Barriers: How to Redivide Functional Lines and Business LinesDeep research · 14 min read
- 6Decompose First, Then Schedule: A Review of Multi-Model Task Decomposition, Capability Switching, and Subtask RoutingDeep research · 13 min read
- 7Making an Agent a Collaborable Object: State, Feedback, and Result ConfirmationDeep research · 13 min read
- 8Let the Agent Execute: Emotional Adaptation, Trust Calibration, and Human Relief from Execution PressureDeep research · 13 min read
- 9The Laws of Human Motivation: The Situational Motivation ModelDeep research · 29 min read
- 10AI Does Not Automatically Create Productivity: From Local Acceleration to System ValueShort · 5 min read
Enjoy this site?