File Services (Group 13)

The live object-storage surface. These commands are admin-key protected and limited to object put/get/remove operations.

Overview

Group 13 is not a general-purpose filesystem API in the active reference set. The live audited surface is deliberately smaller: put_object, get_object, and rm_object. Treat these as object operations, not as folder-management commands.

Access control

Group 13 is admin-key protected. Frontend and tooling integrations should assume privileged credentials are required.

Live commands

Code Name Purpose
134put_objectStore or replace an object payload.
135get_objectRead an object payload.
136rm_objectDelete an object payload.

134 — put_object

put_object writes an object into RAIDA-managed storage. Use it for controlled object publication or synchronization tasks that belong to the privileged object namespace.

Request body element Developer note
Admin keyEvery live Group 13 command starts with the configured admin key.
Object pathResolved under the server's Folders area. Path traversal is rejected.
Object payloadOpaque bytes stored at the resolved path.

135 — get_object

get_object reads back a previously stored object. Clients should treat returned bytes as opaque object content unless a higher-level format contract exists elsewhere in the protocol.

The request carries the admin key plus the target object path. The response body is the stored object bytes on success.

136 — rm_object

rm_object removes an object from the privileged store. Use it when the object should no longer be retrievable.

The request carries the admin key plus the target object path. The success path is a status-only confirmation.

Scope boundary

This page intentionally does not revive historical folder, ACL, or version-management commands because they are not part of the current live Group 13 surface.

Path safety

The live implementation resolves and normalizes paths before access. Treat Group 13 paths as a controlled object namespace, not an arbitrary filesystem escape hatch.