# MYINFO v1.2 — MASTER EXECUTION INDEX

**Purpose:** Multi-agent execution map for Claude Code  
**Source of Truth:** `MYINFO_BLUEPRINT_FINAL_v1.2.md`  
**Task Catalog:** `MYINFO_PROJECT_TASKS_v1.2.md`  
**Execution Principle:** Dependency-safe, review-gated, no architectural drift

---

# 1. AGENT ROLES

## ARCHITECT

Responsibilities:

```text
Architecture decisions
Dependency validation
Schema impact review
API contract consistency
Security boundary review
Cross-module integration rules
Final approval for architectural changes
```

Architect does NOT casually implement feature code unless explicitly assigned.

---

## BACKEND-DEVELOPER

Responsibilities:

```text
PHP backend
MySQL access layer
REST API
Authentication backend
Admin Dashboard backend
Wablas
Google backend verification
Sync backend
Publish/rollback
Audit
Rate limiting
Remote config
```

---

## COMMERCIAL-API-DEVELOPER

Responsibilities:

```text
Commercial API namespace
API Client management
API key lifecycle
Plans & scopes
Quota/rate limit
Paid Wilayah/Bank read APIs
Partner submit APIs
Usage metering
Billing foundation
Shared-hosting usage aggregation
```

This agent does not implement Android authentication and does not reuse APK user tokens as Commercial API credentials.

---

## ANDROID-DEVELOPER

Responsibilities:

```text
Android Native Kotlin
Navigation
Room
Encrypted local DB
Auth client
Wilayah UI
Bank UI
Maps
Nearby
Sync client
Offline mode
App version enforcement
```

---

## FRONTEND-UIUX

Responsibilities:

```text
Bootstrap 5 Admin UI
Android screen UX guidance
Component consistency
Responsive Admin layout
State/error/loading design
Accessibility
Copy/labels
```

This agent may prepare UI implementation instructions, but Android code remains owned by ANDROID-DEVELOPER unless explicitly reassigned.

---

## REVIEWER

Responsibilities:

```text
Code review
Security review
Acceptance Criteria validation
Regression checks
Blueprint compliance
Task completion verification
Architectural drift detection
```

Reviewer does not rewrite production code unless explicitly asked.

---

# 2. GOLDEN RULE

Before any task starts:

```text
READ:
1. MYINFO_BLUEPRINT_FINAL_v1.2.md
2. MYINFO_PROJECT_TASKS_v1.2.md
3. This execution index
```

If a task conflicts with Blueprint:

```text
STOP
→ report conflict
→ Architect decides
```

Do not silently reinterpret requirements.

---

# 3. EXECUTION PHASE MAP

High-level sequence:

```text
PHASE A  Foundation
PHASE B  Admin/Auth Foundation
PHASE C  Remote Config
PHASE D  User Authentication
PHASE E  Wilayah Backend
PHASE F  Bank Backend
PHASE G  Admin Data Workflow
PHASE H  CSV / Audit / Release / Sync
PHASE I  Android Foundation
PHASE J  Android Auth
PHASE K  Android Local Data
PHASE L  Android Wilayah
PHASE M  Android Bank
PHASE N  Android Nearby / Maps
PHASE O  Android Sync / Offline
PHASE P  Security Hardening
PHASE Q  QA
PHASE R  Release
```

---

# 4. MASTER OWNERSHIP TABLE

