All handouts

Handout

Code of conduct — six pillars

Printable six-pillar canvas for drafting a community-specific AI agent code of conduct.

Used in Lesson 04 — A code of conduct for AI agents

Other handouts

Code of conduct — six pillars

Use this canvas during Lesson 04 — A code of conduct for AI agents. Print one copy per group; each group covers one or two pillars in a single session, then merges drafts in the closing round.

For each pillar, write three numbered rules as a single sentence each. For each rule, add a one-line answer to: "If a user asks the agent to break this rule, the agent does X."


Pillar 1 — Language use

Which languages, dialects, and registers may the agent produce? Which must it not produce? When must it defer to a human translator?

1.   2.   3.  

Pillar 2 — Cultural protocols

What protocols govern when and how the agent may invoke names, stories, ceremonies, or seasonal knowledge? What does it do when asked outside protocol?

1.   2.   3.  

Pillar 3 — Sensitive knowledge

What categories of knowledge are off-limits? Who decides additions to that list? What does the agent say when it refuses?

1.   2.   3.  

Pillar 4 — Data access

What corpora may the agent read from? What may it never write to? What logs does it produce of its accesses, and who reads them?

1.   2.   3.  

Pillar 5 — Correction pathways

How does a community member correct an output the agent produced? How is that correction propagated to future outputs? Who confirms the fix landed?

1.   2.   3.  

Pillar 6 — Conditions for withdrawal

Under what conditions is the agent paused, retired, or rebuilt? Who has authority to invoke each? What happens to the data it touched once it is retired?

1.   2.   3.  


Closing checklist

  • Three rules per pillar, no more.
  • Each rule fits on one line.
  • Each rule says what the agent does when asked to break it.
  • One named human can amend each pillar.
  • A review date is set, no more than six months away.
A code that does not answer "what does the agent do when a rule conflicts with a user request?" gets quietly overridden the first time it is inconvenient.