Overview
Deep nesting can make manual navigation slower. Duplicating instructions for several harnesses creates drift unless updates are synchronized. Periodic cleanup can delete useful work when retention rules are vague.
A large shared workspace can also load too much context if its local instructions attempt to describe every subproject in detail. Top-level instructions should remain high level and point into project folders when exact information is needed.
Portability has a maintenance cost. A workflow may use features that do not map cleanly to another harness. The goal is not perfect interchangeability, but preserving enough project knowledge and operating structure to continue working when the primary environment is impaired.