Documentation
Build with Gestura core libraries
This portal is being reshaped for developers who want to embed Gestura's agentic loop and gesture systems inside their own apps. The focus here is the reusable library surface, not the CLI or GUI shells around it.
Core libraries
Start with the reusable library surface instead of the CLI or GUI. Learn the public facade, domain crates, and where each responsibility lives.
Agentic loop
Understand how to embed the request -> tools -> reflection -> response loop inside your own application architecture.
Gesture libraries
Map gestures, haptics, and multimodal events into stable application intents that work across products and runtimes.
Recommended reading path
- Read Core libraries to understand the library boundaries and public entry points.
- Move to the Agentic loop guide to learn how to embed orchestration in your own runtime.
- Add multimodal input with Gesture libraries once the core loop is in place.
- Use the API reference and generated Rustdoc when you need exact types and signatures.
What this portal optimizes for
- • Developers embedding agentic workflows in existing products
- • Teams adopting the reusable Rust libraries before app shells
- • Open-source contributors who need practical examples, not just reference tables
- • Gesture and haptic experimentation that can grow into stable libraries
How the documentation model works
Manual guides teach the system
Use the docs section to understand architecture, adoption paths, and how the libraries fit together in real applications.
Generated Rustdoc remains canonical
Inline crate and module documentation should stay the source of truth for exact APIs, types, trait boundaries, and examples.
Examples prove the patterns
Examples and simulator workflows should show how the pieces are composed for everyday use, not just how each API looks in isolation.
Open source, but easier to learn
The goal is not just to publish APIs. It is to make Gestura knowledge easy to learn, easy to apply, and easy to extend. That means guiding developers from concepts to composition patterns to exact API details without forcing them to reverse engineer the architecture from the codebase alone.