Asset
Only project is required to create an Asset; omit code and the server writes "New Asset <id>", and two assets in one project may share a code, so key on id and never on code.
Entity types
One card per entity type. Each gives the schema name and the REST slug, the field that identifies a row, what a create is refused without, every link field with the types it accepts, the status field, and the traps.
The card is named for the schema name, so /entity-types/Version is the same string
the API answers to.
Attachment
POST /entity/attachments answers 201 on an empty body and returns a row with no file; this_file is editable on create only, so bytes reach a site through the upload dance and never through a create.
Cut
A Cut stores an edit, it does not model one: no field is computed or validated, and
cut_itemsis returned sorted by the item's display name rather than bycut_order.CutItem
Nothing on a CutItem is unique and
coderepeats across Cuts, so an id found by a code search may sit on another Cut: checkcutbefore every update or the write lands on the wrong edit.Delivery
Delivery has two independent Version links, sg_versions and version_sg_deliveries_versions; writing one leaves the other empty, and only the second mirrors Version.sg_deliveries.
HumanUser partial
sudo_as_loginmatchesloginand neveremail; a create is 401 unless it sendssg_status_list: "dis", and an emptyprojectsis not site-wide access.Not measured. what an active user costs in seats, since the site refuses to create or promote one; and whether `projects` or the permission rule set produces the project subset, which needs two users the site does not have
LocalStorage
A LocalStorage row is site-wide and admin-only to write: an Artist reads every row and is refused on create, update and delete.
codemust be unique among live rows, and a DELETE frees it for reuse.Note
A Note is titled by
subjectand bodied bycontent; onlyprojectis required to create one,attachmentslink in that same call, and a bare write torepliesdestroys the Reply rows.Playlist
Playlist.versions reads back sorted by the Version's code, never in the order written; the human order is sg_sort_order on PlaylistVersionConnection, which a write through the field leaves null.
Project
Project is site-wide and has no
projectfield, so a scoping filter 400s on it;nameis the identity, the only field both mandatory and unique, andcodeis a second unique text field.PublishedFile
Only
projectis required to create a PublishedFile, and nothing is unique: the same name, version_number and path publish twice at 201, so read the last version before writing the next.PublishedFileType
PublishedFileType is site-wide with no project field, so a publish that creates one on an unknown extension adds it to every project;
codeis the identity and the only unique field.Reply
Reply is site-wide with no project field, and entity accepts almost every type on the site, not only Note; send entity on create, because a Reply whose entity is null cannot be deleted.
Sequence
A Sequence needs
project, notcode, and project alone names itNew Sequence <id>;shotsis the reverse ofShot.sg_sequence, one link, so a Shot sits in exactly one Sequence.Shot
A Shot needs only
projecton create, andcodeis flagged mandatory, is optional and is not unique: an omitted one becomes "New Shot <id>" and a re-run duplicates rows. Sendcode, key onid.Step
Step is site-wide with no project field, partitioned only by entity_type; list the Steps for a Shot with entity_type is "Shot", and treat neither code nor short_name as unique.
Task
A Task is named by
content, nevercode; a create needs onlyproject;start_date,due_dateanddurationare one triple the server recomputes on every write.TimeLog
A TimeLog create requires only
project;datedefaults to the server's today instead of failing,entitytakes any type despite valid_types ['Task'], and a script may log for any HumanUser.Version
The schema inverts the create contract:
projectis required andcodeis not, generated as "New Version <id>" when omitted.codeis not unique, so key onid.