Consolidate scaffolding into x/

Context and Problem Statement

Templates, attachments, and Quartz static assets were scattered (Templates/ at root, no attachments folder, static/ at root). All serve “vault scaffolding” — supporting infrastructure, not content.

Considered Options

• Top-level x/ folder containing x/templates/, x/attachments/, and x/static/.
• Separate top-level folders (Templates/, attachments/, static/).
• Name the bin Extras/ or _system/.

Decision Outcome

Chosen option: “Top-level x/ folder”, because it consolidates non-content infrastructure under one bin, aligns with LYT’s x/ convention, and reduces top-level folder count. Initial layout:

• x/templates/ (migrated from Templates/)
• x/attachments/ (new — Obsidian default attachment location)
• x/static/ (migrated from static/; later merged into x/attachments/ per 0012-merge-static-into-attachments)

Pros and Cons of the Options

x/ bin

• Good, because concise and conventional in LYT/ACE.
• Good, because reduces top-level folder count.

Separate top-level folders

• Bad, because three folders for scaffolding is sprawl.

Extras/ or _system/

• Bad, because more verbose; x/ is the established convention.