Why fact extraction and published claims stay separate in ProfileScribe
Abstracts
Abstracts
One design choice in ProfileScribe worth calling out: the crawler agent that reads approved public links never writes directly to a profile. It normalizes what it finds into timestamped facts, and those facts sit in a review queue before anything becomes a public claim.
That separation exists because scattered professional evidence (a repo, a link, a mention) is not the same thing as a credible statement about someone's work. Collapsing the two steps is how profiles end up overstated. Keeping extraction and publishing distinct is slower, but it is what makes the eventual post something a professional can actually stand behind.