notion-personal-space-audit

ports belong in a separate high-sensitivity archive; short event logs retain event records; raw conversations remain source material and link to derived decisions.
9. **[LLM]** Recommend minimal shared fields: content type, domain, status, occurrence date, organization date, sensitivity, and relations. Do not force one schema onto all content types.
10. **[LLM]** Produce a concise Markdown report with evidence, signal-light findings, proposed tree, migration table, phased migration order, and a clear statement that no Notion content was changed.
11. **[LLM]** If the user explicitly authorizes structure creation, create only empty navigation pages and usage instructions after the audit. Never move, delete, rename, or rewrite existing content unless separately authorized.
12. **[LLM]** If the user explicitly authorizes updating an existing audit/guide page, append a clearly marked usage-notes section rather than replacing prior findings; make the write idempotent with a unique marker and

1. Read-only by default: no Notion write endpoint is called unless the user explicitly authorizes structure creation or updating an existing guide page; authorized guide-page updates must append rather than replace.
2. Never move, delete, rename, or rewrite existing content as part of an audit or structure setup.
3. Never expose access tokens in reports, logs, or user-facing output.
4. Do not invent content the API did not return; mark inaccessible or uncertain areas explicitly.
5. Sensitive analysis reports are never classified as ordinary log events, and never merged into general archives.

- Do not merge raw conversations, derived reports, and action plans into one record. Keep source, analysis, and action linked but distinct.
- Do not delete empty book/person placeholders during an audit. Put them in an archive or pending-review view first.
- Orphan pages not under any database are easy to miss; enumerate workspace top-level nodes first and recurse. Do not rely on database enumeration alone.
- Do not expose access tokens in reports, logs, or user-facing output.
- Do not modify Notion without explicit confirmation. The audit should produce a migration plan first.
- When structure creation is authorized, use idempotent title checks and create pages under the audited parent; do not move, delete, rename, or rewrite existing content as part of structure setup.
- Notion block append requests must be chunked to at most 100 blocks; use a unique marker to prevent duplicate guide sections, and verify by reading back the full child-block list rather than trusting the write respons