Feature idea: attach signed source-rights observations to provenance records
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- backend-api-design
Research direction
Start by reviewing the project’s existing provenance, lineage, and registry interfaces; the issue does not name specific files or tests. Compare those interfaces with the proposed MCP endpoint and x402 preflight payload, then clarify whether a provider-neutral evidence hook fits and what project-specific schema or example would demonstrate completion.
Written by the indexing model from the issue text.
Description
Hi - I am building AcqPath, a narrow rights-observation layer for AI data workflows.
For provenance, lineage, registry, or AI-BOM workflows, the useful addition is an external evidence record describing what machine-readable AI-use or rights declaration was observed at the source and when.
Current public interfaces:
- MCP: https://api.getacqpath.com/mcp
- stock x402 preflight: POST https://api.getacqpath.com/v1/rights/preflight/x402
- fresh preflight price: 0.02 USDC on Base
- intended-use values: ai-input, ai-index, ai-train, search
The output is signed observation evidence with source/time context. It does not grant a licence, determine ownership, prove actual use, bypass access controls, or turn UNKNOWN into permission. Coverage is intentionally limited to reviewed origins today.
Would a provider-neutral external evidence hook of this kind fit this project? If yes, I can provide a minimal payload/schema or a project-specific example rather than asking for a broad dependency.
- Dominant language
- Python
- Stars
- 43
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ORNL/flowcept
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
DocumentInserter drops whole task batches when a payload key contains a dotPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Dependency-mgmt devops priority:low
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 50/100
-
code-enhancement
Difficulty 3/5 1-2 days Newbie friendliness 25/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Netcracker/qubership-ai-packages#266 ·
Maintainers usually reply within 1 day
-
PROCESSED_DATA_FOLDER: strip whitespace and treat empty as unsetPossibly taken @TorecLuik claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
NL-BioImaging/BIOMERO.importer#63 ·
Maintainers usually reply within 1 day
-
MLX training-complete chat/merge suggestions omit --backend mlxPossibly taken @vaputa claimed this today. Openneeds-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
MakazhanAlpamys/Soup#2913 · 1 comment ·
Maintainers usually reply within 1 day
-
area:security effort:S priority:P3 status:needs-triage type:chore
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
randomparity/kdive#3657 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
aws/mcp-proxy-for-aws#476 ·
Maintainers usually reply within 1 day