NGCI Gate · Maker-Checker
No one approves their own work.
Delegating execution to a wider team only works if a second set of eyes is guaranteed. NGCI Gate enforces separation of duties as a database rule — the person who created an item can never be the one who approves it. Switch who you're acting as and try.
Audit ledger
No decisions yet. Approve or reject an item.
Why this matters. "A maker can't be their own checker" sounds like a policy — here it's a database constraint. The review record physically cannot be saved with the same person as creator and approver, so no application bug, rushed engineer, or future feature can quietly bypass it. That's what lets you hand execution to lower-cost or offshore staff without losing control: the guarantee lives below the app, and every decision lands in the audit ledger.