File Ownership

Step 1: Map All Files

List every file that needs to be created or modified for the feature.

Step 2: Identify Natural Clusters

Group files by:

• Directory proximity (files in the same directory)
• Functional relationship (files that import each other)
• Layer membership (all UI files, all API files)

Step 3: Assign Clusters to Owners

Each cluster becomes one implementer’s ownership boundary:

• No file appears in multiple clusters
• Each cluster is internally cohesive
• Cross-cluster dependencies are minimized

Step 4: Define Interface Points

Where clusters interact, define:

• Shared type definitions (owned by lead or a designated implementer)
• API contracts (function signatures, request/response shapes)
• Event contracts (event names and payload shapes)

Ownership by Project Type

React/Next.js Frontend

Express/Fastify Backend

Full-Stack (Next.js)

Python Django

Conflict Resolution

When two implementers need to modify the same file:

1. Preferred: Split the file — Extract the shared concern into its own file
2. If can’t split: Designate one owner — The other implementer sends change requests
3. Last resort: Sequential access — Implementer A finishes, then implementer B takes over
4. Never: Let both modify the same file simultaneously