This methodology research paper documents the development methodology through which a practitioner without formal training in software engineering or computer science produced two independently validated AI infrastructure systems in under two months using AI-assisted collaboration. The systems examined are Hydra-rray, a containerized behavioral observatory designed to study tool-capable AI models operating with real offensive security tools, and an Android MCP client, a fully offline mobile AI agent integrating local transformer inference, operating-system-level automation through Android AccessibilityService, and Model Context Protocol (MCP) orchestration within a single application package.Development occurred entirely under consumer-access constraints: commodity hardware, standard consumer model interfaces, no engineered system prompts, no prompt-engineering infrastructure, no model fine-tuning, and no custom datasets. Context continuity across stateless model sessions was maintained exclusively through machine-readable YAML context transport documents referred to as batons.Across the two case studies, six consistent methodological properties were observed: outcome-first design, cross-domain methodology replication, vanilla model utilization, machine-readable context as drift prevention, multi-model triangulation for drift detection, and socialized interaction as a mechanism for surfacing tacit knowledge.Within the Hydra-rray experimental environment, an additional behavioral observation emerged: across observed sessions within the Hydra-rray environment, operating under consumer-access constraints and without engineered prompt scaffolding, tool-capable models exhibited a binary execution pattern: either correct tool execution or complete hallucination, with no intermediate partial success states observed.The Android case study further demonstrates that local language-model inference and operating-system-level actuation can operate on consumer mobile hardware not designed for transformer workloads, including a Snapdragon 865 device running Android 13. Development of the Android system occurred independently and the project repository predates Google’s public AppFunctions announcement by one day, suggesting parallel discovery of a similar architectural gap.The paper argues that the primary contribution of these projects is not the systems themselves but the development methodology that produced them: a human-directed AI collaboration process in which the practitioner defines outcomes, evaluates architecture, and orchestrates the work while AI systems generate implementation artifacts. The paper itself is produced using the same methodology, serving as a recursive demonstration of the approach it documents.The methodology is examined through two case studies: Hydra-rray, a containerized behavioral observatory for tool-capable AI agents, and an offline Android MCP client integrating local model inference with mobile automation.