Community
The easiest way in is practical: clone Vellis, follow releases, share useful examples, or ask direct questions as the project takes shape.
Ways in
Clone · follow · share · askRun Vellis
Start with the open repo, run the graph locally, and connect your own MCP-capable tools when you are ready.
See quickstart →Share an example
If you build a useful graph pattern, schema, or starter workflow, send it over. Public examples are the first version of community signal.
Share an example →Follow releases
Watch the public repository or read its release notes on GitHub. Cadence follows real usage, not a calendar promise.
Read release notes →Questions
Ask a question, share a pattern, or surface an edge case by opening an issue in the public Vellis repository.
Ask a question →What to test now
Current, inspectable paths- Stable anchors and typed facts
- Explicit link records
- Deterministic graph traversal
- Validate proposed writes
- Inspect projected state
- Stage schema changes deliberately
- Snapshot and restore state
- Replay history and verify the rebuild
These are the product behaviors worth stress-testing. Builder feedback will shape what Vellis hardens next.