Skip to content

Files

Files holds the stored bytes of each upload or rendering, versioned, with share links.

Files holds the stored bytes of every upload and rendering, versioned, with share links scoped like any record. Nothing is overwritten: every Version of a File reads back.

Summary

PartThis System
GroupMoves to Code
StatusLive
ShelfSilent: it runs without being asked

You can ask:

  • “Store this contract”
  • “Share this file with the customer”
  • “Find the latest version of the deck”

What you get

PartThis System
StartsOn for every Startup at creation, with nothing to install.
Built fromStorage, Database, Identity

Nouns it owns

NounDefinition
FileA File is the stored bytes of an upload or a rendering.

Verbs

VerbObjectApprovalEvent
File.createFileNoneFile.created
File.getFileNoneNone.

Events

DirectionEventHow
EmitsFile.createdBy File.create

States

None.

Who operates it

PartThis System
AccountableOperations Lead
TeamOperations Team
SeatA role agent holds it until a Human is seated.
Autonomysupervised

Approvals and limits

None.

Processes that use it

ProcessHow it uses it
RetentionA Workflow writes File
PrivacyA Workflow writes File
Mail handlingA step calls File.get

Rail underneath

None.

Views and dashboards

ViewShowsMetrics
The Operations Lead’s viewThe Metrics its accountable Role answers for.Liquidity

Access

What each Access level may call here.

Access levelMay call
ownerEvery Verb (5)
adminEvery Verb (5)
memberEvery Verb (5)
viewerRead only (2 of 5)

Import and export

None.

Fees and pricing

None.

Availability and limits

PartThis System
StatusLive

Compliance notes

Controls it carries:

None.

Example

A Services-as-Software logo studio stores each client’s brief, every draft and the final artwork. The client opens a share link that expires in 30 days. The draft they rejected in week one still reads back when they ask for it in week six.