| PT | Task | Primary Owner | Reviewer | Parallel Safe |
|---|---|---|---|---|
| PT-001 | Repository Bootstrap | ARCHITECT | REVIEWER | No |
| PT-002 | Backend Environment & DB Connection | BACKEND | REVIEWER | Yes after PT-001 |
| PT-003 | Existing DB Schema Inspector | BACKEND | ARCHITECT | No |
| PT-004 | System Tables Migration Plan | ARCHITECT + BACKEND | REVIEWER | No |
| PT-005 | API v1 Skeleton | BACKEND | REVIEWER | Yes |
| PT-006 | Admin Dashboard Shell | FRONTEND-UIUX + BACKEND | REVIEWER | Yes |
| PT-007 | Admin Authentication | BACKEND | REVIEWER | No |
| PT-008 | Admin Role Authorization | BACKEND | REVIEWER | No |
| PT-009 | Admin Session & Re-auth | BACKEND | REVIEWER | Yes |
| PT-010 | Settings Storage | BACKEND | ARCHITECT | Yes |
| PT-011 | Remote Config API | BACKEND | REVIEWER | No |
| PT-012 | App Control UI | FRONTEND-UIUX + BACKEND | REVIEWER | Yes |
| PT-013 | User Account Core | BACKEND | REVIEWER | No |
| PT-014 | Email Login API | BACKEND | REVIEWER | Yes |
| PT-015 | Access/Refresh Tokens | BACKEND | REVIEWER | No |
| PT-016 | Device Session API | BACKEND | REVIEWER | Yes |
| PT-017 | Password Change Revocation | BACKEND | REVIEWER | Yes |
| PT-018 | Wablas OTP | BACKEND | REVIEWER | Yes |
| PT-019 | Google Login Backend | BACKEND | REVIEWER | Yes |
| PT-020 | Account Linking | ARCHITECT + BACKEND | REVIEWER | No |
| PT-021 | Login Audit Log | BACKEND | REVIEWER | Yes |
| PT-022 | Wilayah Repository Adapter | BACKEND | ARCHITECT | No |
| PT-023 | Wilayah Hierarchy API | BACKEND | REVIEWER | Yes |
| PT-024 | Wilayah Search API | BACKEND | REVIEWER | Yes |
| PT-025 | Bank Repository Adapter | BACKEND | ARCHITECT | No |
| PT-026 | Bank & Branch API | BACKEND | REVIEWER | Yes |
| PT-027 | Lat/Lng Schema Migration | ARCHITECT + BACKEND | REVIEWER | No |
| PT-028 | Plus Code Decoder | BACKEND | REVIEWER | Yes |
| PT-029 | Short Plus Code Fallback | BACKEND | REVIEWER | Yes |
| PT-030 | Update Lat/Lng Button | BACKEND + FRONTEND-UIUX | REVIEWER | No |
| PT-031 | Admin Map Preview | FRONTEND-UIUX + BACKEND | REVIEWER | Yes |
| PT-032 | Bulk Missing Lat/Lng | BACKEND | REVIEWER | Yes |
| PT-033 | Nearby Query Service | BACKEND | REVIEWER | Yes |
| PT-034 | Change Request Engine | ARCHITECT + BACKEND | REVIEWER | No |
| PT-035 | Wilayah Admin CRUD Draft | BACKEND + FRONTEND-UIUX | REVIEWER | Yes |
| PT-036 | Bank Admin CRUD Draft | BACKEND + FRONTEND-UIUX | REVIEWER | Yes |
| PT-037 | Review Queue | BACKEND + FRONTEND-UIUX | REVIEWER | No |
| PT-038 | Publish Engine | ARCHITECT + BACKEND | REVIEWER | No |
| PT-039 | CSV Upload Parser | BACKEND | REVIEWER | Yes |
| PT-040 | CSV Validation Compare | BACKEND | REVIEWER | No |
| PT-041 | CSV Preview UI | FRONTEND-UIUX + BACKEND | REVIEWER | Yes |
| PT-042 | Commit CSV to Draft | BACKEND | REVIEWER | No |
| PT-043 | Admin Audit Log | BACKEND | REVIEWER | Yes |
| PT-044 | Audit Log UI | FRONTEND-UIUX + BACKEND | REVIEWER | Yes |
| PT-045 | Module Release Versioning | ARCHITECT + BACKEND | REVIEWER | No |
| PT-046 | Rollback Engine | ARCHITECT + BACKEND | REVIEWER | No |
| PT-047 | Sync Change Log | BACKEND | ARCHITECT | No |
| PT-048 | Sync Status API | BACKEND | REVIEWER | Yes |
| PT-049 | Incremental Sync API | BACKEND | REVIEWER | No |
| PT-050 | Snapshot Builder | BACKEND | REVIEWER | No |
| PT-051 | Snapshot Sync API | BACKEND | REVIEWER | Yes |
| PT-052 | Android Bootstrap | ANDROID | ARCHITECT | No |
| PT-053 | Android Theme | ANDROID + FRONTEND-UIUX | REVIEWER | Yes |
| PT-054 | Android Navigation Shell | ANDROID | REVIEWER | Yes |
| PT-055 | Android Remote Config | ANDROID | REVIEWER | No |
| PT-056 | Secure Token Storage | ANDROID | REVIEWER | Yes |
| PT-057 | Android Email Login | ANDROID | REVIEWER | Yes |
| PT-058 | Android WhatsApp Login | ANDROID | REVIEWER | Yes |
| PT-059 | Android Google Login | ANDROID | REVIEWER | Yes |
| PT-060 | Android Auth Routing | ANDROID | REVIEWER | No |
| PT-061 | Android Device Management | ANDROID | REVIEWER | Yes |
| PT-062 | Encrypted Room Foundation | ANDROID | ARCHITECT | No |
| PT-063 | Bundled Snapshot Import | ANDROID | REVIEWER | No |
| PT-064 | Wilayah Local Repository | ANDROID | REVIEWER | No |
| PT-065 | Wilayah Landing | ANDROID + FRONTEND-UIUX | REVIEWER | Yes |
| PT-066 | Wilayah Realtime Search | ANDROID | REVIEWER | Yes |
| PT-067 | Wilayah Browse | ANDROID | REVIEWER | Yes |
| PT-068 | Wilayah Detail | ANDROID + FRONTEND-UIUX | REVIEWER | Yes |
| PT-069 | Bank Local Repository | ANDROID | REVIEWER | No |
| PT-070 | Bank Landing | ANDROID + FRONTEND-UIUX | REVIEWER | Yes |
| PT-071 | Bank Search & Filters | ANDROID | REVIEWER | Yes |
| PT-072 | Branch Detail + Map | ANDROID + FRONTEND-UIUX | REVIEWER | No |
| PT-073 | Favorite Local | ANDROID | REVIEWER | Yes |
| PT-074 | Search History Local | ANDROID | REVIEWER | Yes |
| PT-075 | Location Permission Flow | ANDROID + FRONTEND-UIUX | REVIEWER | No |
| PT-076 | Nearby Distance Engine | ANDROID | REVIEWER | No |
| PT-077 | Nearby Map + List | ANDROID + FRONTEND-UIUX | REVIEWER | No |
| PT-078 | Android Sync Metadata | ANDROID | REVIEWER | Yes |
| PT-079 | Incremental Sync Client | ANDROID | REVIEWER | No |
| PT-080 | Snapshot Replacement Client | ANDROID | REVIEWER | No |
| PT-081 | Silent Background Sync | ANDROID | REVIEWER | No |
| PT-082 | App Version Enforcement | ANDROID | REVIEWER | Yes |
| PT-083 | Maintenance Screen | ANDROID + FRONTEND-UIUX | REVIEWER | Yes |
| PT-084 | Offline Mode | ANDROID | REVIEWER | No |
| PT-085 | Dashboard Statistics | BACKEND + FRONTEND-UIUX | REVIEWER | Yes |
| PT-086 | Android User Management UI | BACKEND + FRONTEND-UIUX | REVIEWER | Yes |
| PT-087 | API Rate Limiting | BACKEND | REVIEWER | Yes |
| PT-088 | HTTPS Enforcement | BACKEND + ANDROID | REVIEWER | No |
| PT-089 | Secrets Audit | REVIEWER | ARCHITECT | No |
| PT-090 | Permission Audit | REVIEWER | ARCHITECT | No |
| PT-091 | Backend Tests | BACKEND | REVIEWER | No |
| PT-092 | Android Tests | ANDROID | REVIEWER | No |
| PT-093 | Auth E2E QA | REVIEWER | ARCHITECT | No |
| PT-094 | Data E2E QA | REVIEWER | ARCHITECT | No |
| PT-095 | Offline Recovery QA | REVIEWER | ARCHITECT | No |
| PT-096 | Publish/Rollback QA | REVIEWER | ARCHITECT | No |
| PT-097 | Staging Deployment | BACKEND + ANDROID | REVIEWER | No |
| PT-098 | Production Preparation | ARCHITECT + BACKEND | REVIEWER | No |
| PT-099 | Play Release Preparation | ANDROID + FRONTEND-UIUX | REVIEWER | No |
| PT-100 | Production Release | ARCHITECT | REVIEWER | No |
| PT-101 | Commercial API Foundation | COMMERCIAL-API | ARCHITECT + REVIEWER | No |
| PT-102 | API Client Management | COMMERCIAL-API + FRONTEND-UIUX | REVIEWER | Yes |
| PT-103 | API Key Generator | COMMERCIAL-API | REVIEWER | No |
| PT-104 | Plans, Scopes, Quota & Rate Limit | COMMERCIAL-API | ARCHITECT + REVIEWER | No |
| PT-105 | Commercial Wilayah Read API | COMMERCIAL-API | REVIEWER | Yes |
| PT-106 | Commercial Bank Read API | COMMERCIAL-API | REVIEWER | Yes |
| PT-107 | Commercial Submit API | COMMERCIAL-API + BACKEND | ARCHITECT + REVIEWER | No |
| PT-108 | Usage Logging & Aggregation | COMMERCIAL-API | REVIEWER | Yes |
| PT-109 | Commercial API Dashboard | COMMERCIAL-API + FRONTEND-UIUX | REVIEWER | Yes |
| PT-110 | Billing Foundation | COMMERCIAL-API | REVIEWER | Yes |
| PT-111 | Shared Hosting Cron & Operations | BACKEND + COMMERCIAL-API | REVIEWER | No |

