github.com/gemaraproj/gemara@v0.23.0

docs/roadmap.md raw

 1---
 2layout: page
 3title: Roadmap
 4---
 5
 6This document outlines the strategic priorities ("big rocks") for Gemara in 2026 and beyond. This roadmap is a living document and is subject to change based on community feedback and evolving industry requirements.
 7These are high-level strategic initiatives, not actionable tasks. They represent major directions and aspirations for the project.
 8
 9These priorities were discussed and agreed upon in the Gemara Roadmapping 2026 Workshop, representing community consensus on strategic direction.
10We welcome input and participation in future roadmapping discussions—join our [biweekly meetings](https://github.com/gemaraproj/gemara/blob/main/README.md#contributing) to help shape the project's direction.
11
12## 2026 Goal
13
14Moving the Gemara project to a stable ecosystem providing the technical foundation required to build automation tools on.
15
16### Strategic Priorities
17
18* **Stabilize Schemas**: Finalize and publish stable releases for each Layer schema to provide a predictable foundation for ecosystem adopters. *Why: Unstable schemas prevent adoption and tooling development.*
19
20* **Mature SDK**: Release and maintain language-specific SDKs to facilitate native Gemara integration for tools. *Why: SDKs lower the barrier to adoption and enable ecosystem growth. Depends on schema stabilization.*
21
22* **Unify Lexicon**: Contribute Gemara definitions to the OpenSSF Glossary to establish shared terminology. *Why: Consistent terminology reduces confusion and improves cross-project collaboration.*
23
24* **Expand Community Materials**: Launch and maintain the `awesome-gemara` repository to centralize community tools, integration scripts, and templates. *Why: Centralized resources reduce duplication and help new adopters discover existing work.*
25
26* **Publish Model Whitepaper**: Formalize and publish Gemara model for community adoption and standards-track consideration. *Why: Formal documentation enables standards-track discussions and broader industry adoption.*
27
28* **Create MCP Tooling**: Integrate and standardize the Model Context Protocol (MCP) server to support authoring Gemara artifacts via Agentic AI workflows. *Why: AI-assisted authoring lowers the barrier to creating Gemara-compliant artifacts and explores new use cases.*
29
30## Completed Milestones
31
32### 2025
33
34* Establishment of the layered data approach (Layers 1-4)
35* Adoption by OpenSSF OSPS Baseline and FINOS CCC
36
37## Contributing
38
39If you have suggestions for the roadmap:
40
41* Open an [Issue](https://github.com/gemaraproj/gemara/issues/new/choose) to start a discussion
42* Join our biweekly meetings to discuss roadmap changes (see the Community [page](./community) for details)
43
44Changes to strategic priorities require community consensus through discussion in meetings or issues, not direct edits to this document.