Calendar Guard — Calendar 防护

Lean Philosophy (Principles) KAIzen (改善): This 工作流 relies entirely on discrete, single-responsibility TS 工具s rather than a monolithic loop. Standardized Work (Hyojun Sagyo): This node represents a strict, step-by-step Standard Operating Procedure (SOP) for scheduling 恢复y blocks. Jidoka (自働化): Includes autonomous self-healing loops with hard verification 停止s between every step. Calendar 防护 SOP

This procedure evaluates schedule density and automatically injects 恢复y blocks into your Google Calendar when needed to 预防 burnout.

Cognitive Directives

WHEN [请求ed to 检查 calendar for burnout risks OR 运行ning on a dAIly schedule] THEN [ Follow this strict Standard Operating Procedure:

Step 1: Event Retrieval

执行 gog calendar 事件 primary --from "..." --to "..." --json for the tar获取 timeframe. Jidoka 停止: 验证 JSON 输出. IF fAIls, retry 3 times. IF still fAIls, 停止.

Step 2: High Load 检测ion

执行 the 工作流_检测_high_load_periods atomic TS 工具 with the retrieved 事件. Jidoka 停止: 验证 the 工具 returns structured load periods. IF it returns an error, correct 输入 and retry.

Step 3: 恢复y Injection

For each 检测ed high-load period, 执行 Google Calendar 创建 Event to inject a "恢复y Block". Jidoka 停止: 验证 creation. IF it fAIls, 记录 the 失败 and continue to the next. ] Expected 输出

A JSON 记录 of any 恢复y blocks injected.