Skip to main content

​
Authorship and provenance

Enoch separates software/system authorship, operational release responsibility, and generated research text and claims. The maintainer/operator can be credited for building, operating, packaging, and releasing the system. They should not be credited as the human author of generated paper prose, arguments, or generated results.

​
Required framing

Use this framing when describing the corpus:
The reports produced by this system are AI-generated research artifacts created from automated run notes, evidence bundles, claim ledgers, and reproducibility traces. The maintainer releases the corpus for inspection and critique but does not claim personal authorship of the generated papers, arguments, or prose.

​
What each artifact should preserve

The dashboard should make provenance visible before a generated artifact is treated as ready. In the current capture below, every paper row keeps links to the draft, claim ledger, and manifest instead of presenting the draft as a standalone publication.
The dashboard screenshot below is pending replacement with a redacted, public-safe capture. The current images/dashboard-papers.png shows paper paths and counts that drift, and includes the compatibility-only “Supabase” footer string. Until replaced, treat as a layout reference only.
Current papers queue showing generated draft, claim ledger, and manifest paths
  • ai_generated: true
  • human_authorship_claimed: false
  • generated/released provenance metadata
  • evidence availability
  • claim-ledger availability
  • review status
  • source fingerprints or equivalent traceability when available

​
How to cite or reference

If you reference the dataset, cite it as an AI-generated research artifact corpus produced by the Enoch agentic research system. Include the caveat that artifacts are not peer-reviewed scientific claims. Do not cite individual generated reports as validated academic papers unless independent human review and replication have happened outside Enoch.