The packages

graview is the tool a person installs; @graview/* is the framework a product imports. 13 packages, one version, each depending only on the ones beneath it.

• @graview/coreThe graph, the log, the schema and the checker. Everything a Graview app declares, and the CLI that verifies it.
• create-graviewStart a product on Graview: `npm create graview my-app`. The conventional door to `graview create`.
• @graview/embedMount a declared Graview app into any element — the scene, the Graview, or the routed pages — without the Shell, sized and themed within the element.
• graviewThe Graview command line: start a product, check its declaration, write its agent docs, serve its store, host it for an agent over MCP, apply an act to it, sync its seed, install the authoring skills. The tool; @graview/* is the framework.
• @graview/layoutWhere every node goes: three planes, one pure function of the graph and the view state.
• @graview/pagesThe traditional face: a routed webapp derived from the same declaration that drives the scene.
• @graview/primitivesThe primitive set, the three lenses, the workbench and the visual system.
• @graview/reactThe React binding: a provider, a scene, and the hooks an app builds on.
• @graview/renderThe spatial renderer. The DOM path is what ships; the GPU capture path is EXPERIMENTAL — see README.
• @graview/shipWhat every deployment needs, hosted or self-hosted: persistence wiring, op-log-native migrations, export, health.
• @graview/skillsSkills that teach an assistant the authoring moves, each ending in a real graview check verdict.
• @graview/studioThe declaration itself as a graph: kinds, fields, edges, acts, rules, roles and grants as nodes, edited with ordinary mutations in Graview's own interface, checked before they are applied, migrated, and written back as the files graview create writes.
• @graview/toolsDerived affordances and the agent tool surface, generated from the same declarations; graview mcp and graview apply host it against a real store.