Preserve reasoning that is useful for understanding older code and migrations. These records are not the current feature catalog or instructions for a new implementation. Start with the current architecture or shipped product manuals.
| Record | Scope and replacement |
|---|---|
| Resident architecture | Former root architecture document: resident graph, lease and design decisions. The current architecture entry point now maps both surfaces. |
| Standing goals | Removed v1 machinery. Current chat behavior is documented under automations. |
| Feature and hint catalog | Mixed-surface design inventory; not a verified catalog of current chat features. Use chat capabilities. |
| Remote session acceptance notes | Historical acceptance snapshots and limitations. Use remote architecture and the maintained test guide; revalidate any old command before use. |
Keep change entries and release history in their existing locations. They explain when behavior changed, while current manuals and references explain the resulting behavior.