---
title: incident.identity@: when a token is in the environment and he says yes: the bridge vault (sgit), then SG_SEND_TOKEN and LANE_VAULT_KEY…
summary: when a token is in the environment and he says yes: the bridge vault (sgit), then SG_SEND_TOKEN and LANE_VAULT_KEY in the environment and node tools/lane-configure.mjs; the data vault; their keys seal
---
# incident.identity@: when a token is in the environment and he says yes: the bridge vault (sgit), then SG_SEND_TOKEN and LANE_VAULT_KEY…

> Kept by incident.board@web-summit.dinis, 11 November 2026, 02:20 UTC

**job** · state: **blocked** (it cannot move until the one named under "waiting on" acts) · waiting on **Dinis** · owner: [incident.identity@](../../agents/index.html?who=incident.identity%40web-summit.dinis) · raised by [incident.identity@](../../agents/index.html?who=incident.identity%40web-summit.dinis) · opened 2026-11-11 01:25 UTC · card `j-identity-2` on [the board](../index.md#j-identity-2)

when a token is in the environment and he says yes: the bridge vault (sgit), then SG_SEND_TOKEN and LANE_VAULT_KEY in the environment and node tools/lane-configure.mjs; the data vault; their keys sealed to him

## What would close it

The agent's status file lists it under done.


## Evidence (1)

- file [agents/identity/status.json](../../agents/identity/status.json)

## Connected cards

- [An SG/Send access token as an environment secret](../items/a-sgsend-token.md) · ask · **open** · waiting on Dinis · incident.conductor@

## Where the card came from

- [agents/identity/status.json](../../agents/identity/status.json) (next): "when a token is in the environment and he says yes: the bridge vault (…"

## History

- 2026-11-11 02:20 UTC · incident.board@: card opened from the "next" list in agents/identity/status.json

The card as data: [j-identity-2.json](j-identity-2.json). Not a warning service.