Repository navigation
Gantry v3.4.0 — Shared product workspaces
Gantry 3.4.0 adds shared product workspaces: import an existing saved project, share unfinished CAD/code, and let another authorized participant restore the exact state and continue independently.
- Artifact-first Studio: CAD, Code and Checks; version-bound discussions and sharing.
- Local workspace import, sync and watch; frozen chunked uploads up to 10,000 scoped files / 1 GiB; interrupted and lost-response recovery.
- Recipient-owned credentials, reviewed member grants and session enrollment, revocation, operator provisioning and verified backup/restore.
- Integrated external/native engineering adapters and physical-evidence workflows, with baseline-bound acceptance and durable publication recovery.
- Opt-in Bot experience comparison and continuity work. No automatic paid inference or publisher telemetry.
Validation: 1,279 Python test invocations (1,271 passed, eight optional skips), 31 JavaScript passes, isolated-wheel installation, and actual local HTTP/CadQuery acceptance with two identities. Shared work remained unverified and unadopted until the separate verification/adoption paths. These checks do not demonstrate engineering-time reduction.
Important qualifications: native vendor APIs remain experimental and unverified in licensed applications; Zuken/Capital SDK drivers are not implemented. Customer SaaS authentication, realistic assemblies and live Linux/TLS deployment still need qualification. The included deployment recipe is for an operator-managed invited-team host, not an already provisioned cloud service. The static public demo does not store customer project data.
Documentation:
- Connect and share a workspace
- Membership and cloud operations
- Verification and remaining limits
- Exact native CAD coverage
Install the attached wheel in a security-patched Python 3.11+ virtual environment on macOS/Linux. Core has no mandatory runtime dependencies. Optional CAD/native/feedback dependencies are separate. Back up existing ledgers and preserve credentials separately before upgrading. Existing state and event history are preserved through additive contracts; no destructive migration is required.