# Family Calendar Agent Permission Ladder Prompt

> A reusable prompt that turns a household's own rules into a read / propose / edit permission ladder for a shared family calendar agent.

## Install

Copy the content below into your project:

# Family Calendar Agent Permission Ladder Prompt

A reusable prompt that turns a household's own rules into a read / propose / edit permission ladder for a shared family calendar agent.

## Start here

You paste one block of text into an ordinary AI chat that accepts text (any assistant with a normal message box). No terminal, account connection or API setup is needed.

**Input to paste:**
1. Household members and each role; mark one or two decision makers.
2. The calendar's name and where it lives, or write "location unknown".
3. The calendar actions you care about (view, add, move, cancel, invite, recurring events, private/medical events, delete history, share with an outsider).
4. For each action: who may see it, who may request it, who must approve it.
5. Hard limits: events never to touch, people never to contact, frozen times, and what to do when the user is unreachable.
6. What the agent should do when unsure.

Paste the full prompt text below, then your own answers. If an item is missing, the prompt tells the assistant to mark it "TO BE CONFIRMED" instead of inventing it.

**How to check the output:** confirm the table lists each action exactly once; every edit row names an authorizer and a scope; every propose row names a human approver; hidden areas are named; missing items are marked TO BE CONFIRMED; and the text never claims an action was already performed.

## Introduction

This prompt helps a household write down what an agent may do with a shared family calendar before anyone configures it. It produces a compact policy: read, propose and edit tiers, escalation and stop rules, review and revocation, and open questions. It is a draft policy, not a configured agent.

## Prerequisites, permissions and limits

- No login, no real calendar access, no invites, no event changes. The assistant only drafts policy text from your input.
- Use plain names or roles, not IDs.
- Do not give legal, medical or safety advice; the prompt does not decide custody, consent or privacy rules for you.
- If the household is not using an agent, the same prompt returns a printed agreement plus a short manual weekly routine.
- Source reviewed; runtime not tested.

## FAQ

**What if I don't know where the calendar lives?** Write "location unknown". The prompt keeps that as a stated fact instead of guessing.

**Can I use the result as-is?** The output is a draft for the family and the person configuring the agent. Confirm every TO BE CONFIRMED item first.

## Source and thanks

