GTT-Method Position
GTT-Method operates at the intersection of multiple disciplines, providing governance for AI-assisted development.
AI-Assisted Software Development: SDD (Specifications) + Context Engineering + AI Coding Agents + Software Architecture = GTT-Method (Governed Context + Governance Layer)
GTT-Method vs SDD
Spec-Driven Development and GTT-Method answer different questions.
SDD
Question: What should be built? What behavior is required? Focus: Explicit specifications and expected outcomes.
GTT-Method
Question: How should the context govern AI development? What boundaries protect architecture? Focus: Governed context and agent governance.
Together
SDD defines WHAT to build. GTT-Method governs HOW an AI agent should operate while building it. They complement each other.
Not Replacement
GTT-Method does not replace SDD. You can use both methodologies in the same project effectively.
GTT-Method vs Context Engineering
Context Engineering is a broader discipline. GTT-Method applies it specifically to AI-assisted development.
Context Engineering
Broad discipline focusing on designing and supplying useful context to AI systems in general.
GTT-Method
Applies context engineering specifically to software development with AI agents, adding governance, architecture and protection patterns.
Relationship
GTT-Method is Context Engineering + Software Architecture + Governance + Protection Patterns applied to AI-assisted development.
Integration
GTT-Method uses context engineering principles but adds software development-specific governance mechanisms.
GTT-Method vs RAG
RAG and GTT-Method solve different problems at different layers.
RAG (Retrieval-Augmented Generation)
A retrieval technique for supplying relevant information to an AI system. Solves: "How do I give the AI better information?"
GTT-Method
A development methodology for governing AI-assisted software development. Solves: "How do I keep the architecture consistent while AI builds?"
Can Complement
GTT-Method can use RAG to retrieve context. But GTT-Method is not RAG. GTT-Method is governance; RAG is retrieval.
Different Concerns
RAG: Information retrieval. GTT-Method: Context governance, architectural intent, rules enforcement.
GTT-Method vs Prompt Engineering
Prompt engineering and GTT-Method operate at different levels of abstraction.
Prompt Engineering
Asks: "How should I phrase instructions so the AI understands them better?" Focus: Instruction quality and phrasing.
GTT-Method
Asks: "How should the development environment itself be structured so the AI behaves correctly?" Focus: Context governance and architectural protection.
Scope Difference
Prompt engineering: One interaction. GTT-Method: Entire development process across multiple sessions.
Relationship
GTT-Method is not "better prompt engineering". It's a different approach addressing structural governance vs. instruction phrasing.