Roadmap 0.11, SuperCad Studio

SCF.2 File director: one routing table decides whether a write goes to the database, the project folder, the blob store or the device

  • Feature
  • Built · in the lab
  • SuperCad Studio

store-routes.json (read by the browser and by PHP StoreRoutes), super-director.js (plan, write, read, migrate, queue, sync and async writers), host api.store per plug-in. Local first, queued mirror to the account, rows tombstoned never removed, unreadable stores never written over. Still no SQLite writer and no cloud blob writer.

super-file-11 2026-11-20: The routing table stays the only decision (store-routes.json + StoreRoutes.php, which now also gives the blob path: browser and server agree). Writers now registered: sqlite-local (rows.sqlite, per-computer opt-in cc-super-sqlite-rows), blob-cloud (super-blobsync.js, the director's blobstore home), and an account writer for team_shared_item. bin/test-super-sqlite-rows.mjs 45/0, test-super-director.mjs 102/0, test-store-routes.php 15/0.

scf-built-11 2026-11-21: BUILT, in the lab. The director in the real page: work-rows.mjs 16/0 and work-sync-live.mjs (real server) write through it to json-local / sqlite-local and the account mirror.

Waits on: Owner decision: may a .supercad be saved without big blobs (a thin file that fetches them on demand)? Until then nothing reads sc_blob on demand

Add a comment

Community comments

No comments yet

Add detail as we go: how you would use it, files or steps that show the problem, what other programs do. The team reads every comment.

Sign in or create a free account to add a comment.