/
01.01 Tools and development processes (Proposal)

Get Involved

◎ COVESA Community Calendar
◎ COVESA Getting Started
◎ Understanding and Engaging in COVESA
◎ Project Launch Process

Groups and Projects

Groups and Projects continued...

◎ Vehicle Signal Specification (VSS)
◎ AOSP App Framework
◎ Commercial Vehicle and Fleet Group
◎ Generative AI Group
◎ Central Data Service Playground

◎ Vehicle Data Model
◎ Cyberecurity Group
◎ In-Vehicle Payments Group
◎ Connected Safety
◎ All Groups and Projects

Resources

◎ COVESA Events
◎ Industry Events 2025
◎ Antitrust and Open Statement
◎ Member Visibility

Join/Sign Up

◎ Join COVESA
◎ Sign Up for Member Newsletter
◎ Request Wiki Account
◎ Request Access to Slack

01.01 Tools and development processes (Proposal)

Tools and development processes (Proposal)

Goal: Establish technical infrastructure and workflows for the GenAI Working Group
Presentation Date: December 15, 2025
Sources: collective feedback from group members

🎯 Guiding Principles

We adhere to the following principles to ensure efficient collaboration and technical excellence:

  • KISS (Keep It Simple, Stupid): We start simple and avoid unnecessary complexity.

  • Use Standards: We leverage well-defined standards like MCP and A2A instead of reinventing the wheel.

  • Focus on Integration: Our primary focus is on AI tool integration, not the development of AI models themselves.

  • Everything as Code: All artifacts should be stored in Git, versioned, and be AI-friendly.

📝 Documentation Format

We have selected Markdown as our primary documentation format.

  • Rationale: It is simple, universal, and highly AI-friendly. This aligns with our KISS principle.

📦 Repository Structure

We will adopt a Monorepo strategy.

  • Plan: We will start with a single repository to maintain uniformity and simplicity.

  • Next Steps: The repository will be set up in the coming days.

💻 Code & Style Practices

  • Status: Currently, we have no specific coding or styling guidelines.

  • Plan: This is a work in progress and will be defined as we begin implementation.

🔄 Data & Interfaces

We are committed to using standard formats and interfaces:

  • Data Format: JSON (Standard for MCP).

  • Interfaces: MCP APIs.

🛠️ Tools & Workflow

  • GitHub: This will be the primary location for our knowledge documentation and work output. We intend to publish documentation via a static web page generated from the repository.

  • Confluence: This will be used primarily for documenting group meetings and governance, but not for technical work output.

🤖 MCP Servers

  • Strategy: In addition to implementing our own MCP servers, we aim to build a curated list of existing MCP servers.

  • Scope: This list does not aim to be a complete full index, but rather a useful resource for the group.

🔎 Future Focus & Out of Scope

  • Future Topics: Security (Authentication and Authorization), Safety/Regulatory (ISO 26262), and Edge/Cloud Deployment.