Deploys
DJINN + Vercel
Deploy status, build failures and rollback state, reported where the work is being discussed.
How it connects
The deploy is not the finish line
A green build that broke a page is worse than a red one. DJINN reports deploy state alongside the change that caused it, so a regression has an owner within minutes.
Rollback is a human call
DJINN surfaces the failure, the likely commit and the rollback command. Pressing it stays with a person.
Ship the committed tree, not the desk
On a shared checkout a production deploy will pick up whatever is sitting uncommitted. The runbook makes that explicit because it has bitten us.
Connector spec
- Auth
- pat · vercel_v1
- Host
- https://api.vercel.com
GET v6/deployments
Emits deployment · incremental on created · cursor pagination
Declared boundary: anyone in the workspace
This spec parses and validates, and it has not been run against a live Vercel account. Sigil fetches and paginates today; it does not yet apply the mapping or enforce the boundary shown here. Both are declared and checked for shape, not executed.
Documents
Vercel setup and reference.
Setup steps, scopes, and the policy boundaries that govern this connector. Sent by email — leave an address and we send them manually, same as the handbook.
- SetupProject linking and deploy hooks
- RunbookDeploy reporting and rollback runbook
Want Vercel wired into your own company brain?