AI Architect
Start with the BACKEND constraints
Select FieldDesk Backend and read its Code Manifest: HTTP boundaries, application logic and transaction ownership.
Work at the subsystem level
AI Architect works with a subsystem and the Software Units in that context. It is currently in beta.
Use it to help create and maintain architecture guidance: how the subsystem is organized, which responsibilities belong where, and which rules implementation should follow.
More views
FieldDesk BACKEND: Unit Types define controller, use-case and service responsibilities.
Laravel Use Case: explicit preconditions, transaction ownership and after-commit effects.
U-58 AmendWorkOrderAction: Laravel Use Case in BACKEND, source path and consuming WorkOrderController.
More views
AI Architect: edit the proposed Code Manifest before applying it to BACKEND.
Investigate before proposing changes
The assistant investigates the subsystem and can clarify open decisions before preparing guidance.
Review proposals against the code and team constraints; they do not guarantee the correctness of the whole architecture.
Good starting points
Document an existing codebase
Investigate an existing subsystem’s structure, responsibilities, and conventions, then review the proposed guidance against its code.
Guide a new product
Define subsystem responsibilities from product goals, requirements, and technical constraints before implementation.
Evolve guidance with the technology stack
For technology upgrades or architectural changes, review affected assumptions and the proposed subsystem and Unit Type guidance diff.
Use guidance in implementation and review
Software Units makes implementation context navigable. MCP for Coding Agents provides a way for external agents to read the relevant context during implementation.
Architecture Governance addresses the later question of whether implementation follows the rules. Keep the decision and the verification of that decision connected.
More views
Laravel Use Case: explicit preconditions, transaction ownership and after-commit effects.
FieldDesk BACKEND: domain boundaries, atomic commands, audit and after-commit effects in the Code Manifest.
FINDING-329: cancellation authorization must be enforced by U-58, linked to REQ-49 and API-25.
