Orca GTT Method
GTT-Method
Governance Through Thinking
Back to home

The Approach

How GTT-Method establishes reliable development environments through explicit context governance.

Core Concept: Governed Context

GTT-Method addresses the problem by establishing governed context around AI-assisted software development.

Software Development + AI Coding Agents + Governed Context = Governance Through Thinking

What GTT-Method Does

Context Governance

Explicitly structure, maintain, protect and control project context so AI agents can use it reliably.

Architecture

Make architectural decisions and constraints explicit, protecting them from unintended agent-driven changes.

Specifications

Define clear requirements and expected behavior so agents work toward defined outcomes.

Rules & Constraints

Establish directives and restrictions that limit implementation options and preserve intent.

Traceability

Keep all changes reviewable through version control so decisions remain visible and auditable.

Drift Prevention

Detect and prevent architectural drift through mechanisms that validate governed context remains intact.

What GTT-Method Does NOT Attempt

GTT-Method does not attempt to make the AI "smarter".

Instead, GTT-Method establishes a more reliable development environment and context contract around the agent.

The goal is not to replace specifications, developers or AI agents. The goal is to make the context and architectural intent that guide AI agents explicit and governable.

Enforcement Philosophy

Put each concern in the plane that can enforce it.

PlaneMechanismGuarantee
Control PlanePermissions & hooksDeterministic
Build PlaneCI validationDeterministic
Instruction PlaneAgent rulesProbabilistic
Procedural PlaneSkills & workflowsOn demand

An instruction saying "AI must not modify architecture files" is useful, but remains an instruction. A filesystem permission, hook or CI gate provides actual enforcement.

GTT-Method combines instructional governance with deterministic controls wherever possible.