Exact Git-tracked sourcedocs/CREDITS_AND_CONTRIBUTIONS.md View exact source

Credits and contribution policy

Ownership

Evidence Lane is conceived, directed, funded, and owned by Praveen Rathee. Copyright © 2026 Praveen Rathee. All rights reserved. AI systems and software tools assist work; they do not own the project, accept candidates, authorize source changes, or receive copyright authorship.

Credited AI and toolchain roles

Third-party names are used only to describe provenance. Their software, services, licenses, and trademarks remain governed by their respective owners. The third-party licenses page records the current pinned dependency, packaged-binary, pypdfium2/PDFium, and upstream notice boundaries that must remain current before publication.

Public upstream references

The PV6 research cycle inspected exact commits of GitHub Agentic Workflows, GitHub Agentic Workflows MCP Gateway, GitHub Copilot SDK, GitHub Agentic Workflows threat detection, GitHub Agentic Workflows harness, Open WebUI, Graphify, GitHub CodeQL source, GitHub MCP Server, GitHub Branch Deploy, and GitHub Local Action. OpenAI public MCP and app guidance supplied metadata, annotation, structured-result, interactive-panel, CSP, and publication context. The upstream reference provenance ledger records every audited commit and tree, license, intended role, local implementation surface, refusal boundary, and verdict. The website renders the same complete ledger and links each repository to its pinned commit rather than to an unverified moving branch.

That ledger is the attribution authority for these references. It does not turn a URL into copied source, claim feature parity, treat Open WebUI’s current license as MIT, or convert an Actions run into a coding-agent session.

Human contributions

These records describe review and evaluation roles. Asking a question, giving feedback, suggesting a direction, or testing a build does not automatically create source authorship, ownership, or acceptance authority.

An accepted source contribution can be credited as authorship only when it has an attributable record, an explicit license/rights basis, a reviewable Git Delta, passing evidence, and human acceptance through the project HIL. Until those conditions are met, the repository will not infer contribution or ownership claims.

Release boundary

Credits never grant candidate approval, Git push authority, plugin installation authority, pointer movement, Fuse, main-branch merge, or State Travel. Those are separate governed actions.