Cadeia de valorPublicado · serializadores e piloto por fazer

Registos de campo que se podem citar — com o consentimento, a proveniência e a retratação em anexo.

Para institutos de política, equipas de avaliação e unidades de evidência que precisam de microdados operacionais agrícolas que se sustentem.

Vista de contas do FuroField, com margem por hectare por ciclo de cultura
Espaço de trabalho do produto · dados de demonstração ilustrativos
Publicado · serializadores e piloto por fazerO estudo, o protocolo, a coorte congelada, o consentimento vinculado à finalidade com propagação da retirada, as versões de extração apenas por acrescento com substituição, os pseudónimos por estudo e as barreiras de publicação estão em produção e verificados. A serialização em formatos estatísticos colunares e as provas de adaptadores para os ambientes de análise não estão entregues, e um piloto externo ainda não decorreu. O FuroField fornece microdados governados; não analisa, não pondera, e não afirma representatividade nem causalidade.

A investigação agrícola nesta região corre sobre inquéritos, porque a alternativa nunca esteve disponível. Um inquérito é caro, é periódico, é recordado em vez de registado, e quando fica tratado a época que descreve já vai em duas atrás. Entretanto o registo operacional — o que foi de facto semeado, aplicado, colhido, pago e vendido — existe em milhares de machambas e não é utilizável por ninguém de fora, porque não traz consentimento, nem proveniência, nem forma de retirar um participante.

A espinha de investigação do FuroField transforma essa captura operacional de rotina num conjunto de dados com permissões: um estudo e um protocolo versionados, uma coorte congelada com hashes imutáveis, consentimento específico à finalidade que se propaga quando é retirado, e extrações apenas por acrescento, substituídas individualmente em vez de trocadas em silêncio.

O que deliberadamente não faz é a análise. Não pondera, não modela, não estima, e não lhe dirá que uma coorte é representativa. Esses juízos são seus e continuam seus — o trabalho da espinha é tornar os dados subjacentes suficientemente defensáveis para que os seus juízos possam ser examinados por outra pessoa.

O problema

Operational farm data is abundant, and almost none of it is citable

The barrier is not access to records. It is that a record gathered for running a farm carries none of the apparatus a study needs: no purpose-bound consent, no frozen cohort, no version you can point a reviewer at, and no mechanism to remove a participant who changes their mind without silently invalidating everything already published from that extract.

  • Consent given once, in general terms, for a purpose nobody wrote down
  • No frozen cohort, so the population under study drifts while the study runs
  • Extracts shared as files, superseded by other files, with no lineage between them
  • Withdrawal handled by deletion — which corrupts the published analysis rather than annotating it
  • Identifiers reused across studies, so two datasets can be joined that were never meant to be
Como funciona

Do primeiro registo a algo sobre o qual pode agir

01

Declare the study and freeze the protocol

Study, design, protocol and variable set are versioned authority records. A protocol cannot be frozen against a source that is custodial or unresolved — the freeze produces a refusal report naming what is missing, rather than a dataset with a quiet hole in it.

02

Freeze the cohort, then let it move on the record

Membership and intervention definitions are frozen with immutable hashes. Exclusions and assignment deviations are appended as events, never edited in place, so attrition and cohort flow are readable after the fact instead of reconstructed.

03

Bind consent to the purpose and the version

Consent is specific to a purpose and a protocol version, withdrawal propagates through what depends on it, and the participant gets a receipt. Subject requests are answered with hash-bound downloads. A grower can act on their own behalf, not only through an operator.

04

Release through gates that refuse rather than degrade

Per-study pseudonyms, a frozen geography and suppression policy, and five executing release gates with expiring grants and logged access. A gate that fails produces a refusal — never a quieter, coarser download that looks like the real one.

O que recebe

Em detalhe

An extract with canonical bytes and a codebook

Append-only versions carrying a manifest, codebook, quality report and hashes, so two people who cite the same version are provably citing the same bytes.

Supersession instead of silent recall

No released file is withdrawn behind your back. A consumer of a superseded version sees that it was superseded, the id that replaces it and the reason — which is what makes a correction publishable rather than embarrassing.

Per-study pseudonyms that do not join

Identifiers are derived per study, so two extracts released to different teams cannot be linked back together by the identifier alone.

Withdrawal that annotates rather than destroys

A participant who withdraws is propagated through what depends on their consent and recorded as an event. The published analysis stays examinable; what changed is legible.

Sampling frame and instruments, frozen and versioned

Frame, members, instrument versions, measurement occasions and assignment provenance are held as records, with attrition and cohort flow append-only.

An access trail on every release

Expiring principal grants and logged access events, so who obtained which version and when is part of the study record rather than a memory of who was emailed.

Para quem é

Feito para estas operações

Policy research institutes and university agricultural economics groups
Monitoring, evaluation and learning teams inside programmes and funds
Evidence and impact units accountable to a funder or a board
Perguntas

Sobre investigadores e avaliadores

Is this a replacement for our survey instrument?

No, and we would rather say so before you invest time than after. A survey asks questions nobody's operations answer — intent, perception, household composition, recall of a year with no records. This spine supplies the observed operational half: what was planted, applied, harvested, paid and sold, with consent and provenance. It complements an instrument and shortens it; it does not replace the reasons you field one.

Do you do the analysis, or provide weights?

Neither, by design. FuroField records an approved design and releases the data under it; it does not choose an estimator, construct weights, or make a claim about representativeness or causality. Those remain the researcher's responsibility, and a platform that offered them would be asserting authority over findings it has no standing to hold.

How do you handle a participant who withdraws after publication?

Withdrawal propagates through what depends on that consent and is recorded as an event, and the affected extract version is superseded with a stated reason rather than deleted. Deleting it would corrupt the published analysis and hide that anything happened; superseding it lets you issue a correction that a reviewer can follow.

What is not built yet?

The spine reached production in August 2026 and the boundary is published on this page rather than discovered later. Columnar serialisation for the statistical formats and worked adapter proofs for the common analysis environments are not shipped, so an extract arrives in the released canonical form and you convert it. A funded external pilot is the next step and has not run.

Whose data is it?

The producer's. The scheme or farm operates the workspace and the participant holds the consent, which is why withdrawal has to work and why a study cannot freeze against a source it does not properly hold. A dataset a participant cannot leave is not a consented dataset, whatever the paperwork says.

Ponha os seus talhões no mapa esta época

Comece grátis até 25 hectares — sem cartão. Cresça ao hectare à medida que a operação cresce.