About the series

Long-term, citable technical documentation—between an academic paper and an engineering whitepaper.

Purpose

Document architectural decisions, standards implementations, and engineering experience so they can be independently reviewed and cited.

Scope

Architecture reports, reference implementations, standards experience reports, security analyses, benchmarks, and case studies on research infrastructure.

Versioning

Semantic versioning (MAJOR.MINOR.PATCH). Identifiers (SF-TR-YYYY-NNN) are permanent; revisions receive new release tags and Zenodo versions.

Licensing

Report content defaults to CC BY 4.0 unless otherwise stated in the report.

Review

Internal technical review before release—not journal peer review. Limitations and scope are stated in each report.

Principles

Transparency and reproducibility over promotional language.

  • Document what was built, how it was validated, and what was not claimed.
  • Prefer measurable statements over promotional language.
  • Reference standards by version.
  • Maintain a clear line between technical report and product marketing.

In planning

Topics for future reports—no fixed order or schedule.

  • Mycelium Architecture
  • GA4GH Data Connect in Practice
  • FAIR-by-Design Genomics Platforms
  • Federated Omics Infrastructure Patterns
  • Secure Data Access Architectures
  • Lessons Learned Building Research Infrastructure
  • DRS Implementation Guide
  • Crypt4GH Integration Patterns
  • Open Standards for Translational Research