Use this template when documenting a public evidence package that links to Permea Core.
evidence_package_id
Human-readable package name.
Public repository URL or repository identifier.
Why the package exists and which review question it supports.
Examples: computational evidence package, reproducibility package, benchmark-support package, dataset-provenance package, review-support package.
- dataset registry entry:
- dataset card:
- provenance record:
- benchmark registry entry:
- benchmark card:
- benchmark run record:
- research package registry entry:
- research package review path:
- claim registry entry:
- claim boundary:
Commands, package docs, or package artifacts needed to reproduce the package's public computational outputs.
Core validation commands and package validation commands that reviewers should run.
- computational-only unless separately validated
- no wet-lab validation by Permea
- no biological efficacy claim
- no therapeutic outcome claim
- no BBB success claim
- no solved-delivery claim
- no SOTA performance claim
- no experimental validation claim
- no clinical evidence claim
- no expression improvement claim
What this package does not establish and what future validation would be required before expanding claims.
One of:
- proposed
- documented
- reproducible_computational
- public_review_ready
- externally_validated
- superseded
- archived
Evidence package metadata version.
Reviewer notes, known issues, supersession path, or future validation requirements.