Dino-GSP Project File (.algeo) Protocol
A Dino-GSP project file stores an editable, interactive geometry project.
File format
| Item | Current standard |
|---|---|
| Extension | .algeo or .json |
| Content | UTF-8 JSON |
| MIME type | application/vnd.dino-algeo.project+json |
Top-level structure
typescript
interface FileContentLatest {
slides: SlideV2[];
messages: SeedChatMessage[][];
templateStyle?: SlideStyleSheetV2;
metadata: ProjectMetadata;
}| Field | Type | Required | Description |
|---|---|---|---|
slides | SlideV2[] | Yes | Ordered list of canvases in the project. |
messages | SeedChatMessage[][] | Yes | AI conversations. The outer array contains conversations; each inner array contains its messages. Use [] when there are none. |
templateStyle | SlideStyleSheetV2 | No | Project master template with the same shape as a canvas styleSheet. |
metadata | ProjectMetadata | Yes | Project metadata and sharing options. |
Canvas SlideV2
typescript
interface SlideV2 {
definitions: DefinitionV2[];
uvarMap: [string, number][];
styleSheet: SlideStyleSheetV2;
doc: DocOp[];
camera?: SlideCamera | SlideCamera3D;
}| Field | Type | Description |
|---|---|---|
definitions | DefinitionV2[] | Definitions for points, lines, circles, functions, text, sliders, buttons, images, and other objects. Order affects dependency resolution. |
uvarMap | [string, number][] | Current user-variable values as [name, value] pairs, including dynamic state such as dragged coordinates and slider values. |
styleSheet | SlideStyleSheetV2 | Canvas background, axes, grid, type defaults, and per-object styles. |
doc | DocOp[] | Associated rich-text content in Quill Delta Op form. |
camera | SlideCamera | SlideCamera3D | Optional 2D or 3D camera state. |
Project master template
templateStyle is an optional project-level master template with the same shape as slides[].styleSheet. It is stored separately from the current style of each canvas:
templateStyleis the reusable project master.slides[].styleSheetis the style currently stored on an individual canvas.- Applying a master template preserves per-object styles keyed by object ID.
A project master should contain reusable visual styles only. Axis or grid ranges, intervals, visibility and locking state, and per-object styles should not propagate as master-template properties.
Reading and writing guidance
- Store the complete object, not only
slides[].definitions; variable values, styles, rich text, cameras, conversations, and the master template are all project content. JSON.stringify(content, null, 2)produces an inspectable.algeoor.jsonfile. Parse JSON first when reading, then validate the required fields.- Do not manually generate complex geometry DSL. Prefer complete content returned by the SDK, or generate projects through REPL, MCP, or the Agent API.
Use in each integration
- SDK: Read and write complete projects with editor-mode
getContent()/loadContent(), or presentation-modeloadFile(). - HTTP API: The Render API accepts complete
FileContentLatestin itscontentfield. - MCP:
import_projectimports a complete project andexport_projectexports an.algeofile.