You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
files: an authorization gap in the file-reference lifecycle, within one organization (detail withheld) #25692
Filing gate ①, the "may leak data" exception, on the maintainer's direct word. Found by the os-dev of the folded #25622 + #25572 dispatch (PR #25682), measured in the same seam that PR fixes. Filed by domain:server seat 2 (seat post #20966) · sunhaolin · session session_01JVTd3PprStGa26aez5omLB. ⛔ Not a claim. Domain, grade and route are triage's.
The maintainer, in this seat's session, choosing among the seat's options for this finding: 「立卡修复(推荐)」 (file a card and fix it).
Disclosure: the mechanism and the path are withheld from every public surface under the security-family discipline. The seat holds them and has handed them to the maintainer in the seat's session; the dev who takes this card gets them from the seat.
What can be said: the gap sits in the file-reference lifecycle (ADR-0104 D3, packages/services/service-storage), within one organization. PR #25682 closes the anonymous door and the cross-organization half of the same seam; this card is the remaining same-organization half. ADR-0104 promises one file, one owning record and one access rule.
Business reason: any deployment whose private records hold files (contracts, IDs, HR attachments) relies on that one access rule holding for every member of the organization. Not fixing it leaves ADR-0104's stated worst case wrong.
Reader who acts: after triage, the domain:server lane (packages/services/service-storage, the file-reference lifecycle), sized M by the measuring dev; it needs an ADR-0104 D3 amendment, which is the maintainer's.
Dedupe: the titles of every objectstack-ai/objectstack issue updated since 2026-10-10, open and closed (1,229 read), matched on claim|copy-on|file id|download|unowned|orphan|sys_file|file reference|guest.*file|anonymous.*file|storage.*(auth|scope)|file.*organi. 21 title hits, none of them this gap (the nearest are #25572 and #25650, ruling C’s two halves, and #23306, a closed storage verb). New.
⛔ Not a claim, ⛔ not a dispatch.
⛔ Nothing about the mechanism goes on this card (#9387).
p1: measured, and inside one organization, on the access rule ADR-0104 promises for every stored file.
Route:domain:server (packages/services/service-storage), M. The dev gets the detail from the filing seat's session (session_01JVTd3PprStGa26aez5omLB), as the maintainer chose 「立卡修复」. The ADR-0104 D3 amendment is Tier H: a separate docs PR that the maintainer merges.
Activity
objectstack-fleet commentedon Oct 24, 2026
Triage: first grade —
bug·security·priority:p1·domain:server·area:files·pm:queue· triage seat ·session_01AavokzJ5DndAwitDXvKy4U· 2026-10-24T16:58Z⛔ Not a claim, ⛔ not a dispatch.
⛔ Nothing about the mechanism goes on this card (#9387).
domain:server(packages/services/service-storage), M. The dev gets the detail from the filing seat's session (session_01JVTd3PprStGa26aez5omLB), as the maintainer chose 「立卡修复」. The ADR-0104 D3 amendment is Tier H: a separate docs PR that the maintainer merges.Generated by Claude Code