Conflict-of-Interest Disclosure

What It Models

A disclosure joins a member’s duty to declare outside interests with the reviewed declaration for that period. Its purpose is to inform conflict handling without automatically removing voting rights. Submissions owns the form and review process.

Identity and Attributes

Appointment-period uniqueness makes repeated daily obligation creation safe. Period settings determine the coverage and due date. Reviewed summary data comes from the delivered basis or available revision answers and may remain absent.

Relationships

A standing interest can match a decision subject and suggest a recusal. The suggestion does not write one. A recorded recusal may cite the holder’s own disclosure, while appointments and committees remain owned by the committee module.

Invariants

Uniqueness and date checks protect the obligation shape. Permission filters protect sensitive reads. Form start deduplication depends partly on its future receiving contract, and review status has a race between the initial read and final write.

How It Is Stored and Shared

The decisions service creates and requests obligations. Recruitment’s review handler writes the outcome in the shared database boundary. The registered reviewer-conflict function is intended to read standing declarations, and Queries exposes the sensitive disclosure dataset. No custom fields are declared.

Open Design Questions

The production form port is unavailable and skipped due notices are lost. The final request write needs a decision about handling concurrent review, and end-to-end Submissions start deduplication remains unproved.