Roadmap: smaller deferrals — adopted_by, attachment labels, reference words, JSON export

[dvejsada]

Roadmap thread for the remaining deliberate deferrals in spec §18, collected in one place. If discussion on any of these grows, it gets its own thread.

• Structured adopted_by — collective acts name their adopting body as plain text today; an organ/body type would make it referenceable through a directive
• Template-generated attachment labels — attachment titles hardcode their ordinals ("Schedule A", "Schedule B"), so reordering attachments means renaming them; a template-supplied label scheme would restore reorder-safety, at the cost of language-specific label words
• Template-supplied reference label words — authors write "Section" before a reference, and the word can clash with the active numbering scheme ("Section I.A" where "Article I.A" is customary); a style parameter could let the template choose the word
• Machine-readable export — the source file is the canonical machine-readable representation, and the spec deliberately defines no export format; a JSON document model could exist as a companion specification if implementations converge on a need

Which of these actually blocks you, and in what document? Concrete cases move these up the list.