A participant can begin with one real task or one real capability. A complete platform is not required.
A Capability Note can be written without an API:
Capability: What can you do?
Location: Where can it happen?
Availability: When or how much is available?
Responsible party: Who can accept the Work?
Conditions: What inputs, tools or limits apply?
Evidence: What will prove completion?
Cost/time: What does one accepted result require?
Rights: What use, reuse, confidentiality or attribution conditions apply?
The first Work should be deliberately small. It should make one interface real and produce evidence strong enough for another team to understand the result. Avoid selecting the most dramatic autonomous use case merely because it makes the best demonstration.
Days 1-30: define one Work, baseline, Authority,
contract and first accepted result.
Days 31-60: reproduce with a second team, device, maker
or location; record differences and hidden assumptions.
Days 61-90: decide whether to scale, standardize,
change the interface, keep the capability local, or stop.
A network that can stop weak ideas is more credible than one that converts every pilot into a success story.
Contribution can be paid service, sponsored work, in-kind equipment, research contribution or another explicitly agreed arrangement. Unpaid contribution should be visible rather than disguised as free capacity. IP, reuse, attribution and confidentiality follow the specific Work and contribution agreement.