Decision Matrix

To aid in choosing the ideal level of AI assistance, this matrix relates key decision factors to the AI level that best suits your project's situation.

ATLAS Framework Decision Matrix

When selecting the appropriate level of AI assistance, evaluate your project against these key dimensions:

1. Security and Compliance Requirements

High

Prefer Levels 0-2 (Pure Code Forge to Specific Boost)

For defense, healthcare, financial systems

Moderate

Consider Levels 3-5 (Code Accelerator to Component Reactor)

For business applications with some sensitive data

Low

All levels possible, including 6-7 (Visual Symphony to Prompt-to-Product)

For internal tools, prototypes, non-sensitive applications

2. Project Complexity

High (Novel algorithms, unique architecture)

Prefer Levels 0-3 (Pure Code Forge to Code Accelerator)

When implementing custom algorithms or unique architectural patterns

Moderate (Common patterns with customization)

Consider Levels 2-5 (Specific Boost to Component Reactor)

For applications that follow standard patterns but require customization

Low (Standard application types)

Consider Levels 4-7 (Blueprint Amplifier to Prompt-to-Product)

For CRUD applications, dashboards, and standard web applications

3. Team AI Proficiency

Low

Start with Levels 0-2 (Pure Code Forge to Specific Boost)

For teams new to AI-assisted development

Moderate

Consider Levels 3-5 (Code Accelerator to Component Reactor)

For teams with some experience using AI tools

High

All levels possible, including 6-7 (Visual Symphony to Prompt-to-Product)

For teams experienced with AI tools and prompt engineering

4. Development Speed Priority

Low (Quality and precision paramount)

Prefer Levels 0-3 (Pure Code Forge to Code Accelerator)

When precision and quality are more important than speed

Moderate (Balanced approach)

Consider Levels 3-5 (Code Accelerator to Component Reactor)

When balancing quality and development speed

High (Rapid deployment critical)

Consider Levels 5-7 (Component Reactor to Prompt-to-Product)

When time-to-market is the primary concern

5. Long-term Maintenance Considerations

High (Long lifespan, ongoing development)

Prefer Levels 0-4 (Pure Code Forge to Blueprint Amplifier)

For systems expected to be maintained for many years

Moderate (Regular updates needed)

Consider Levels 2-6 (Specific Boost to Visual Symphony)

For applications requiring periodic updates and enhancements

Low (Short-term or disposable solution)

All levels possible, including 7 (Prompt-to-Product)

For prototypes, MVPs, or short-lived applications

Integration Across Multiple Levels

A project does not always fit neatly into a single AI level. Often, different parts of a system can benefit from varying degrees of automation and assistance.

Many projects can benefit from using different levels for different components:

  • Security-critical components: Levels 0-2
  • Business logic: Levels 3-5
  • Administrative interfaces: Levels 5-6
  • Prototyping new features: Level 7

Migration Considerations Between Levels

Transitioning between AI levels need not be permanent. Depending on project evolution or changing business needs, it may be necessary to move up or down to a level that better meets current requirements.

Lower → Higher

  • Plan for verification processes
  • Develop AI prompt engineering skills
  • Establish testing frameworks
  • Focus on requirements clarity

Higher → Lower

  • Expect productivity changes
  • Address knowledge transfer gaps
  • Focus on code documentation
  • Potentially refactor generated code