Martin Petrasek
Responsible for programme architecture, theoretical framework development, public documentation trail and institutional correspondence.
People and stewardship
Research leadership, programme stewardship and correspondence routes.
IRSFP is presented as an independent research platform with a public programme architecture. The team page clarifies who stewards the research lanes, how correspondence is routed and what forms of collaboration are useful.
Institute roleindependent research platform
Primary functionprogramme architecture
Collaboration modereview, replication, institution
Mailboxresearch@irsfp.org
Leadership
A serious institute page should make responsibilities explicit. This section focuses on stewardship and correspondence, not inflated biography.
IRSFP research desk
Coordinates programme pages, DOI references, repository continuity, public status labels and collaboration intake.
Collaboration roles
The institute is most useful when collaborators engage with a specific programme, output record or validation route.
Scientific critique
Formal assumptions, definitions, equations, inference routes, validation gaps and falsification criteria.
Repository and reproducibility
Versioned materials, computational notebooks, data requirements, provenance and reproducible documentation.
Research dialogue
University, laboratory and applied-research correspondence around programme-specific validation paths.
Best first contact
Name the programme and the record under discussion.
Messages with a clear scope are easier to route and more likely to produce useful technical exchange.
research@irsfp.org
Public documentation
Reference DOI records, programme pages or archive names.
IRSFP prioritizes durable documentation and public traceability over informal claims.
record trail
Institutional correspondence
Use institutional mail and state affiliation, scope and expected output.
Suitable for review invitations, replication proposals and applied stability discussions.
formal route
Start with a programme
The strongest correspondence begins with one programme, one output record and one clear technical question.