In the Web2 era, definitions were fixed by the platform's code. A "deposit" was hard-wired to a specific function: in a banking app, it meant money; in a file server, it meant data. The verb was rigid and could not cross boundaries. You could not speak of a "mineral deposit" in a banking interface, nor a "financial deposit" in a geological database. The context was imprisoned by the application. In the Web3 and Fourth Industrial Revolution (4IR) paradigm, the context determines the definition. The verb "deposit" is semantically neutral and infinitely plastic. It becomes whatever the Schema context declares it to be. If the context is geological, "deposit" can refer to the accumulation of minerals or sediment. If the context is financial, "deposit" refers to an "On Us" ledger transfer at Citi. If the context is usage-based, "deposit" refers to the layering of interaction metadata. The machine does not enforce a single meaning; it reads the context (the input conditions) and executes the specific reality required—whether that is moving ions in a sponge or moving digits in a bank account.
@type) provide the instructional context that tells the system which definition to apply.