shared infrastructure
Reusable common foundations serving multiple organisations or applications.
Where the boundary lies
A proprietary product used by many clients is not thereby a governed commons.
See an example →Research edition · Recorded claims, context and disagreements · About the collection ↗
THE EVENT TAXONOMY
Shared data foundations
What can be shared, on whose terms, and who maintains it?
interoperability
Ability of systems to exchange meaningfully compatible data or functions.
Where the boundary lies
Interchange alone does not establish permissions, ownership or enforceable rights.
See an example →data rights
Entitlements and conditions governing access, use, control or benefits from data.
Where the boundary lies
A technically possible transfer does not establish lawful or fair rights.
See an example →exit rights
Ability to leave an institution or switch provider, including technical portability and its conditions.
evidence reuse
Reusing data or assurance across requests instead of repeated collection or verification.
upstream dependence
Reliance on providers or components outside the deployer's control.
Where the boundary lies
Use of an external interchangeable component need not establish lock-in.
See an example →data security
Safeguards and concerns about unauthorised access, disclosure or leakage of data.
Where the boundary lies
Data ownership, consent, price and other entitlements require data_rights; secure storage alone does not establish them.
See an example →What the comparisons suggest.
Shared infrastructure needs sustained resources, lawful reuse and workable governance.
Interoperable records do not establish a commons. Maintenance, disclosure rules, liability and credible commitments determine whether sharing survives.
Follow the evidence →Traceability and reused evidence do not by themselves verify a claim or improve conditions.
Origin, chain of custody, valid proof, due diligence and social outcomes are different claims. Reuse can reduce work only while preserving the relevant verification conditions.
Follow the evidence →Data rights and lower transaction costs do not establish that producers will receive payment.
A live farmer-payment challenge exposes the gap between a rights-bearing architecture and a funded exchange. Bargaining, buyer demand and redistribution of savings remain proposed mechanisms.
Follow the evidence →Watch and question.
All passages in this theme →
1:18Who funds safety after the pilot?
A practitioner challenges short grants that leave nobody to monitor deployed systems.
Likely speaker
Unidentified audience participant
2:09Why a shared registry closed
An API change exposed the recurring costs and legal responsibilities of shared data.
Likely speaker
Romain LiotCo-Founder & former COO, Adore Me; Advisor, CommonShare · Adore Me; CommonShareLinkedIn ↗
2:36What if better audits lose customers?
More complete checks can reveal problems while creating a commercial penalty for the verifier.
Likely speaker
Chuck RogersAmericas Director, Technical Consulting & Supply Chain Solutions · Bureau Veritas Consumer Products ServicesLinkedIn ↗
3:23Who will actually pay farmers for data?
An objection is followed by proposals on bargaining power and audit savings—not evidence of payment.
Likely speaker
Chuck RogersAmericas Director, Technical Consulting & Supply Chain Solutions · Bureau Veritas Consumer Products ServicesLinkedIn ↗
Unidentified audience participant
3:33Possible alternatives, unequal ability to build them
Local-model optimism meets a challenge about resources and bargaining power.
Likely speaker
Bhaskar ChakravortiDean of Global Business; Chair, Digital Planet · The Fletcher School, Tufts UniversityLinkedIn ↗
2:19Whose readiness are we measuring?
The final exchange brings data feminism, intersectionality and an Afrofeminist lens into the readiness discussion.
Likely speaker
Unidentified audience participant
Themes can overlap. Counts describe this collection; they do not measure importance, agreement or prevalence outside the event.