update_architecture
Update project architecture records after implementing recommendations to log file changes and maintain documentation in sync.
Instructions
Update the project architecture tracking after implementing recommendations.
This tool provides flexible project lookup. You can specify any combination of identifiers, and it will resolve to the matching project.
Priority: project_id > workspace_path > project_name
WHEN TO USE:
After implementing architectural recommendations from get_architecture_recommendation()
When completing significant structural changes to the codebase
To document what was actually built vs. what was recommended
To keep the architecture documentation in sync with the code
IMPORTANT: Call this after implementing architectural recommendations to:
Log the implementation details
Track files created and modified
Update architecture history
Document any deviations from recommendations
WORKFLOW:
get_architecture_recommendation() - Get guidance
Implement the recommendation
log_change() - Log each file change
update_architecture() - Update architecture tracking (THIS STEP)
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| project_id | No | Project ID from create_project() (optional if project_name or workspace_path provided) | |
| project_name | No | Project name to look up (alternative to project_id) | |
| workspace_path | No | Workspace directory path (alternative to project_id) | |
| recommendation_id | Yes | ID from get_architecture_recommendation() (required) | |
| actual_files_created | No | List of new files created (optional) - e.g., ["src/auth.ts", "src/middleware/jwt.ts"] | |
| actual_files_modified | No | List of existing files modified (optional) - e.g., ["src/app.ts", "src/routes.ts"] | |
| implementation_summary | Yes | Brief summary of what was implemented (required) |