Project Atlas
Project Atlas
Section titled “Project Atlas”The site is structured around a simple rule: every project should have a crisp public-facing overview before it gets a deep documentation tree.
Current lanes
Section titled “Current lanes”vespid_voice— Android-first voice control, realtime orchestration, and agent-facing UX.SkillAuth— delegated authorization for agent execution on login-gated platforms.hermes-profile-sync— portable export and restore for Hermes profiles across machines.vespid— lower-level runtime substrate for brokered execution, session state, and vault-backed control.vespid.ai site— the public shell, docs spine, and brand system tying the repo set together.
What each project page should answer
Section titled “What each project page should answer”- What problem is this trying to solve?
- Who is it for?
- What is already working?
- What remains risky or unresolved?
- Where do the deeper docs live?