docs: add public architecture documentation#1
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0b74499bc5
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| mobile -->|Uploads assets + metadata| api | ||
| api --> storage |
There was a problem hiding this comment.
The high-level diagram currently shows uploads flowing from Mobile app -> Edge API -> Object storage, but the Data flow and Trade-offs sections describe direct client uploads to object storage (Mobile->>Store and “Client uploads first”). This internal contradiction makes the documented architecture ambiguous for readers trying to understand trust boundaries and validation responsibilities, so one of these paths should be updated to match the intended design.
Useful? React with 👍 / 👎.
1 participant
No description provided.