Skip to main content
Research backbone · A brand-bearer of SyntrocietyOpen source · Open data · Slate
§ The Syntrociety research framework

SYFERS.

The infrastructure that turns a federation of into a research institution.

SYFERS is what holds the federation's evidence: methodology that describes how Labs work, tools that record what Labs do, and a public repository where the records become citable. Three layers, one purpose. If a single Lab cannot prove its practice, a federation can.

§ Who you are

Three doors into one instrument.

SYFERS reads differently depending on why you are here. Three doors, the same infrastructure.

For those who practice SYFERS daily

What this instrument gives you.

Daily practice becomes legible to institutions without extra work. What sits in an alternative corner can, through these instruments, be brought into the system.

Jump to §03 for Lab members →

For those who want to study the federation

A corpus you can actually study.

Open data, documented methodology, citable records. Per-Lab and federation-wide. No paywall, no login.

Jump to §03 for researchers →

For cooperatives considering joining

What open registration actually means.

Not reporting on top, but registration as a byproduct of being a Lab. The threshold, and what you get in return.

Read Become a Lab →
SYFERS data flowSix stations left to right: Lab, people, chart, compass, lens, Repository. Each step adds discipline; the last publishes openly.LabTHE WORKREGISTERSDaily practice, decisions, harvestsidentitypeopleidentity hostHOLDSMembers, Friends, consentsrecordschartrecords platformREGISTERSProposals, decisions, auditsreflectscompassself-assessmentREFLECTSSixteen SYFERS conditionstranslateslensdocument pipelineTRANSLATESLetters, contracts, archivespublishesREPOSITORYCC BY-SA 4.0CITESOpen data, citable, no loginWhat gets registered is what can be cited.

§ Compass

A mirror,
not a gate.

Compass lets a Lab place itself, for each of the sixteen SYFERS conditions, on one of four levels: absent, emerging, established, embedded.

Nobody scores anyone. The Lab tells itself the truth about where it is, in the same words every other Lab uses.

Because every Lab uses the same sixteen conditions, what one Lab learns becomes legible to the others. A Lab that has worked through embedded on one condition can show what that asked, in practice. Maturity grows by reading each other, not by being ranked.

Begin the self-assessment →

§ 01, Three layers

Methodology, tools, and
a public repository.

Each layer is necessary. None of the layers is sufficient on its own.

i.

The framework · Methodology

Methodology

How a Lab counts as a Lab.

The research discipline behind Living Lab work. How decisions are recorded, how soil is sampled, how members are tracked, how reproducibility is preserved. Built against the specifications of EU research frameworks (ORRI, Horizon Europe Cluster 6) so that what Labs do is what funders and researchers can read.

A discipline, not a product
ii.

The tools · Two surfaces

Two surfaces

Where Labs do the work.

chart.syfers.eu is the Lab tool: members, decisions, plant register, energy data, project log. lens.syfers.eu is the Document Intelligence platform: archive, drafting, consent-based proposals. Together they turn daily practice into structured evidence, in real time, without extra effort.

Open source · Free to all member Labs
iii.

The repository · Public output

Public output

Where the work becomes citable.

Every record the tools generate flows into a public repository at syfers.eu. Researchers can access it and cite it. Stakeholders can read it. Funders can verify it. The repository is the layer that makes the federation visible to the outside world as something other than a brochure.

Open access · Per-Lab and federation-wide

A single can describe what it does, but it cannot prove much. Its results sit in a folder, its decisions in a chat, its handbook on a shared drive that almost nobody reads. It can speak; it cannot be cited.

A federation of Labs that all register their practice the same way produces something different: a corpus. Patterns across Labs become visible. Outliers become questions. Methodology becomes testable. The same framework that governs daily registration also governs reporting to funders, to researchers, to whoever asks. One stream of work, multiple audiences.

SYFERS is what allows a federation of small projects to act like a research institution, without becoming one.

The federation does not own a building or hold a patent. What it owns is the framework, the tools, and the repository. That is enough. Researchers can study the corpus. Other federations can adopt the framework. Labs can leave with their data intact. Nobody is held captive by infrastructure they did not help build.

§ 03, Who uses it