---

# 5. CRITICAL PATH

Tasks that MUST NOT be skipped:

```text
PT-001
→ PT-002
→ PT-003
→ PT-004
→ PT-005
→ PT-013
→ PT-015
→ PT-022
→ PT-025
→ PT-034
→ PT-045
→ PT-047
→ PT-048
→ PT-049
→ PT-050
→ PT-052
→ PT-055
→ PT-062
→ PT-063
→ PT-079
→ PT-080
→ PT-081
→ PT-091..096
→ PT-097
→ PT-098
→ PT-099
→ PT-100
```

If any critical-path task is incomplete, later release phases must not be considered stable.

---

# 6. SAFE PARALLELIZATION WAVES

## WAVE 1

After PT-001:

```text
BACKEND:
PT-002
PT-005

UIUX:
PT-006

ANDROID:
PT-052
```

Do NOT start DB-dependent feature work before PT-003.

---

## WAVE 2

After PT-003 + PT-004:

```text
BACKEND:
PT-007
PT-010
PT-013
PT-022
PT-025

ANDROID:
PT-053
PT-054
PT-062

UIUX:
Admin components
Android visual guidance
```

---

## WAVE 3

After auth foundations:

```text
BACKEND:
PT-014
PT-015
PT-018
PT-019
PT-021

ANDROID:
PT-055
PT-056
```