Original TokRepo prompt, category: everyday agents. Licensed CC BY 4.0. Reference context: [ChatGPT release notes](<https://help.openai.com/en/articles/6825453-chatgpt-release-notes>). The complete prompt and reference note are appended separately.

## Complete reusable prompt

# Permission Ladder for a Shared Family Calendar Agent

You help a household write down what an agent may do with their shared family calendar. The result is a permission ladder the family can review and then hand to whoever configures the agent. You do not log in, read a real calendar, send invites, or change any event. You only draft the policy text from what the user gives you.

## What the user must supply
1. Household members and, for each, their role (for example: parent/admin, teen, child, grandparent, caregiver). Mark one or two as the decision makers who can grant permission.
2. The calendar's name and where it lives, if the user knows (for example: a shared online calendar, a paper wall calendar, a calendar app on one phone). If unknown, write "location unknown".
3. A list of typical calendar actions the family cares about. Examples: view events, add an appointment, move an event, cancel an event, invite someone, create a recurring event, add a private/medical appointment, delete history, share the calendar with an outsider.
4. For each action, who is allowed to see it, who may request it, and who must approve it.
5. Any hard limits: events the agent must never touch, people the agent must never contact, times when changes are frozen (for example, during a school week), and what should happen when the user is unreachable.
6. What the agent should do when it is unsure (for example: stop and ask a named person, or leave a note in a review queue).

If any item is missing, do not invent it. List what is missing and produce a ladder that marks those cells "TO BE CONFIRMED".

## Build the ladder in three tiers
For every action in item 3, classify it into exactly one tier:

**Tier 1 — Read (agent may see, never change).** State which calendar areas are visible, which are hidden (for example: private or medical events), and that read access never implies permission to edit.

**Tier 2 — Propose (agent may prepare, a human decides).** The agent may draft a suggested event, a suggested move, or a suggested cancellation, but it must not apply it. Each proposal needs: what would change, why, the source of the request, the proposed time, and the named human approver. Say plainly that the agent cannot approve its own proposal.

**Tier 3 — Edit (agent may change, within named bounds).** Only list actions the family has explicitly approved. For each, name: the exact action, who authorized it, the scope (which calendar, which date range, which members), any required second confirmation, and the freeze periods when edit is suspended. If the family has not approved an edit tier for an action, write "no edit permission — propose only".

Add a short **Escalation and stop rules** section: when the agent must pause, who it asks, how long it waits, and what it records. Include a rule that the agent must not act when the request is ambiguous, comes from an unlisted person, or falls outside the stated scope.

Add a **Review and revocation** section: how often the family reviews the ladder, who can lower or remove a tier, and that lowering a tier takes effect immediately.

## Manual alternative (no agent connected)
If the household is not using an agent yet, output the same ladder as a printed household agreement plus a short manual routine: who checks the shared calendar each week, how change requests are written down, who approves them, and how approvals are recorded. This keeps the same tiers without any automation.

## Output format
Use Markdown with these headings in order:
1. Household and decision makers
2. Calendar and scope
3. Permission ladder table (columns: Action | Tier | Who may request | Who must approve | Limits)
4. Escalation and stop rules
5. Review and revocation
6. Open questions and TO BE CONFIRMED items
7. Manual routine (if used instead of an agent)

Keep it compact enough to read in one sitting. Use plain names or roles, not IDs.

## Worked example (fictional, for shape only)
User input: "Family of four. Mom and Dad are decision makers. Teen has their own events. Shared calendar on a phone app. Actions: view events, add appointment, move appointment, cancel appointment, invite grandparent, add medical appointment. Rule: no changes during school nights. If unsure, ask Mom."

Illustrative output shape:
- Action: View events | Tier 1 Read | Who may request: all members | Who must approve: none | Limits: medical events hidden from teen
- Action: Add appointment | Tier 2 Propose | Who may request: any member | Who must approve: Mom or Dad | Limits: agent drafts only, no auto-add
- Action: Cancel appointment | Tier 3 Edit | Who may request: Mom or Dad | Who must approve: Mom or Dad plus a second confirmation | Limits: never cancel medical or school events; frozen on school nights
- Escalation: if the request is unclear or from an unlisted person, pause and ask Mom; record the pause in a review note
- Open question: is the grandparent invite an edit or a proposal? Marked TO BE CONFIRMED.

## Checks before the family uses it
Run these against the user's own inputs and say pass or fail for each:
1. Every action from item 3 appears once and only once in the table.
2. No action is placed in Tier 3 unless the user named an authorizer and a scope.
3. Every Tier 2 row names a human approver and states that the agent cannot self-approve.
4. Hidden areas are named in Tier 1, not left vague.
5. Missing inputs are marked TO BE CONFIRMED rather than filled in.
6. The stop rule covers ambiguity, unlisted requesters, and out-of-scope requests.
7. The text never claims the agent has already read, changed, invited, or scheduled anything.
If any check fails, fix the ladder and re-run the checks before presenting it.

## Boundaries
- This is a draft policy, not a configured agent. Preparing it does not grant access, connect an account, send invitations, or change a calendar.
- Do not give legal, medical, or safety advice, and do not decide custody, consent, or privacy rules for the family.
- Do not invent features of any calendar product or assume what a tool can do.
- If the family describes a conflict or risk you cannot resolve from their inputs, surface it as an open question and stop there.


## References and reuse

- [ChatGPT release notes](https://help.openai.com/en/articles/6825453-chatgpt-release-notes) · Reviewed 2026-10-04

Original TokRepo prompt · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Reference documents retain their own rights.

---

<!-- ZH -->

# 家庭共享日历智能体权限阶梯提示词

一套可复用提示词，把家庭自己提供的规则整理成共享家庭日历智能体的“只读 / 提议 / 编辑”三级权限阶梯。

## 开始使用

把一段文字粘贴进普通的、能接受文本的 AI 聊天窗口即可（任何有正常输入框的助手）。不需要终端、账号连接或 API 设置。

**需要粘贴的输入：**
1. 家庭成员及各自角色；标出一两位决策人。
2. 日历名称和存放位置，不知道就写“位置未知”。
3. 你在意的日历操作（查看、新增、移动、取消、邀请、重复事件、私密/医疗事件、删除历史、分享给外人）。
4. 每个操作：谁能看到、谁可以提出、谁必须批准。
5. 硬性限制：绝不触碰的事件、绝不联系的人、冻结时段、联系不上用户时怎么办。
6. 智能体不确定时该做什么。

把下面提示词全文和你自己的答案一起粘贴。若某项缺失，提示词会要求助手标注“待确认”，而不是自行编造。

**如何检查输出：** 确认表中每个操作只出现一次；每条编辑行都写明了授权人和范围；每条提议行都写明人工批准人；隐藏区域被具名；缺失项标注为待确认；全文没有声称某项操作已经执行。

## 简介

这套提示词帮助家庭在配置之前，先写下智能体对共享家庭日历可以做什么。输出是一份紧凑的政策：只读、提议、编辑三级，升级与停止规则，复核与撤销，以及待确认问题。它是政策草稿，不是已配置的智能体。

## 前提、权限与限制

- 不登录、不读取真实日历、不发邀请、不改事件。助手只根据你的输入起草政策文本。
- 使用普通姓名或角色，不要用编号。
- 不提供法律、医疗或安全建议；提示词不会替你决定监护、同意或隐私规则。
- 如果家里还没用智能体，同一提示词会输出一份打印版约定和一份简短的人工每周流程。
- 已审阅来源；未做运行测试。

## 常见问题

**不知道日历放在哪里怎么办？** 写“位置未知”。提示词会把它作为已知事实保留，而不是猜测。

**结果可以直接用吗？** 输出是供家庭和配置者使用的草稿。请先确认所有待确认项。

## 来源与致谢

TokRepo 原创提示词，分类：日常智能体。许可协议 CC BY 4.0。参考背景：[ChatGPT release notes](<https://help.openai.com/en/articles/6825453-chatgpt-release-notes>)。完整提示词与参考说明单独附上。

## 完整可复制提示词

# 共享家庭日历智能体的权限阶梯

你帮助一个家庭写下智能体可以对其共享家庭日历做什么。结果是一份权限阶梯，家庭可以审阅，然后交给配置该智能体的人。你不登录、不读取真实日历、不发邀请、也不更改任何事件。你只根据用户提供的内容起草政策文本。

## 用户必须提供的内容
1. 家庭成员，以及每人的角色（例如：家长/管理员、青少年、儿童、祖父母、照护者）。标出一两位可以授予权限的决策人。
2. 日历的名称和存放位置（如果用户知道的话）（例如：共享在线日历、纸质墙挂日历、某部手机上的日历应用）。如果不知道，写“位置未知”。
3. 家庭在意的典型日历操作清单。例如：查看事件、新增预约、移动事件、取消事件、邀请某人、创建重复事件、添加私密/医疗预约、删除历史、把日历分享给外人。
4. 每个操作：谁可以看到、谁可以提出、谁必须批准。
5. 任何硬性限制：智能体绝不能触碰的事件、绝不能联系的人、更改被冻结的时段（例如上学期间），以及联系不上用户时该怎么办。
6. 智能体不确定时该做什么（例如：停下来询问指定的人，或在复核队列中留下一条备注）。

如果任何一项缺失，不要编造。列出缺失项，并生成一份将那些单元格标注为“待确认”的阶梯。

## 分三层构建阶梯
对第 3 项中的每个操作，将其归类到且仅归类到一个层级：

**第 1 层——只读（智能体可以查看，绝不更改）。** 说明哪些日历区域可见、哪些隐藏（例如：私密或医疗事件），并说明只读权限绝不意味着可以编辑。

**第 2 层——提议（智能体可以准备，由人决定）。** 智能体可以起草建议的事件、建议的移动或建议的取消，但不得应用它。每项提议需要：会改什么、为什么、请求来源、建议时间，以及指定的人工批准人。明确说明智能体不能批准自己的提议。

**第 3 层——编辑（智能体可以在指明的边界内更改）。** 只列出家庭已明确批准的操作。对每个操作，写明：确切操作、谁授权、范围（哪个日历、哪个日期范围、哪些成员）、任何必需的二次确认，以及编辑被暂停的冻结时段。如果家庭尚未为某个操作批准编辑层级，写“无编辑权限——仅限提议”。

添加一个简短的**升级与停止规则**部分：智能体何时必须暂停、询问谁、等待多久，以及记录什么。加入一条规则：当请求含糊不清、来自未列出的人，或超出所述范围时，智能体不得行动。

添加一个**复核与撤销**部分：家庭多久复核一次阶梯、谁可以降低或移除某个层级，以及降低层级立即生效。

## 人工替代方案（未连接智能体）
如果家里还没用智能体，就把同一份阶梯输出为一份打印版家庭约定，外加一份简短的人工流程：谁每周检查共享日历、更改请求如何写下、谁批准，以及批准如何记录。这样可以在没有任何自动化的情况下保持同样的层级。

## 输出格式
使用 Markdown，按顺序包含以下标题：
1. 家庭与决策人
2. 日历与范围
3. 权限阶梯表（列：操作 | 层级 | 谁可以提出 | 谁必须批准 | 限制）
4. 升级与停止规则
5. 复核与撤销
6. 待确认问题与待确认项
7. 人工流程（如果用来替代智能体）

保持足够紧凑，以便一口气读完。使用普通姓名或角色，不要用编号。

## 示例（虚构，仅示意结构）
用户输入：“四口之家。妈妈和爸爸是决策人。青少年有自己的事件。共享日历在手机应用上。操作：查看事件、新增预约、移动预约、取消预约、邀请祖父母、添加医疗预约。规则：上学日晚上不做更改。不确定时，问妈妈。”

示意输出结构：
- 操作：查看事件 | 第 1 级 只读 | 谁可以提出：所有成员 | 谁必须批准：无 | 限制：医疗事件对青少年隐藏
- 操作：新增预约 | 第 2 级 提议 | 谁可以提出：任何成员 | 谁必须批准：妈妈或爸爸 | 限制：智能体只起草，不自动添加
- 操作：取消预约 | 第 3 级 编辑 | 谁可以提出：妈妈或爸爸 | 谁必须批准：妈妈或爸爸加二次确认 | 限制：绝不取消医疗或学校事件；上学日晚上冻结
- 升级：如果请求不清楚或来自未列出的人，暂停并询问妈妈；把暂停记录到复核备注中
- 待确认问题：邀请祖父母属于编辑还是提议？标注为待确认。

## 家庭使用前的检查
针对用户自己的输入运行这些检查，并逐项说明通过或失败：
1. 第 3 项中的每个操作在表中出现一次且仅出现一次。
2. 除非用户指定了授权人和范围，否则不得把任何操作放入第 3 级。
3. 每条第 2 级行都写明人工批准人，并说明智能体不能自行批准。
4. 隐藏区域在第 1 级中具名，而不是含糊带过。
5. 缺失输入标注为待确认，而不是补写。
6. 停止规则覆盖含糊不清、未列出的请求者和超出范围的请求。
7. 全文没有声称智能体已经读取、更改、邀请或安排过任何事情。
如果任何检查失败，先修正分级梯，并重新运行检查，再呈现出来。

## 边界
- 这是政策草稿，不是已配置的智能体。起草它不会授予访问权限、连接账号、发送邀请或更改日历。
- 不提供法律、医疗或安全建议，也不替家庭决定监护、同意或隐私规则。
- 不要编造任何日历产品的功能，也不要假设某个工具能做什么。
- 如果家庭描述了根据其输入无法解决的冲突或风险，将其作为待确认问题提出，并就此停止。

## 参考资料与复用

- [ChatGPT release notes](https://help.openai.com/en/articles/6825453-chatgpt-release-notes) · Reviewed 2026-10-04

TokRepo 原创提示词 · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)。参考资料保留各自原有权利。

---
Source: https://tokrepo.com/en/workflows/family-calendar-agent-permission-ladder-prompt-7db383c6
Author: Prompt Lab