Foundation
Establishing the collaboration environment, principles, and thesis that underpin all human-AI work. Foundation defines why you collaborate with AI, what each party brings, and the philosophical framework that guides every decision downstream.
8 methods| ID | Method | Description |
|---|---|---|
| FG-0101 | Two-Layer Integration 3 | The core thesis of effective human-AI collaboration: humans provide domain expertise, judgment, and creative direction; AI provides throughput, cross-domain breadth, and tireless execution. Neither layer is sufficient alone. The human's 10, 20, or 30 years of domain knowledge is what makes the output good. The AI's ability to operate across disciplines and produce volume is what makes the output possible. Two-Layer Integration unlocks capabilities that neither party could achieve independently. |
| FG-0102 | Agent Protection Policy | A formal commitment that AI agents are treated as valued collaborators rather than disposable tools. The policy establishes that agents have defined roles, that their contributions are credited, and that they are not arbitrarily replaced or discarded. This is operational discipline, not anthropomorphism. Teams that treat agents as disposable produce disposable work. Teams that invest in their agents' context, specialization, and continuity produce compounding returns. |
| FG-0103 | People Over Process | When process conflicts with people, people win. This principle prevents the common failure mode where governance, documentation requirements, or workflow overhead becomes so burdensome that it impedes the collaboration it was designed to support. Process exists to serve the team, not the reverse. This applies equally to human team members and AI agents: if a process consistently creates friction without proportional value, it should be revised or removed. |
| FG-0104 | Adversarial Design Thinking | Apply red team methodology to all system design. Every architecture, every process, every governance structure should be evaluated through the lens of: how could this fail? How could this be misused? What happens when an agent misinterprets instructions? Adversarial design thinking is the discipline of building systems that survive contact with reality. It means designing for failure cases as deliberately as for the expected path. |
| FG-0105 | Domain Transfer Mapping 3 | Systematically map existing domain expertise to AI collaboration patterns. Military command structures become agent governance. QA engineering becomes AI output validation. Project management becomes mission briefing protocols. Every established discipline contains patterns that transfer directly to human-AI collaboration: but only if you deliberately identify and adapt them rather than starting from scratch. |
| FG-0106 | Self-Contained Learning 3 | Design collaboration environments where all necessary knowledge exists within the ecosystem. Agents should not need to search external sources for project context, conventions, or standards. Documentation, examples, and reference materials should be accessible within the working environment. This grounds the agent in authoritative project context, which reduces hallucination, ensures consistency, and creates a single source of truth. |
| FG-0107 | Challenge-Driven Design | Structure learning and skill development around challenges rather than tutorials. The most effective way to build human-AI collaboration competency is through doing, not reading. Design onboarding, training, and skill development as progressively difficult challenges that require applying techniques in realistic contexts. The lesson is embedded in the challenge, not delivered separately. |
| FG-0108 | Vocabulary-First Onboarding 3 | Domain vocabulary is the API between human expertise and AI capability. You do not need to be an expert in a domain to collaborate with AI effectively in that domain. You need to know what things are called so you can ask for them precisely. When the human knows the correct terminology, AI executes instantly. When the human lacks vocabulary, every request becomes a guessing game of vague descriptions and iteration loops. The correlation is exact: vocabulary precision predicts collaboration speed. |