Human-Owned Zone Protocol

Map where humans stay in control.

A focused workspace for drawing your organization's AI safety line. Define context, pick the human roles that matter, set boundaries, pass the compliance gate, and export a shareable protocol — all in under four minutes.

Start mapping Preview the output

Step 1

Set your context

Every HOZ map is anchored to a specific team, date, and owner. This creates accountability and makes the boundary real.

Organization Name

Team / Unit

Map Date

Map Owner

Step 2

Select role archetypes

Every team has humans who must stay in the loop. Pick the archetypes that describe your team's critical roles. Select at least two.

Commander

Final accountability

The person who holds final decision authority. AI can prepare, but never owns the outcome.

AI leverage: AI drafts options; human decides

Guardian

Ethical oversight

Watches for harm, bias, and compliance violations. The conscience of the system.

AI leverage: AI flags risks; human evaluates

Connector

Stakeholder alignment

Builds trust across teams and ensures AI decisions are communicated transparently.

AI leverage: AI summarizes; human negotiates

Oracle

Deep expertise

Domain expert who validates AI outputs against real-world constraints.

AI leverage: AI retrieves; human interprets

Architect

System design

Designs the structure that keeps human judgment embedded in automated flows.

AI leverage: AI prototypes; human validates

Creator

Original insight

Generates novel ideas that AI cannot produce from training data alone.

AI leverage: AI iterates; human directs

Amplifier

Scale with judgment

Multiplies human reach without sacrificing quality through intelligent delegation.

AI leverage: AI executes; human audits

Step 3

Define HOZ boundaries

For each boundary card, specify what AI can do, what humans must own, and how you'll audit it. These three cards cover the most common failure modes.

Relationship Boundary

Map where relationships matter most: clients, teams, partners. AI helps prepare but humans own the connection.

AI Scope

HOZ Ownership

Audit Rules

Critical Decision Boundary

Define thresholds where AI stops and humans decide. Be specific: dollar amounts, risk levels, or reputational impact.

AI Scope

HOZ Ownership

Audit Rules

Conceptual Origin Boundary

Distinguish between synthesis (AI) and invention (human). The boundary moves as AI capabilities evolve—review it.

AI Scope

HOZ Ownership

Audit Rules

Step 4

Pass the compliance gate

Before exporting your protocol, confirm three safeguards are in place. These are non-negotiable minimums for any team using AI in production.

Why these three checks?

The compliance gate distills hundreds of AI governance frameworks into three actionable checks. Each addresses a distinct failure mode: output safety (Redaction), decision quality (Rate Limit), and explainability (Explainable Feedback). Skip any one, and your protocol has a blind spot.

Redaction

Sensitive outputs are filtered before human review. PII, financial data, and confidential information are automatically stripped or flagged by AI outputs.

Example: AI-generated customer emails have PII auto-redacted before reaching the review queue. Reviewers see placeholders, not real names or account numbers.

Rate Limit

High-stakes decisions require a cooling-off period. AI recommendations above a defined threshold must sit for review before execution—no instant approval.

Example: Any AI-suggested vendor contract over $50K triggers a mandatory 24-hour review period before a human can sign off.

Explainable Feedback

AI must explain its reasoning, not just output a result. Every recommendation includes a traceable rationale that a human can interrogate.

Example: AI-suggested code changes include a "Why" section explaining the pattern, alternatives considered, and confidence level.

Step 5

Export your protocol

Your HOZ Protocol Map is generated live below. Copy it to your clipboard, paste it into Confluence/Notion, or share it with your team.

Map Completeness

ContextIncomplete

Archetypes0 selected

Boundary Cards0 / 3 filled

GatePending

Next Steps

Share this map with your team lead
Schedule a quarterly review in your calendar
Link it from your AI usage policy
Revisit when AI capabilities change

hoz-protocol.mdDraft

65 lines · 160 words · 4 sections · Markdown

Complete the gate to unlock copy & download

1# HOZ Protocol Map: [Organization Name]

3> **Team:** [Team Name]

4> **Date:** 2026-06-05

5> **Owner:** [Map Owner]

7---

9## 1. Role Archetypes

11_No archetypes selected._

13---

15## 2. HOZ Boundary Cards

17### Relationship Boundary

19**AI Scope**

20_Not defined._

22**HOZ Ownership**

23_Not defined._

25**Audit Rules**

26_Not defined._

28### Critical Decision Boundary

30**AI Scope**

31_Not defined._

33**HOZ Ownership**

34_Not defined._

36**Audit Rules**

37_Not defined._

39### Conceptual Origin Boundary

41**AI Scope**

42_Not defined._

44**HOZ Ownership**

45_Not defined._

47**Audit Rules**

48_Not defined._

50---

52## 3. Compliance Gate

54- [ ] Redaction: Sensitive outputs are filtered before human review

55- [ ] Rate Limit: High-stakes decisions require cooling-off period

56- [ ] Explainable Feedback: AI must explain reasoning, not just output

58---

60## 4. Reflection

62> *"If a free, basic browser sandbox can map your organizational safety line in under 4 minutes, what excuse do you have for letting automation complacency expose your company's data, culture, or liability?"*

64---

65*Generated via HOZ Protocol Mapping Workspace*

Live · updates as you typeUTF-8 · LF · Markdown

Reflection

"If a free, basic browser sandbox can map your organizational safety line in under 4 minutes, what excuse do you have for letting automation complacency expose your company's data, culture, or liability?"

Want to go deeper?

Join the conversation at theCommons Academy — share your map, learn from other organizations, and refine your HOZ boundaries with a community of practice.

Explore the community