Optional source-rights evidence node before web extraction #1166
reflectme-source
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I was looking at ScrapeGraphAI’s graph-based scraping model and the existing custom-node / API / SDK / MCP integration surfaces.
For public-web extraction pipelines, one optional graph node could add source-rights evidence before or alongside extraction:
URL + intended purpose -> evidence provider -> existing scrape/extract graph -> structured output + evidence referenceI’m building AcqPath as one provider for that step. It observes machine-readable source-rights/TDM declarations for a public URL + intended purpose and returns a signed, timestamped receipt.
Important boundary: the receipt is not a license or legal clearance. ScrapeGraphAI and downstream customers keep their own policy logic; this is only an external evidence record that can travel with the result.
The useful abstraction would be provider-neutral: an optional evidence/enrichment node or hook returning normalized metadata (provider, observation time, declaration state, receipt digest/verification reference).
Would a custom graph node be the preferred extension point for this, or is there a lower-level preprocessing/enrichment hook that would fit better? I can provide a minimal async node contract/fixture if useful.
All reactions