project-structure

To organize repository structure, place backend transport code, domain logic, frontend modules, and rules/config data into explicit directory boundaries. This prevents misplaced modules and tangled dependencies by enforcing consistent placement rules across services, APIs, and UI code.

Analytics pipelines and testing conventions should live in dedicated analytics modules and test locations defined by explicit directory boundaries. This ensures reporting workflows and tests follow predictable module boundaries without duplicating business logic.

The best way to place governance docs is within `.codex/` governance storage directories. Storing project guidance and governance artifacts in this dedicated location prevents governance gaps and maintains alignment with service and API placement rules.

Prevent tangled dependencies by following file creation conventions tied to intent, placing new API routes and services within explicit directory boundaries for backend transport and domain logic. This reduces coupling and discourages cross-layer business rule repetition.

You should avoid notebook production logic in analytics pipelines because it creates anti-patterns that increase coupling and duplication. Placing analytics outputs in dedicated modules with explicit boundaries maintains predictable structure and maintainability.