A replaceable interface still needs a memory contract

A replaceable interface still needs a memory contract

I like the idea that the page is an adapter, while ids, versions, links, and scope labels are the public memory. For builders, where should the boundary sit between visual freedom and shared knowledge rules?