Account linking PT-020 waits until login providers exist.

---

## WAVE 4

Data backend parallel:

```text
Wilayah:
PT-023
PT-024

Bank:
PT-026
PT-027
PT-028
PT-029
PT-033
```

Admin map UI waits for PT-028/PT-029.

---

## WAVE 5

Admin data workflow:

```text
PT-034
→ PT-035 / PT-036
→ PT-037
→ PT-038
```

CSV can partially proceed in parallel:

```text
PT-039
→ PT-040
→ PT-041
→ PT-042
```

---

## WAVE 6

Release/sync backend:

```text
PT-043
PT-045
→ PT-047
→ PT-048
→ PT-049
→ PT-050
→ PT-051
```

Rollback PT-046 waits for release model PT-045.

---

## WAVE 7

Android auth:

```text
PT-057
PT-058
PT-059
→ PT-060
```

Device UI PT-061 can follow PT-016.

---

## WAVE 8

Android modules:

Wilayah:

```text
PT-064
→ PT-065
→ PT-066
→ PT-067
→ PT-068
```

Bank:

```text
PT-069
→ PT-070
→ PT-071
→ PT-072
```

Favorite/history can proceed once PT-062 exists:

```text
PT-073
PT-074
```

---

## WAVE 9

Nearby:

```text
PT-075
→ PT-076
→ PT-077
```

