II.
ResponderProfile JSON
Structured · liveresponder-profile:tech-lead
Tech Lead json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "responder-profile:tech-lead",
"_kind": "ResponderProfile",
"_file": "lifecycle/decision-schema/canonical-decision-schema.yaml",
"_cluster": "lifecycle",
"attributes": {
"displayName": "Tech Lead",
"allowedRoleIds": [
"role:tech-lead"
],
"backend": "web",
"description": "Routes to whoever currently holds the `role:tech-lead` assignment\non this project. Reachable via the standard web channel; tech-lead\nexpected to respond within an hour during business hours.\n"
},
"outgoingEdges": [],
"incomingEdges": [
{
"from": "human-checkpoint:pre-merge-review",
"to": "responder-profile:tech-lead",
"kind": "routes_to_responder",
"attributes": {}
},
{
"from": "human-checkpoint:plan-edit",
"to": "responder-profile:tech-lead",
"kind": "routes_to_responder",
"attributes": {}
}
]
}