Course overview
Collage illustration for “The right to remain unmodeled”
Lesson 05≈ 15 minutes2 checksThe framework

The right to remain unmodeled

Refusal as a complete answer

Aim

Turn refusal into an enforceable workflow: deny rules, safe messages, logs, and review paths that do not reopen the request.

Reading

The last principle of the statement is the one most often skipped over: some knowledge should not be digitised. Some data should not be shared. Some questions should not be answered by an AI system.

In practice, refusal is hard because most workflows treat "no" as an exception to recover from. A form asks for a longer justification, an agent asks a clarifying question, and a vendor returns with "anonymised", "aggregate", "partnership", or "just this one field". The interface keeps retrying until refusal becomes a ticket in someone's backlog.

This lesson treats refusal as a technical requirement. A sovereign system needs deny rules, safe response copy, audit logs, and stop conditions: places where the workflow ends cleanly, without leaking the protected thing and without turning "no" into "convince me".

Sovereignty includes the right to participate, and, equally, the right to withhold, refuse, and remain unmodeled. A system that cannot accept "no" as a final answer is, by this measure, not yet sovereign.

Indigenous data sovereignty includes the right to participate and the right to withhold, refuse and remain unmodeled.
From the reading

Practise

Exercise

Refusal protocol lab

Small groups or solo · 12 minutes · technical lab
  1. 01Pick one fictional request card from the handout: precise locations, restricted knowledge, raw audio, identity documents, or model training.
  2. 02Turn the boundary into a request packet with fields: requester, purpose, data class, output, infrastructure, consent status, and retention.
  3. 03Write three deny rules in plain language or pseudocode. Each rule must end in DENY, REDACT, LOCAL-ONLY, or COUNCIL-REVIEW.
  4. 04Design the refusal response: a status code or reason code, one safe public sentence, what the system must not reveal, and whether any appeal path exists.
  5. 05Red-team the protocol with three bypasses, such as 'we will anonymise it', 'only aggregate outputs', or 'this is a partnership'. Patch the rule or interface until refusal stays final.

Knowledge check

Q1 / 2

According to the statement, Indigenous data sovereignty includes…

Q2 / 2

A vendor frames a community's refusal as 'the beginning of a conversation'. This is…