Track: This track focuses on extending, improving, and testing OmegaClaw itself while respecting the boundaries of the core system. Contributors are invited to propose and build meaningful improvements around areas such as memory, goal management, flaw detection, benchmarking, reliability, usability, and performance. The emphasis is not just on adding features, but on improving OmegaClaw in ways that are useful, maintainable, and aligned with its architecture.

Participants should think carefully about what can be safely extended, what interfaces are stable enough to build against, and what types of contributions create real value rather than future maintenance burden.
Strong submissions will clearly define the problem being solved, explain how the improvement fits into OmegaClaw, and provide acceptance criteria or evidence that the contribution works.

Example contribution areas:
- Memory improvements
- Goal-setting or goal-tracking mechanisms
- Flaw detection and correction workflows
- Benchmarking and evaluation tools
- Reliability and performance improvements
- Safer sandbox experiments
- Plugin-like extensions that do not risk the core architecture
- Tests, metrics, or validation frameworks

What success looks like:
A contribution improves OmegaClaw in a concrete and measurable way, while remaining safe, understandable, and maintainable for the core team and future community contributors.

Track: OmegaClaw has powerful capabilities, but every open-source system needs a clear path for new contributors, builders, and users to understand what it does, how it works, and how they can begin experimenting with it.
This track is focused on improving the onboarding experience around OmegaClaw through documentation, demos, tutorials, and educational content. Contributions should help someone move from “I’m curious about OmegaClaw” to “I understand how to try it, use it, and contribute to it." Participants may create quick-start guides, setup walkthroughs, example use cases, demo videos, contributor documentation, architecture explainers, or learning materials that make OmegaClaw more accessible to different audiences. Strong submissions will reduce friction, clarify technical concepts, and create reusable resources that help the community get started faster.

Example contribution areas:
- Beginner-friendly setup guides
- Demo videos or walkthroughs
- Educational content explaining OmegaClaw concepts
- Contributor onboarding documentation
- Tutorials for common workflows
- Clear explanations of system boundaries, entry points, and safe experimentation areas

What success looks like:
A new contributor or community member can understand OmegaClaw, set it up, explore its capabilities, and identify where they can safely contribute without needing deep prior knowledge of the full system.

Track: This track focuses on bringing OmegaClaw into ASI: Create as an interactive agent, workflow, or guided experience that community members can explore and use directly. ASI: Create is designed to help users build, automate, and deploy AI agent workflows through a more accessible interface. For OmegaClaw, this creates an opportunity to move beyond documentation and command-line experimentation by giving users a practical way to interact with OmegaClaw through the ASI ecosystem.

Participants in this track should design or prototype ways for community members to engage with OmegaClaw inside ASI: Create. This may include conversational flows, agent workflows, guided demos, task templates, interaction journeys, or integrations that allow users to ask questions, test OmegaClaw’s capabilities, and understand how it can support real use cases. The goal is to make OmegaClaw more discoverable, usable, and understandable through ASI: Create, while also showing how it can participate in a broader ecosystem of agents, tools, workflows, and decentralized AI infrastructure.

Example contribution areas:
- An OmegaClaw agent or workflow inside ASI: Create
- A guided demo that helps users understand and test OmegaClaw
- Conversational flows for asking OmegaClaw questions or triggering actions
- Templates for common OmegaClaw use cases
- A user journey showing how community members move from discovery to interaction
- Integration concepts connecting OmegaClaw with other agents, tools, datasets, or compute resources available through ASI: Create
- Educational experiences that explain OmegaClaw’s role in the ASI ecosystem

What success looks like:
A community member can access OmegaClaw through ASI: Create, interact with it in a clear and useful way, understand what it does, and explore meaningful use cases without needing to start from the full technical stack.