{"version":"2.1.234","anchor":"terminal-recordings-addressed-as-stored-cast-streams","canonical_anchor":"terminal-recordings-addressed-as-stored-cast-streams","heading":"Terminal recordings addressed as stored .cast streams","tier":"soon","area":"Storage Backend","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/terminal-recordings-addressed-as-stored-cast-streams","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Terminal recordings addressed as stored `.cast` streams\n\nStorage addressing learned about terminal recordings saved as timestamped `.cast` files in a session folder.\n\n**What**\n\nThe internal storage addressing scheme learned about terminal recording files, stored as `.cast` streams inside a session folder and named by an epoch-millisecond timestamp. New filesystem helpers reject reads of symlinked paths, non-regular files, hard-linked values and anything over the size cap, each with its own error.\n\n**Details**\n\n- The timestamp must be 1 to 16 decimal digits.\n- A new table of errors explains, per kind of key, which members name a single stored value rather than a group of them, so asking for a group by a single-value name gets a specific message.\n\n**Evidence**\n\n`must be the recording stamp: 1 to 16 decimal digits (epoch milliseconds)`\n\n- Area: Storage Backend\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 5\/5\n- Present in the build but not switched on"}