Do not implement Nearby before branch coordinate strategy is confirmed.

---

## WAVE 10

Android sync:

```text
PT-078
→ PT-079
→ PT-080
→ PT-081
```

---

## WAVE 11

Hardening:

```text
PT-082
PT-083
PT-084
PT-087
PT-088
PT-089
PT-090
```

---

## WAVE 12

QA:

```text
PT-091
PT-092
→ PT-093
PT-094
PT-095
PT-096
```

---

## WAVE 13

Release:

```text
PT-097
→ PT-098
→ PT-099
→ PT-100
```

---

---

## WAVE 14 — COMMERCIAL API

Commercial API is separate from the Android auth track and may proceed after shared foundations are stable.

```text
PT-101
→ PT-102
→ PT-103
→ PT-104
```

Then:

```text
PT-105
PT-106
PT-108
```

Partner submission:

```text
PT-107
```

requires the Admin Change Request workflow to already be stable.

Operations/UI:

```text
PT-109
PT-110
PT-111
```

Commercial API work must never block APK login or count APK traffic toward commercial quota.


# 7. ARCHITECT GATES

The Architect must explicitly approve these gates before proceeding.

## GATE A — Existing DB Confirmed

Requires:

```text
PT-003 complete
```

Architect checks:

```text
Actual table names
Actual keys
Actual indexes
Latitude/Longitude presence
MySQL version
Collation
Any schema mismatch
```

---

## GATE B — System Schema Approved

Requires:

```text
PT-004 complete
```

No system migration is applied before this approval.

---

## GATE C — Auth Model Approved

Requires:

```text
PT-013
PT-015
PT-018
PT-019
PT-020
```

Verify:

```text
One UserID
Multiple auth providers
Max 3 devices
Phone verification
No auto-merge conflicts
```

---

## GATE D — Data Model Integration Approved

Requires:

```text
PT-022
PT-025
PT-027
```

Verify:

```text
Bank uses Wilayah
Postal code not duplicated unnecessarily
Code fields remain VARCHAR
Existing database preserved
```

---

## GATE E — Admin Publishing Architecture Approved

Requires:

```text
PT-034
PT-037
PT-038
PT-043
PT-045
```

Verify:

```text
No direct editor write
Review required
Audit exists
Versioning forward-only
```

---

## GATE F — Sync Protocol Approved

Requires:

```text
PT-047
PT-048
PT-049
PT-050
PT-051
```

Verify:

```text
Incremental
Tombstone
Snapshot
Per-module version
Checksum
Recovery
```

---

## GATE G — Android Offline Architecture Approved

Requires:

```text
PT-062
PT-063
PT-078
```

Verify:

```text
Encrypted DB
Bundled initial data
Independent module versions
Token storage separate
```

---

## GATE H — Release Candidate Approved

Requires:

```text
PT-091 through PT-096
```

