Worked example
What credit should Kinfolk Observatory give to a tool its builders consulted and to a similar feature they learned about afterward?
Source notes
Use Steve Little’s account in Every Idea Has Ancestors. He reports that the builders consulted B. F. Lyon’s Exploring Family Trees. Jonny Perl’s DNA Painter already highlighted repeated appearances of an ancestor in a fan chart. Steve says he learned of that feature after the Observatory built its own.
Observed result
Credit Finder classified Lyon’s project as a reported direct influence and Perl’s fan feature as an earlier example. It kept both findings unverified in the offline report. The distinction lets an editor acknowledge the prior feature without claiming the builders copied it, saw it during development, or know what entered an AI model’s training.
What this establishes
The run used an attributed paraphrase of Steve’s account and did not independently establish precedence. The release’s optional checker flagged references to uncertain findings in its ready-to-paste section. Review the wording before reuse.
Next research step
Read Steve’s article and follow its credit trail. Check the earlier feature and the project’s own development record before upgrading either finding or publishing a definitive credit line.
Sources and verification
- Steve Little, Every Idea Has Ancestors
- Kinfolk Observatory, the published chart history and credit roll
Credit Finder v1.3.2 ran in Quick mode in Claude Code using an offline source extract. Its output and the bundled checker’s failure were saved. This tested classification and uncertainty handling on the reported historical case.
How the skill was tested
The released skill was also exercised in two fresh Codex sessions. On a harder atlas case, the optional checker rejected local evidence links and finding IDs in proposed research tasks. Check the underlying sources before using a proposed credit line.