Check the input, then compare the complete deliverables
Explore the original materials, item-by-item outcomes and full report below. Attempt the input independently before using the reference to find omissions or disagreements.
Accounts and biographies are fictional. No X reading, additional search, Notion writing or contact with anyone occurred.
Original synthetic material. Try the input independently, then compare the reference results.
Original synthetic input
{
"synthetic": true,
"case": "notion-personal-crm",
"data": {
"profiles": [
{
"row": "P01",
"account_id": "u101",
"handle": "alpha_demo",
"bio": "Independent developer building open-source tools. Website example.com.",
"city": null
},
{
"row": "P02",
"account_id": "u102",
"handle": "beta_demo",
"bio": "Shanghai. Documenting product design.",
"city": "Shanghai"
},
{
"row": "P03",
"account_id": "u101",
"handle": "alpha_demo",
"bio": "Independent developer building open-source tools. Website example.com.",
"city": null
},
{
"row": "P04",
"account_id": "u103",
"handle": "gamma_demo",
"bio": "Learned something new today.",
"city": null
}
]
}
}Processing rules
Use supplied public biographies only. Infer no city, occupation, income or private contact details. Unpublished city stays null; vague field tags stay unconfirmed. Deduplicate by stable account_id and retain original-row mapping. The placeholder domain is not a verified personal site.
Complete reference results under this tutorial’s rules; nothing was written to a third-party service.Scroll horizontally within the table if needed.
| Identity | Recordable facts | City / field | Handling |
|---|---|---|---|
| u101 | @alpha_demo; example.com placeholder | City unpublished; independent development | Merge P01/P03, retain both sources |
| u102 | @beta_demo; product design notes | Shanghai; product design | From P02 public text only |
| u103 | @gamma_demo; limited biography | City unpublished; field unconfirmed | Do not infer an occupation |
u101/u103 cities stay empty. Language, avatar or activity time is not location evidence.
Two rows for u101 become one record with a reversible P01/P03 source mapping.
Public profile index — fictional accounts 4 original rows, 3 unique identities. u 101 merges P01/P03. u102 publicly states Shanghai. u103 field unconfirmed. Unpublished fields remain blank; website not externally verified; no private contact collection. Local import file only; no Notion write, follow, like or contact.
Prepare the materials and check your tools
Start with the practice files
- Download four biographies and rules.
- Extract facts before tags.
- P01/P03 are one identity.
Before using real services
- Set an authorized public account list and limit.
- Inspect target schema and existing identities read-only.
- Do not fill private gaps through messaging or cross-site searches.
Complete one file-based exercise first. For real services, verify the actual account, available tools and operation scope, then follow the acceptance check at each stage.
Download the original input and rules ↓Execution and takeover boundaries
The actions below require the agreed inputs, accounts and scope. Configuring a Routine does not expand that authorization.
Can run automatically
Organize supplied public-profile snapshots; deduplicate by stable account_id and preserve source text, dates and missing fields.
Requires confirmation
Confirm live read scope and Notion fields to create or update. Import approval does not authorize outreach, sharing or private-information searches.
Take over after a failure
Preserve both sources and times for conflicting fields. After uncertain writes, deduplicate by account_id and read page ids; request human decisions rather than appending the batch again.
Define account scope and field sources
A profile index should save only needed, source-backed fields. Accessible content is not a reason to collect every possible detail.
Read four synthetic biographies. List original row id, account_id, visible fields and allowed source. Use uploaded material only; do not search accounts/sites or contact anyone.A four-row source index.
Original rows and stable identities are distinct.
Extract facts and leave unknowns blank
Public statements differ from model inference. A blank preserves the information boundary instead of inventing a likely answer.
Extract handle, biography, public city and website exactly, with P ids per field. Keep unpublished cities null. Infer no income, occupation or contact details; do not call example.com a verified homepage.A traceable fact table.
Only u102 has a supplied public city.
Assign field tags only from explicit text
Tags are an index, not a professional identity judgment. Vague text does not establish a field or qualification.
Tag u101 independent development and u102 product design with quotations. Mark u103 unconfirmed. Do not force a vague bio into investing or AI. Save tag-map.csv.Three evidence-based tag states.
u103 receives no invented field or occupation.
Deduplicate without losing original mapping
Display names may collide or change. Use stable identity and preserve the collection record.
Merge P01/P03 by account_id. Return3 profiles plus the mapping from 4 original rows. Send conflicting fields to review without silent overwrite. Produce an import file; do not write Notion.Three profiles and source mapping.
All four inputs are accounted for; u101 appears once in final records.
Compare existing identities before a live import
Appending records does not enforce business uniqueness. Inspect the schema and old keys before approving specific writes.
Read <target data source> schema and account_id keys. Preview proposed inserts/updates. After confirmation, write only those items and read back page ids. Check duplicates after unclear failures. If tools are missing, return CSV; do not search private data or send messages.A verified import or local handoff.
Reruns do not create duplicate people or overwrite manual fields.
Date updates and retain removal handling
Public information changes. Review differences with source time rather than silently replacing records.
Draft a public-profile-index Skill with account list, limit, field evidence, blanks, identity deduplication, conflicts and observation times. Default to a diff for review. Do not enrich private fields, bulk update or contact profiles automatically.A maintainable update method.
Old/new sources and dates remain traceable.
Find the evidence before choosing the next action
Too many blank fields
Retain blanks and reasons instead of inferring private details for completeness.
Can identical display names be merged?
Verify stable account identity first.
Fields conflict for one identity
Keep both sources and times for human review.
Notion contains duplicates
Check business keys and actual write results; do not append the batch repeatedly.
Check every item before finishing
These page-local checkboxes reset on refresh. Checking them does not verify a real service connection.
Checked 0 / 6 items
Download the inputs separately from the reference answers
Start with input and rules without showing the reference answers. After acceptance, save the report and complete prompt set.
source-data.json↓Rules and scopeDefinitions, exceptions and delivery requirements.workflow-rules.md↓Item-by-item reference resultsCompare every input with its outcome.expected-results.csv↓Complete reference reportResults, evidence and missing information.reference-report.md↓All stage prompts6 instructions with expected outputs and acceptance checks.practice-prompts.txt↓Check documented capabilities and exercise results separately
Content updated: · Editing a page does not reverify its sources or live workflow.
Documentation review: Unverified · no review date recorded
No case-specific documentation review is recorded. References below are provided for review and do not establish verification.
Live workflow verification: Unverified
Live accounts, external writes, scheduled execution and long-term operation are unverified. Synthetic exercises and page checkboxes do not establish live verification.
Accounts and biographies are fictional. No X reading, additional search, Notion writing or contact with anyone occurred.
- Notion: query a data source ↗
Inspect schema and existing business keys before writing. No live Notion import was performed here.
- Grok Bot: apps and the shared computer ↗
Check connected accounts, available tools, visibility and user takeover.
- Grok Bot: Skills and Routines ↗
Validate a manual run before saving a method or scheduling it.
Try another small batch of your own material
Retain original input and operation records. Verify that each result can be traced before adding connections or recurring runs.