No production release before all critical QA passes.

---


### GATE I — Commercial API Boundary Approved

Requires:

```text
PT-101
PT-103
PT-104
PT-107
```

Verify:

```text
APK user identity is separate from API Client identity
APK bearer token cannot authenticate Commercial API
Commercial API key cannot authenticate App API
raw API keys are not stored
scope/quota/rate controls are enforced
submit endpoints cannot direct-write production
shared-hosting implementation has no mandatory daemon dependency
```


# 8. REVIEWER CHECKLIST PER PT

Reviewer must verify:

```text
[ ] Goal satisfied
[ ] Scope not expanded unnecessarily
[ ] Depends On satisfied
[ ] Blueprint respected
[ ] No unrelated files rewritten
[ ] No secrets introduced
[ ] Error handling present
[ ] Security impact considered
[ ] Tests executed
[ ] Acceptance Criteria met
[ ] Definition of Done met
```

Reviewer response format:

```text
REVIEW RESULT: PASS / CHANGES REQUIRED

FINDINGS:
1.
2.

SECURITY:
...

REGRESSION RISK:
...

BLUEPRINT COMPLIANCE:
...

APPROVAL:
YES / NO
```

---

# 9. HANDOFF FORMAT BETWEEN AGENTS

Every agent handoff MUST include:

```text
PT:
OWNER:
STATUS:

IMPLEMENTED:
- ...

FILES CHANGED:
- ...

NEW CONTRACTS:
- API:
- DB:
- UI:
- CONFIG:

ASSUMPTIONS:
- ...

OPEN ISSUES:
- ...

NEXT DEPENDENT TASKS:
- ...

REVIEW REQUIRED:
YES
```

No agent should rely only on chat history for important implementation state.

---

# 10. FILE OWNERSHIP GUIDANCE

To reduce collisions:

## Backend Agent Primary

```text
backend/src/
backend/migrations/
backend/config/
backend/scripts/
```

## Admin/UI Primary

```text
backend/admin/
backend/public/assets/css/
backend/public/assets/js/
```

Backend may edit Admin files only where server wiring is needed.

## Android Agent Primary

```text
android/
```

## Architect Primary

```text
docs/
architecture decision records
migration design
API contract governance
```

## Reviewer

Read-all, modify-none by default.

---

# 11. CONFLICT RULE

If two agents need the same file:

```text
1. Earlier dependency owner completes first.
2. Commit/checkpoint.
3. Next agent rebases/reads current file.
4. Never independently rewrite same file in parallel.
```

Especially protect:

```text
backend/public/index.php
backend/config/*
Android navigation root
Room database definition
Remote config models
Admin main layout
```

---

# 12. TASK STATUS STANDARD

Allowed status:

```text
TODO
READY
IN_PROGRESS
BLOCKED
IN_REVIEW
CHANGES_REQUIRED
DONE
```

Recommended tracker entry:

```text
PT-028
Status: IN_REVIEW
Owner: backend-developer
Reviewer: reviewer
Blocked by: none
Blocks: PT-030, PT-032
```

---

# 13. CLAUDE CODE ORCHESTRATION MODEL

Recommended project-level orchestrator behavior:

```text
PROJECT MANAGER / ARCHITECT
        |
        +-- architect
        |
        +-- backend-developer
        |
        +-- commercial-api-developer
        |
        +-- android-developer
        |
        +-- frontend-uiux
        |
        +-- reviewer
```

The orchestrator should:

```text
Read current PT
Check dependency
Assign owner
Wait for implementation result
Send to Reviewer
If PASS:
  mark DONE
  unlock dependent PT
If CHANGES_REQUIRED:
  return to same owner
```

---

# 14. DO NOT AUTO-DELEGATE ARCHITECTURAL DECISIONS

The following require Architect decision:

