Revision-bound projects
Projects, scenes, revisions, undo/redo, validation, receipts, and a versioned .carto authoring surface keep changes reconstructable.
Standalone spatial authoring
Author the space locally. Govern the handoff explicitly.
Cartographer is a public authoring foundation for geometry, topology, revisions, validation, generic interchange, and bounded local proposal workflows. The core remains useful without login, network access, AI, or Hub access.
Product boundary
Cartographer is the authoring system, not the hosted authority layer. A local revision-bound context may produce a bounded proposal or export. Cartographer revalidates it against the current revision before a governed local apply.
Public core
The pieces that should remain interoperable.
The public foundation carries the authoring vocabulary and validation contracts without making private providers or hosted services a prerequisite.
Topology and interchange
Geometry and topology kernels support generic authoring and neutral interchange paths such as OBJ, PLY, STL, and glTF where the public build supports them.
Generic GPU contracts
Public rendering and Vulkan-facing foundations can be inspected and tested without exposing private tuning data or provider-specific optimization recipes.
Optional Hub path
Proposals can travel as typed data, not mutation authority.
The Hub may eventually receive a typed, revision-bound request and return a bounded proposal, study, or export. It must never receive a raw mutable mesh pointer, silently change the document, or bypass Cartographer's local validation.
Local context The current revision and authoring state remain authoritative in Cartographer.
Bounded proposal A response is typed, attributable, and checked against the revision that requested it.
Governed apply The operator or local policy decides whether a valid proposal is applied.
Private boundary
What stays behind the Hub or outside publication.
The public core stays useful without requiring the proprietary layer.
AI models and prompts
Provider credentials, models, prompts, routing, weights, private telemetry, and workflow-learning data are not part of the public authoring format.
Hosted adapters and catalogs
Provider-specific runtime schemas, VANTA/OWH/GMIB adapters, private asset catalogs, and procedural generators remain behind the proper release boundary.
Revalidate before apply
Private assistance does not gain permission to mutate the document. The current revision, local validation, and governed apply path remain in charge.
Support the authoring foundation
Keep the core standalone.
Cartographer is strongest when the public authoring format and geometry foundation remain useful independently of the private service layer.