Domain Design and Contracts
These documents explain domain boundaries that cross routes, services, repositories, storage connectors, and internal protocols. They answer why the implementation is split this way and which contracts multiple implementations must share; they are not deployment-facing configuration guides.
Identity and authentication
Section titled “Identity and authentication”- External authentication module: provider descriptors, login flows, account resolution, email verification, and frontend/backend ownership.
Storage and remote nodes
Section titled “Storage and remote nodes”- Remote storage target and policy ownership: remote node, storage target, and remote policy ownership. Chinese source; translation pending.
- Storage descriptor and field normalization: backend-authoritative fields, capabilities, and normalization rules.
- Object naming and OneDrive direct downloads: object keys, provider paths, and direct-download boundaries.
- Object storage custom authentication and AWS SDK reuse boundaries: native COS/OSS signers, presigning, and S3 operation reuse constraints.
Upload finalization
Section titled “Upload finalization”- Upload finalization contracts: finalization rules shared by relay, multipart, presigned, and provider-resumable paths.
Resource locking
Section titled “Resource locking”- Resource lock system refactor contract: the shared REST, WebDAV, WOPI, and administrative lifecycle; removal of persisted
is_locked; workspace namespaces; authoritative transactions; and generation-keyed read caching.
When changing these paths, review the corresponding API, OpenAPI schema, generated frontend types, and focused tests. Do not recreate connector capability matrices in the product layer.