Define Notion data source property schema

[thxforall]

ISSUE-001: Define Notion data source property schema

Goal

Define the Notion data source property schema for AI-generated meeting and Telegram summaries.

This issue locks the write-back contract before implementing the webhook worker.

Scope

1. Summary data source

Required properties:

Property	Type	Required	Notes
Title	title	yes	Meeting or digest title
Source Type	select	yes	meeting_audio, telegram_digest
Period Start	date	yes	Source period start
Period End	date	yes	Source period end
Summary	rich_text	yes	Human-readable summary
Topics	multi_select	no	Main topics
Decisions	rich_text	no	Short decision summary only
Risks	rich_text	no	Risk summary
Participants	multi_select	no	Human-reviewed names only
Review Required	checkbox	yes	True if any uncertainty exists
Review Status	status	yes	Needs Review, Reviewed, Published, Blocked
Raw Transcript URL	url	no	Object storage link
Trace ID	rich_text	yes	Idempotency / replay tracking
Model Name	rich_text	yes	Model used for extraction
Created At	created_time	yes	Notion managed
Last Edited At	last_edited_time	yes	Notion managed

2. Action Items data source

Required properties:

Property	Type	Required	Notes
Task	title	yes	Action item text
Summary	relation	yes	Relation to Summary data source
Owner	people / rich_text	no	Use rich_text if Notion users are not guaranteed
Due Date	date	no	Nullable
Status	status	yes	Todo, Doing, Done, Blocked, Needs Review
Confidence	number	yes	0.0-1.0
Evidence	rich_text	yes	Short source quote or paraphrase
Review Required	checkbox	yes	True if low confidence or unclear owner/date
Source Type	rollup	yes	From related Summary
Trace ID	rollup or rich_text	yes	Prefer rollup from Summary
Created At	created_time	yes	Notion managed
Last Edited At	last_edited_time	yes	Notion managed

Relation / Rollup Strategy

• Summary data source has many Action Items.
• Action Items must relate back to exactly one Summary.
• Action Items roll up:
  • Source Type
  • Period Start
  • Period End
  • Trace ID

Views

Summary data source views

1. Needs Review

   • Filter: Review Required = true OR Review Status = Needs Review

2. Published

   • Filter: Review Status = Published

3. By Source Type

   • Group by Source Type

4. Recent

   • Sort by Period End DESC

Action Items data source views

1. Needs Review

   • Filter: Review Required = true OR Status = Needs Review

2. Open Tasks

   • Filter: Status != Done

3. By Owner

   • Group by Owner

4. Due Soon

   • Filter: Due Date is within next 7 days
   • Sort by Due Date ASC

Config Contract

NOTION_SUMMARY_DATA_SOURCE_ID=
NOTION_ACTION_ITEMS_DATA_SOURCE_ID=
NOTION_INTEGRATION_SECRET_REF=

Acceptance Criteria

• Summary data source property schema is defined.
• Action Items data source property schema is defined.
• Relation between Summary and Action Items is defined.
• Required rollups are defined.
• Review views are defined.
• Config contract uses data_source_id.
• Schema supports idempotency via trace_id.
• Schema avoids storing full transcript in Notion.
• Owner field strategy is decided: people vs rich_text.

[thxforall]

ISSUE-001 finalization notes before creating the Notion data sources.

Locked decisions

• Use two Notion data sources:
  • Summary data source
  • Action Items data source
• Production implementation must use data_source_id, not database_id.
• Production write-back uses @notionhq/client and a Notion API integration token from secret manager.
• Do not store full raw audio, full transcript, diarization debug dumps, or sensitive raw messages in Notion.
• Use object storage URLs for raw transcript references.

Owner field decision

Use rich_text for Owner in MVP.

Reason:

• Telegram users and meeting speakers are not guaranteed to map to Notion workspace users.
• Speaker attribution is evidence-ranked and must not auto-confirm real person identity.
• A later migration can add an optional Notion people field after identity mapping is reliable.

Optional future property:

• Owner User as people, nullable, human-reviewed only.

Required implementation config

NOTION_SUMMARY_DATA_SOURCE_ID=
NOTION_ACTION_ITEMS_DATA_SOURCE_ID=
NOTION_INTEGRATION_SECRET_REF=

Manual creation checklist

1. Create Summary data source.
2. Create Action Items data source.
3. Add relation from Action Items to Summary.
4. Add rollups on Action Items:
   • Source Type
   • Period Start
   • Period End
   • Trace ID
5. Create Summary views:
   • Needs Review
   • Published
   • By Source Type
   • Recent
6. Create Action Items views:
   • Needs Review
   • Open Tasks
   • By Owner
   • Due Soon
7. Capture both data source IDs.
8. Store the Notion integration token in secret manager and record only NOTION_INTEGRATION_SECRET_REF.
9. Share both data sources/pages with the Notion integration.

Worker implementation remains blocked until

• NOTION_SUMMARY_DATA_SOURCE_ID is available.
• NOTION_ACTION_ITEMS_DATA_SOURCE_ID is available.
• NOTION_INTEGRATION_SECRET_REF is available.

[thxforall]

Notion data source creation result (2026-05-07)

Created under Notion page: Decoded AI Summary Writeback Schema

• Page URL: https://www.notion.so/3595b97b3d4281c3bcedd5795ec44b95

