The authoring kernel for the VisionVolve suite.
VV Studio edits, renders, and collaborates on VVDOC documents — the designed-artifact format that flows between Workshop, Marketing, Catalog and every other tool in the suite. Scene-graph editing in the browser. Headless authoring via CLI + MCP. Live multi-author collaboration. One source → many outputs.
Service status
Live from /health. Unauthenticated probe; safe to share.
Capabilities
Consumers (Workshop, Catalog, Marketing, …) pick the lowest tier that meets their need. Higher tiers = more power + more coupling. See STUDIO-CAPABILITIES.md for the full contract reference.
This environment requires an IAM Bearer token for every /api/*,
/studio/*, and /doc/* endpoint. Get a token with
vv-iam login --env=staging in your shell, then
return here. Per-project ACL is honored via optional .acl.json
sidecars — see docs/SECURITY.md.
Quick links
Open the editor
WYSIWYG scene-graph editor for VVDOC. Multi-select, alignment, live collab.
/studio.html
Service health
Unauthenticated probe — version, git_sha, MCP paths, uptime.
GET /health
API surface
OpenAPI 3.1 spec — every render-surface route, request/response shapes, error envelope.
/api/openapi.yaml
Source code
All code, ADRs, tests, deploy workflow. Issues + PRs welcome.
github.com/Visionvolve/doc-studio
Architecture
Kernel/domain/workflow + the 5-tier capability model. How consumers integrate.
docs/ARCHITECTURE.md
Security model
IAM gate + per-project ACL + threat-model table. Mitigation status per concern.
docs/SECURITY.md
vv-standards
The suite constitution — VVDOC spec, principles, patterns, ADRs.
github.com/Visionvolve/vv-standards
Per-tier contract
What each integration tier guarantees. Pick the lowest one that satisfies your need.
docs/STUDIO-CAPABILITIES.md