Notion Ops

Operate Notion as a reliable execution system for multi-agent and human workflows.

Core Outcomes

• Keep Total tasks as the single source of execution truth.

• Enforce immutable Work Logs for every status transition.

• Enforce signature policy for AI and human actors.

• Preserve deterministic continuation across MCP clients.

• Keep handoff, context, and approval chains auditable.

Execution Workflow

1. Audit Baseline

• Verify required databases and relations.

• Verify role model (Orchestrator , Planner , Executor , Reviewer , Human Supervisor ).

• Verify template quality and required task fields.

• Verify continuity chain (Runs , Handoffs , Context Packets ).

Use: references/database-contracts.md

2. Harden Template Layer

• Keep one canonical SOP template for governance.

• Maintain specialized templates (AI solo, incident, research, supervisor).

• Ensure template defaults are safe:

• Status=Backlog

• Signature Status=Missing for AI-capable templates

• Interoperability=Ready

• explicit Policy Version

Use: references/operating-model.md

3. Operate Task Lifecycle

• Fill mandatory fields before Ready .

• Create first work log before In progress .

• Attach evidence before review gates.

• Enforce signatures and approvals before Done .

• If blocked, publish blocker owner and next action immediately.

Use: references/checklists.md

4. Maintain MCP Continuity

• On pause/transfer, publish one Handoffs record.

• Keep one Context Packets record marked Current .

• Include executable Resume Command and Next Action .

• Link active task to client profile and context/handoff records.

Use: references/mcp-continuation.md

5. Run Daily Control

• Check signature compliance.

• Check transition-log completeness.

• Check unresolved blockers and aging In progress tasks.

• Check open approvals and stale context packets.

Non-Negotiable Rules

• Never move AI-executed work to Done without valid AI signature.

• Never change task status without a matching Work Logs entry.

• Never transfer work across clients without handoff + context update.

• Never close incidents without mitigation proof and follow-up actions.

Output Contract

When reporting work, return:

• Current State : concise health snapshot.

• Actions Performed : exact updates and affected artifacts.

• Compliance Gaps : signature/log/approval/continuity misses.

• Next Actions : ordered commands for immediate continuation.

Failure Handling

• Relation mismatch: fetch schema and map exact property names before writing.

• Ambiguous selection update: use unique snippets or replace full content.

• Rate limits: switch to direct page fetches by ID and continue incrementally.

• Partial continuity data: freeze status advancement, then repair handoff/context links.

References

• Database Contracts

• Operating Model

• Execution Checklists

• MCP Continuation