Created data sources:

• Meeting Summaries
  • Database URL: https://www.notion.so/0a4904bdb8124a709a34eaefacd1e5e1
  • NOTION_SUMMARY_DATA_SOURCE_ID=b6991f03-6b48-43ca-8e14-d005fdc0c78b
• Action Items
  • Database URL: https://www.notion.so/b0733c829009430a998017331945a03f
  • NOTION_ACTION_ITEMS_DATA_SOURCE_ID=4c6bb959-5b2c-414f-bd32-5c560ced1800

Schema notes:

• Summary properties created: Title, Source Type, Period Start, Period End, Summary, Topics, Decisions, Risks, Participants, Review Required, Review Status, Raw Transcript URL, Trace ID, Model Name, Created At, Last Edited At.
• Action Items properties created: Task, Summary relation, Owner, Due Date, Status, Confidence, Evidence, Review Required, Source Type rollup, Period Start rollup, Period End rollup, Trace ID rollup, Created At, Last Edited At.
• Owner strategy: rich_text for MVP.
• Raw transcript/audio is not stored in Notion; only Raw Transcript URL is present.

Views created:

• Meeting Summaries: Needs Review, Published, By Source Type, Recent.
• Action Items: Needs Review, Open Tasks, By Owner, Due Soon.

Manual follow-up still required:

• Notion MCP created status-type properties, but left workspace-default status labels in Korean. Manually configure Summary Review Status options to: Needs Review, Reviewed, Published, Blocked.
• Manually configure Action Items Status options to: Todo, Doing, Done, Blocked, Needs Review.
• Re-check status-based view filters after the manual status option rename. The checkbox-based Needs Review views are active; status-based filters were not fully applied by MCP.
• Due Soon view currently sorts by Due Date; manually add the next-7-days filter if required in the Notion UI.
• Share both data sources/pages with the production Notion integration.
• Store the production Notion API token in secret manager and record NOTION_INTEGRATION_SECRET_REF. Codex did not receive or store the token value.

Config values currently available:

NOTION_SUMMARY_DATA_SOURCE_ID=b6991f03-6b48-43ca-8e14-d005fdc0c78b
NOTION_ACTION_ITEMS_DATA_SOURCE_ID=4c6bb959-5b2c-414f-bd32-5c560ced1800
NOTION_INTEGRATION_SECRET_REF=<pending secret-manager entry>

ISSUE-002 / #474 unblock assessment:

• Still blocked until NOTION_INTEGRATION_SECRET_REF exists and the production integration access is verified.
• Worker implementation should stay in a separate branch/worktree after those values are confirmed.

[thxforall]

Secret ref update (2026-05-07)

Confirmed GitHub Actions secret exists:

NOTION_INTEGRATION_SECRET_REF=NOTION_INTEGRATION_TOKEN

Current config contract values:

NOTION_SUMMARY_DATA_SOURCE_ID=b6991f03-6b48-43ca-8e14-d005fdc0c78b
NOTION_ACTION_ITEMS_DATA_SOURCE_ID=4c6bb959-5b2c-414f-bd32-5c560ced1800
NOTION_INTEGRATION_SECRET_REF=NOTION_INTEGRATION_TOKEN

Remaining before closing #473:

• If the token value was ever pasted into chat/logs, rotate it in Notion and re-run gh secret set NOTION_INTEGRATION_TOKEN --repo decodedcorp/decoded with the new value.
• Share both Notion databases with the production integration.
• Verify token access with @notionhq/client against both data source IDs.
• Finish manual Notion UI cleanup for status option labels and status-based view filters.

[thxforall]

Status update (2026-05-07): secret ref and integration assumption are now available.

NOTION_SUMMARY_DATA_SOURCE_ID=b6991f03-6b48-43ca-8e14-d005fdc0c78b
NOTION_ACTION_ITEMS_DATA_SOURCE_ID=4c6bb959-5b2c-414f-bd32-5c560ced1800
NOTION_INTEGRATION_SECRET_REF=NOTION_INTEGRATION_TOKEN

Notion connection observed by user:

• kiyori, available to anyone in BKY Notion.

#474 can proceed to implementation-ready with the first worker task being an @notionhq/client access smoke test. #473 remains open only for final Notion UI cleanup if needed: status option labels and status-based view filters.

[thxforall]

Acceptance evidence update (2026-05-07): production-token access smoke passed.

Confirmed config:

NOTION_SUMMARY_DATA_SOURCE_ID=b6991f03-6b48-43ca-8e14-d005fdc0c78b
NOTION_ACTION_ITEMS_DATA_SOURCE_ID=4c6bb959-5b2c-414f-bd32-5c560ced1800
NOTION_INTEGRATION_SECRET_REF=NOTION_INTEGRATION_TOKEN

Smoke result:

• NOTION_INTEGRATION_TOKEN can query Meeting Summaries.
• NOTION_INTEGRATION_TOKEN can query Action Items.
• Both returned sampled 0 page(s), which is expected before worker write-back exists.

Remaining optional UI cleanup only:

• Status option labels and status-based view filters may still need final Notion UI adjustment if the workspace-default Korean labels remain.

[thxforall]

Closing as superseded by the Notion -> Obsidian direction tracked in #520/#518. Historical Notion schema/access evidence remains in this thread, but this is no longer the active implementation path.