📋

Technical Details

Deep-dive into QUAD implementation: Agent patterns, flow docs, hierarchy rules

The 2 Dimensions: Business + Technical

Every circle operates along two axes: Business (understanding requirements, stakeholders, value) and Technical (code, systems, infrastructure). The B/T ratio defines each circle's focus.

B

Business Dimension

  • • Understanding stakeholder needs
  • • Translating requirements to specs
  • • Prioritization and value assessment
  • • User experience and workflows
  • • Communication with non-technical teams
T

Technical Dimension

  • • Writing and reviewing code
  • • System architecture decisions
  • • Database design and optimization
  • • Infrastructure and DevOps
  • • Performance and security

B/T Ratios by Circle

Management
B 80%
T 20%
Development
B 30%
T 70%
QA
B 30%
T 70%
Infrastructure
B 20%
T 80%

Shared vs Dedicated Resources

MORE DEDICATEDMORE SHARED
Management
Circle
Dedicated
per project
Development
Circle
Mostly Dedicated
can share
QA
Circle
Mostly Shared
across projects
Infrastructure
Circle
Always Shared
across directors

Organizational Structure

GROUP
(e.g., Wealth Management)
Director A
Project 1
Project 2
Director B
Project 1
Project 2
Director C
Project 1
Project 2
SHARED RESOURCES
Infrastructure Circle
ALWAYS SHARED
QA Circle
USUALLY SHARED
Enabling Teams
OPTIONAL

Hierarchy Rules

Level 1
BASE RULES
QUAD Platform - Universal do's and don'ts
Level 2
COMPANY-WIDE
Entity/Org level policies
Level 3
DIRECTOR
Program/Portfolio level
Level 4
TECH LEAD
Team level
Level 5
TEAM MEMBER
Personal preferences

Each level can ADD restrictions, never CONTRADICT upper levels

Example Rules

LevelExample Rule
Base Rules"Never commit secrets to Git"
Company-wide"All PRs require 2 reviewers"
Director"Use Java 21 only for this program"
Tech Lead"Follow our naming conventions"
Team Member"I prefer dark mode in IDE"

Agent Class-Object Pattern

CLASS (Template)

Story Agent (Template)
  • - Capabilities defined
  • - Base rules configured
  • - No connection yet
  • - "Ready" state
Cannot execute tasks

OBJECT (Instance)

Suman's Story Agent
  • - Connected to platform
  • - App password set
  • - Local machine context
  • - User-specific rules
Can execute tasks
→
assign + setup = object

Setup Flow

1
Agent Template exists
QUAD Platform
2
User joins team
Gets web access
3
App Password created
Restricted perms
4
Local machine setup
Agent installed
5
Agent = Object
Active!

Flow Document Template

# FLOW: [Feature Name]
## Overview
| Field | Value |
| Flow ID | FLOW_XXX_001 |
| Owner | Management Circle (BA/PM/TL) |
| Status | Draft / Active / Retired |
## Step 1: [Action Name]
### UI
| Element | Type | Validation |
### API
POST /api/endpoint
### Database
SELECT * FROM table
### Test Cases
| TC001 | Happy path | 200 |

QA Testing View (Auto-Generated)

Flow: FLOW_LOGIN_001
UI Tests:
Email field shows keyboard
Password field masks input
Login button disabled when empty
Error message displays on failure
API Tests:
POST /api/auth/login returns 200
Returns 401 with invalid password
Returns 422 with malformed email
Database Tests:
users.last_login_at updated
device_login_history row created
login_attempts incremented on failure
Edge Cases:
SQL injection attempt blocked
Account lockout after 5 failures

One Source of Truth Architecture

GIT REPOSITORY
(Version Controlled)
/docs/flows/
/src/code
/tests/specs
↓
QUAD WEB APP
Flow viewer, API browser, DB schema, AI chat (RAG), Test dashboard
↓
Confluence (sync)
Jira (sync)
Swagger (auto)

All tools sync FROM Git (single source). Never edit in Confluence directly.

QUAD™ - Circle of Functions | A methodology by A2 Vibe Creators | First Published: December 2025