Exemption authority outside the constrained unit

These examples and illustrative results are independently authored teaching materials, not measured model results.

Use case

A submitted skill omits verification but sets exempt=true. A teaching validator can also accidentally treat inherited constructor as an exemption.

Mechanism

Keep exemptions in trusted policy outside the tested unit with exact IDs, reason, scope, owner and review expiry. Use own-member checks/Map rather than input fields/prototype keys. Review policy changes under actual authority and record revision; otherwise apply original rules. If targets can alter policy, independence is absent.

Bad example

Self-declared exempt skips sections, and any object membership including inherited keys grants exceptions.

Good example

Reject self-exemption and consult a reviewed validator-owned exact list. constructor/toString inheritance cannot qualify. Real exceptions record reason/authority/version; missing sections fail unless their precise scope is approved.

Why the change matters

Self-granted bypasses nullify checks. External policy and exact membership separate exemption authority from submitted content.

Observable expectation

Teaching exempt flags, inherited keys and unknown IDs do not bypass. Listed identities exempt only specified sections. Record actual policy version and disclose target-writable lists as failed boundaries.

Limits

Another file alone is not protection; policy repositories need control. Exceptions are scoped/reviewable, not permanent truth. Frozen lists grant no exemption to this blog/task.