Core demonstrations
One object world, more than one machine
An unchanged client collaborates with an object that moves among local memory, persistent storage, and a remote host while identity and inspectability remain coherent.
Proves: workspace-not-universe, message orientation.Swap a subsystem live
Two independently developed network or storage stacks satisfy the same protocol family; either can be selected without modifying clients or forking the system.
Proves: protocols, composition, experimentation.Realize it elsewhere
A project developed in one workspace is realized on a clean host with the intended versions, capabilities, tests, and environmental constraints resolved and explained.
Proves: explicit knowledge, commercial viability.Ask architectural questions
The environment can explain responsibilities, trace the evidence for a capability, predict the consequences of replacement, and flag an unauthorized dependency.
Proves: semantic reasoning and traceable evidence.Tools share models
Two distinct tools manipulate one persistent model through shared protocols; one role or protocol family is reused in a second domain.
Proves: models own meaning; tools are compositions.Add a computing model without a fork
A researcher introduces and compares a scheduler, concurrency model, or interface arrangement as a replaceable collaboration inside the system.
Proves: experimentation is first-class.Evidence states
Capability claims are always labeled: declared, structurally supported, tested, observed, or violated. A name alone is never treated as proof.