AckdbMergeCandidate

One first-writer-wins key conflict: a write tried to attach a key that another person already owns. It is recorded, never acted on — merging is always a human decision. A repeat of the same tuple bumps `updatedAt`; a dismissed candidate stays dismissed.

Properties

idstringrequired

personAstringrequired

The person the conflicting write resolved to.

personBstringrequired

The current owner of the contested key.

personANamestring (nullable)

personBNamestring (nullable)

keyTypestringrequired

keyValuestringrequired

evidencePayloadIdstring (nullable)

The ingest that produced the conflict.

sourcestringrequired

statusstringrequired

"open""merged""dismissed"

createdAtstring <date-time>required

updatedAtstring <date-time>required

Bumped on every repeat of the same conflict.

Example

AckdbMergeCandidate example

{
  "id": "string",
  "personA": "string",
  "personB": "string",
  "personAName": "string",
  "personBName": "string",
  "keyType": "email_address",
  "keyValue": "elly@acme.com",
  "evidencePayloadId": "string",
  "source": "slack",
  "status": "open",
  "createdAt": "1970-01-01T00:00:00.000Z",
  "updatedAt": "1970-01-01T00:00:00.000Z"
}