Outcome#
You can map source, authoritative, working, temporary, output, archive, and disposal locations with explicit owners, access, recovery, and retention.
Concept#
A file can be accessible without being durable, approved, backed up, or safe to share. Multiple undocumented copies create ambiguity about which one is authoritative and which rules apply.
Worked Example#
Every placement has a reason and no sensitive or durable data is assigned to an unapproved temporary location.
A correct example uses these decisions:
- Should a research dataset be committed to the exercise or code repository? No; use the supervisor-approved data location and version metadata instead.
- What must happen to required output created on temporary storage? Copy it to the approved durable project location and remove the temporary copy when appropriate.
Common Trap#
Using Git for datasets or checkpoints, or assuming a synced personal folder is approved project storage.
If Blocked#
Do not create another ad hoc copy. Record the unresolved owner, classification, or storage decision and ask the supervisor. Use the NAS guide only after the assigned supervisor folder is known.
Useful references:
Understand Before Accepting AI Output#
An agent cannot decide ownership, classification, retention, or approved services. It must not scan or reorganize real project data to complete this exercise.