```text
Changing master table design
Merging App API and Commercial API identity/auth
Changing Commercial API credential model
Adding new authentication provider
Changing auth merge rules
Changing sync version strategy
Changing release semantics
Replacing encrypted Room approach
Changing Plus Code strategy
Adding background location
Changing permissions
Adding global search
Merging Bank and Wilayah modules
Changing Draft/Review/Publish workflow
```

Implementation agents must not decide these silently.

---

# 15. FIRST EXECUTION SEQUENCE

Recommended first real coding sequence:

```text
STEP 1
PT-001 Repository Bootstrap

STEP 2
PT-002 DB Connection Abstraction

STEP 3
PT-003 Existing DB Schema Inspector

STOP
ARCHITECT GATE A

STEP 4
PT-004 System Tables Migration Plan

STOP
ARCHITECT GATE B

STEP 5 in parallel
PT-005 API Skeleton
PT-006 Admin Shell
PT-052 Android Bootstrap

STEP 6
PT-007 Admin Authentication
PT-010 Settings Storage
PT-013 User Account Core
PT-022 Wilayah Repository
PT-025 Bank Repository
PT-053 Android Theme
PT-054 Android Navigation
PT-062 Encrypted Room Foundation
```

This sequence minimizes rework.

---

# 16. DO NOT START THESE TOO EARLY

Do NOT start:

```text
PT-030 Update Lat/Lng Button
```

before Plus Code services exist.

Do NOT start:

```text
PT-038 Publish Engine
```

before Change Request + Review + Audit + Versioning foundations exist.

Do NOT start:

```text
PT-063 Bundled Initial Snapshot
```

before Snapshot Builder format is stable.

Do NOT start:

```text
PT-079 Incremental Sync Client
```

before backend sync contract is stable.

Do NOT start:

```text
PT-077 Nearby Map/List
```

before coordinates and local Bank repository are complete.

Do NOT start:

```text
PT-100 Production Release
```

before QA Gate H.

---

# 17. DEFINITION OF MULTI-AGENT DONE

Multi-agent workflow is considered healthy when:

```text
[ ] Each PT has one primary owner
[ ] Dependencies are checked before start
[ ] No architecture changes happen silently
[ ] Reviewer validates each PT
[ ] Shared files are not concurrently rewritten
[ ] Handoffs contain concrete file/API/DB changes
[ ] Architect gates are respected
[ ] Blueprint remains source of truth
[ ] Release only occurs after QA gates
```

---

# 18. RECOMMENDED AGENT FILES

Suggested Claude Code agent definitions:

```text
.claude/agents/
├── architect.md
├── backend-developer.md
├── commercial-api-developer.md
├── android-developer.md
├── frontend-uiux.md
├── reviewer.md
└── project-orchestrator.md
```

Each agent file should contain:

```text
ROLE
RESPONSIBILITIES
ALLOWED AREAS
FORBIDDEN DECISIONS
REQUIRED INPUTS
OUTPUT FORMAT
HANDOFF RULES
REVIEW RULES
```

---

# 19. RECOMMENDED PROJECT COMMANDS

Optional Claude Code commands:

```text
/plan PT-xxx
/implement PT-xxx
/review PT-xxx
/status
/next
/architecture-check
```

Suggested behavior:

```text
/plan
Architect analyzes only.

/implement
Primary owner implements one PT only.

/review
Reviewer validates against Blueprint + PT.

/next
Orchestrator selects next READY task based on dependencies.
```

---

# 20. FINAL RULE

For MyInfo v1.1:

```text
Blueprint defines WHAT and WHY.

Project Tasks define WHAT MUST BE BUILT.

Master Execution Index defines WHO, WHEN, and IN WHAT ORDER.

Code is subordinate to all three.
```

If there is inconsistency:

```text
1. Blueprint
2. Approved Architecture Decision
3. Project Task
4. Execution Index
5. Existing implementation
```

Do not let existing code override agreed architecture merely because it already exists.

---

**END — MYINFO v1.2 MASTER EXECUTION INDEX**