3 ecosystem projects
AI4RA UDM, OpenERA, and Vandalizer are being framed as related public assets rather than isolated tools.
Open source
Software as shared infrastructure for a community of practice.
The point of the open source section is not to market products. It is to show how the community is turning shared values into durable public goods. Every release page should connect code to purpose, governance, and institutional usefulness.
Ecosystem logic
The releases make more sense together than separately.
AI4RA UDM provides shared language, OpenERA turns that language into operational capability, and Vandalizer explores AI-enabled workflows under explicit constraints. The site should help visitors understand that relationship quickly, especially if they are arriving from the community side rather than the software side.
- AI4RA UDM creates a common semantic layer for data and interoperability.
- OpenERA provides an open operational layer for workflows and services.
- Vandalizer adds a governed automation layer for targeted AI use cases.
Current state
This ecosystem is real, but it is still early.
The site should say plainly when something is still in formation. That increases trust, reduces product-style ambiguity, and helps contributors understand where their input can still materially shape the work.
3 currently planned
The emphasis is still on framing, governance, use cases, and institutional fit rather than launch theater.
Contribution is still wide open
Practitioner review, workflow critique, evaluation criteria, and governance work are as important as code.
Release pages
Each project needs purpose, status, and governance in plain view.
The release pages should help both practitioners and technical collaborators answer the same questions: why this exists, what state it is in, how it relates to the ecosystem, and what kind of contribution is useful now. That framing matters if you want institutions to treat these as public assets they can trust rather than as opaque experiments they are expected to adopt on faith.
AI4RA UDM
The shared data model layer for common language, interoperability, and durable exchange across research administration systems.
The model is still being framed and validated with practitioners, so the most valuable work is clarifying scope, terms, and real institutional edge cases before anything hardens.
research administrators, data teams, institutional IT
Identify terms or concepts that are defined inconsistently across institutions.
Versioned definitions and change history
OpenERA
The open operational platform layer for research administration workflows and interoperable services.
OpenERA is still at the framing stage, so the immediate need is to validate workflow assumptions and identify where openness and interoperability would create the most operational value.
operations teams, institutional leaders, implementers
Describe workflow pain points, coordination failures, and brittle handoffs that should shape the platform.
A sharper statement of which workflows OpenERA is meant to support first
Vandalizer
The AI workflow layer for transparent, governed automation in research administration contexts.
Vandalizer is best treated as a governed exploration space, so useful progress now depends on bounded use cases, review expectations, and visible failure modes rather than broad automation claims.
research administrators, AI practitioners, technical collaborators
Identify high-friction administrative tasks that may be suitable for bounded automation.
Explicit use cases with clear boundaries
Contribution
Participation should not collapse into “open source equals developers only.”
The ecosystem needs code, but it also needs evaluators, pilot partners, documentation writers, governance contributors, and institutions willing to surface real constraints. The site should normalize all of those roles.
- Review release framing and identify missing institutional assumptions.
- Contribute use cases and workflow examples before implementation hardens.
- Help test documentation, language, and adoption pathways.
- Participate in governance and stewardship conversations, not only code work.
Where to start
Start with the release page, then move into the participation guide.
Until each project has its own public repository and documentation surface linked here, the most honest next step is to read the framing, identify gaps, and use the participation guide to understand what kind of contribution is useful now.