Two readers. One repository.

What Labs need from SYFERS is different from what researchers need. Both are served by the same layers.

For Labs

Daily practice becomes daily evidence.

What this instrument structurally makes possible: your work does not have to change to become legible to institutions. The regenerative work you do, the decisions you take in Council, the plants you register, the harvests you count, this is brought by SYFERS into a form that EU frameworks, researchers and funders can read. Not by adapting your work. By registering your work as it is.

Member Labs use the two tools as the working infrastructure of the cooperative. The framework keeps registration consistent across Labs; the repository turns the records into something stakeholders, funders, and researchers can read. The Lab does its work; the work registers itself.

What SYFERS structurally does: work that sits in an alternative corner can, through these instruments, be brought into the system. Not as compromise. As hybrid strategy. Becoming mainstream without losing the regenerative substance. This is no accident. It is what the instrument was built to make possible.

  • Member & governance log
  • Decision archive with consent trail
  • Plant, soil, biodiversity register
  • Auto-publication to public repo
  • Cross-Lab handbook access

How your name stays protected

Personal identity stays within the Lab.

What goes out is the work, not who does the work. Names of members and participants are, at document generation, automatically translated to their role: facilitator, member, with a number when there are several. It happens without extra work; it is how SYFERS drives the publication layer.

Under the hood, this is how it works. SYFERS holds two repositories: a private repo where Lab members register their work with the names they use internally, and a public repo where only the anonymised version appears. The translation from names to roles happens between the two. Lab members see both. Researchers and the public see only the second.

Private — within the Lab

  • Member names
  • Personal decisions with attribution
  • Internal handbook versions

Public — open repo

  • Member roles (facilitator, member 01, member 02)
  • Anonymised decision trails
  • Aggregate Lab metrics

Between the two

  • Automatic translation at document generation
  • No manual anonymisation work per registration

For researchers

A corpus you can actually study.

Universities, policy researchers, philanthropic evaluators, and independent journalists can read the federation's evidence directly. The methodology is documented; the data is structured; citations are durable. What you find is reproducible because the framework is public.

  • Citable per-Lab and cross-Lab data
  • Documented methodology
  • Decision & governance traces
  • Longitudinal records (multi-year)
  • Open access · No paywall · No login

Editorial offering · Depth

When this instrument chafes.

For those who practice SYFERS from the Lab, it sometimes feels like tension between two worlds. The world where you work daily, with land, body, rhythm, lived knowing. And the world the instrument comes from, with data, registration, legibility for institutions.

That tension is no accident. We have described it in an editorial essay. SYFERS sits at the crossing of what researchers call boundary objects: instruments that work in two paradigms at the same time. Their productivity comes precisely from that position. Not despite the tension, but because the tension is held.

If you are curious where this work stands in a wider field, or why the federation chooses this hybrid form rather than withdrawing or institutionalising, read on.

→ Read The two cultures

§ 04 · Patterns

The operational analysis set.

Patterns is the set of criteria that SYFERS uses for analysis. It is the operational subset of The Lens, the editorial reference at /lens. Patterns holds the Lens entries that are workable within app context, with weights set per Council or per analysis.

When a Lab runs an analysis, it picks from Patterns which criteria are relevant for that specific analysis, and sets weights. SYFERS reads the registered data through these criteria, from the perspective documented in The Lens.

Patterns evolves with the federation. When a new Lens entry is deemed operational by the Council, it is added to Patterns. When a Lens entry does not lend itself to app analysis (for example because it asks for qualitative judgement that does not tolerate quantification), it remains in The Lens as editorial reference but not in Patterns.

§ 06, Where to next

Read further, or begin.

If you are a researcher who wants to study the corpus, start at the hub. If you are a cooperative considering federation, read how SYFERS supports Labs in practice. If you want to understand the framework's roots, the federation's research programme begins with one paper.

Every layer is open. Nothing is paywalled. Nothing requires login to read.

§ Within the broader methodology

SYFERS works as a boundary object between Lab practice and institutional legibility.

One of five boundary configurations the federation names. See boundary work for the broader methodology.

Read boundary work →

§ Frequently asked questions for this page

Frequently asked questions.