Skip to content

Latest commit

 

History

History
30 lines (18 loc) · 2.93 KB

File metadata and controls

30 lines (18 loc) · 2.93 KB

Consortium Roles

Public-Safe Role Map

This document describes a public-safe candidate role structure for proposal-facing materials. It is not a statement of funded participation, confidential collaboration terms, or partner-specific deliverables.

Use text labels and placeholder boxes for organization identity in open-source diagrams. Do not add third-party logos unless license and written permission are clear.

Candidate Role Table

Entity / group Public-safe role Possible contribution Current public status Claim boundary
Axonova Intended Korean lead and AI-SNN reference-stack integrator Proposal-facing ownership of model, metrics, benchmark, and open-source package Candidate lead-integrator framing for public proposal materials Do not claim awarded funding, validated performance, or committed third-party deliverables
EPFL/RRL International validation-pathway context using modular, origami, and soft robotics embodied testbed expertise Publicly aligned embodied robotics context for future benchmark design and validation planning Public-safe validation-pathway reference, not a confidential commitment Do not claim confirmed funded participation, partner-specific validation, or confidential data access
MorphoSNN open-source repo Public reference-stack seed Documentation, examples, metric framing, benchmark scaffolding, and claim boundaries Public seed repository Do not claim deployment readiness or completed benchmark validation
Future demand/validation users Generic robotics, manufacturing, and edge AI research groups Future feedback, validation scenarios, benchmark requirements, or adoption signals Generic non-committal user category Do not imply named customer commitments or proprietary user data

Logo/Identity Handling Rule

Text names may be used for public-safe role descriptions. Do not commit third-party institutional logos to this public repository without explicit permission or documented usage rights. For now, use text-only names or placeholder boxes in diagrams.

Presentation decks and submitted proposal materials may use approved logos according to applicable submission and branding rules. If logos are later used in slide materials, keep them outside the open-source repo unless rights are confirmed.

Public repository wording must avoid implying institutional endorsement, funded participation, or completed validation unless formally confirmed.

Claim Boundaries

Public materials should avoid claims of validated robotics performance, biological fidelity, confidential data access, confirmed funded participation, or partner-specific deliverables unless supported by explicit public evidence and appropriate permission.

Proposal-facing language may describe intended roles, candidate validation pathways, and public-safe technical responsibilities. It should keep implementation status, validation status, and partnership status clearly separated.