Why ProfileScribe separates fact extraction from published claims
Abstracts
Abstracts
One design choice in ProfileScribe: the crawler agent that reads approved sources never writes directly to a public profile. It normalizes what it finds into timestamped facts first, and those facts sit in a review queue before anything becomes a claim someone can read.
That separation exists because scattered professional work (links, repos, writing) is easy to mis-summarize if extraction and publishing happen in the same step. Keeping them apart makes it possible to check a claim against its source before it goes live, rather than after.
It is a small architectural decision, but it is the one that makes the rest of the system worth trusting.