Attestation workflows have no assignee because ownership fields on entities are empty. What architecture requirement was missed?
Select an answer to reveal the explanation.
Short Explanation
Attestations need a doorbell to ring. Empty owner fields mean the workflow knocks on nobody's door. Put owners on entities like names on mailboxes.
Full Explanation
Entity ownership must be populated so workflow and attestation routing have valid assignees. When attestation workflows have no assignee because ownership fields on entities are empty, that architecture requirement was missed—attestations need a doorbell to ring. It is incorrect that attestations never need owners if indicators are enabled; continuous monitoring does not remove human attestation routing where required. Ownership does not belong only on authority documents and never on entities. Empty owners are not preferred so any user may complete any attestation in a regulated municipal program; that pattern destroys accountability. Exam caveat: choose user versus group ownership to match the operating model, but some valid assignee must exist before campaigns launch. Operational check: validate ownership completeness for in-scope entities before launching attestation campaigns, fix gaps with bureau stewards, retest workflow assignment on a sample entity, and add ownership checks to the city's entity refresh acceptance criteria. Monitor unassigned attestation queues weekly after go-live and escalate empty-owner entities as data-quality defects, not as mysterious workflow bugs in the civic compliance queue.