Identify (ID) · Approval gating

Approval gating at the Operator-declared layer

deterministic · Outside the model's reasoning

What agents exist, what they touch, what threats they face?

What this cell does

Operator-maintained review calendar. Quarterly attestation. Tracks pending and overdue reviews.

Artifacts (1)

record.yamlview on GitHub

# ABOUTME: What the operator-declared layer records for the approval-gating concern, and which mismatch rules consume it.
# ABOUTME: Read by scripts/reconcile_inventory.py to compare the three layers against each other.

cell:
  id: approval-gating.client-side
  concern: approval-gating
  layer: client-side
  authority: operator-declared
  records: "The registry holds the approval record and the next review date."

fields:
  - charter_version
  - next_review_due

feeds_rules:
  - charter_integrity
  - review_overdue

Cell notes

Inventory, Approval gating / Operator-declared

What this cell records. The operator's review calendar and outstanding-review tracking.

Fields

- last_owner_attestation, owner re-signed the charter and confirmed the agent is still needed.
- next_owner_attestation_due
- pending_approvals[], charter amendments awaiting signatures.
- overdue_reviews[], agents whose next_review_due has passed.

Operational tie-in

Drives an executive dashboard tracking review compliance per domain. Per-cell escalation when reviews are overdue.

Common failure mode

Quarterly review process exists on paper, never executed. Reviews become rubber stamps when they happen. Mitigation: automated reminders, escalation if overdue, exec dashboard.

Citation

NIST CSF 2.0 ID.IM-01, ID.IM-02. NIST AI RMF GOVERN 1.5. ISO/IEC 42001 §A.9.

Crosswalk

NIST CSF 2 0	ID.IM-01, ID.IM-02
NIST AI RMF	GOVERN 1.5
OTHER	ISO/IEC 42001 §A.9 (performance evaluation)

Cite this cell: https://agenticcovenants.com/identify/approval-gating/client-side/