skills/vercel__eve
1
0
Fork 0
mirror of https://github.com/vercel/eve.git synced 2026-09-20 05:35:39 +08:00
Code Issues Packages Projects Releases Wiki Activity

e0: prepare changes

Browse Source
This commit is contained in:
vercel-gh-bot-3[bot]
2026-06-28 21:30:06 +00:00
committed by GitHub
parent 6dc84fc33f
commit b9e6000f06
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/patterns/multi-tenant-approvals.md
+2 -2
View File
@@ -187,8 +187,8 @@ Policy lookup failures should throw or deny, never silently allow. Recheck autho
An approval durably pauses the session and a later request resumes it. Your HTTP boundary must ensure a caller cannot continue or stream a session owned by another tenant. Persist session ownership in your application and check it before proxying:
- `POST /eve/v1/session/:sessionId`, including `inputResponses`;
- `GET /eve/v1/session/:sessionId/stream`.
- `POST /eve/v1/session/:sessionId`, including the `continuationToken` and `inputResponses` body fields
- `GET /eve/v1/session/:sessionId/stream`
Built-in approval confirms that a human with access to the session approved the call. It is not a four-eyes workflow that proves a different person or role approved it. For that requirement, create an application-owned approval request, notify eligible approvers through a channel, and have policy return allow only after that request records an authorized decision.