Synchronize your instance with Federación Futuh

What it's for

Activate the canonical synchronization channel from the Hub Central to your instance, understand what data comes from outside, what data remains yours, and which cost model applies.

Before you start

• Role: administrator of your Futuh instance.
• Your organization has a Futuh subscription that includes federation.
• Access to the Federación Futuh menu (top-level Odoo menu; requires the federation admin role).
• Estimated time: 10–15 minutes of initial configuration; the rest happens automatically.

What is federated today

The current version of Federación Futuh distributes four categories of canonical data from a single Hub Central operated by the Futuh team within the infrastructure of Asamblea de Cooperación Por la Paz:

• BDNS regulatory bases analyzed with AI: each grant call published in BDNS is processed once at the Hub to extract formal requirements, evaluation criteria, and eligible beneficiaries. Your instance receives the structured analysis, not the PDF.
• BDNS awards: the historical record of who received which grant, so that Radar can estimate success rates by call.
• Document templates: standard agreements, model reports, common legal clause texts (LGPL, GDPR, cooperative contracts).
• Silvio Agent Pack: pre-trained AI agents that Silvio uses for specific tasks (summarizing regulatory bases, suggesting clauses, drafting client emails).

Which categories your organization receives depends on the sector bundle you have contracted with Futuh (cooperation, social-action third sector, ESS). Within what you have contracted, the sync brings the full catalog of each data type: there is no fine per-client filter over which specific records arrive, that filtering happens afterwards, already in your instance.

Step 1: Connect the Hub endpoint

1. Open Federación Futuh → Configuración Federación → Hubs configurados and open the Hub Futuh Central record.
2. Verify the Hub URL (pre-configured as https://hub.futuh.coop; only change it if the Futuh team gave you another).
3. In the Configuración group, paste the token into the Token de autenticación field. The field is masked as you type.
4. Save.

The module has no “test connection” button. To confirm the connection works, let the automatic healthcheck run (every 4 hours, it updates the record’s Estado group) or force a sync (Step 3). If something fails, the most common causes are an expired token or a URL pointing to the wrong Hub environment (staging instead of production). Contact the Futuh team to review.

Step 2: Review the canonical subscriptions

You do not need to activate the canonical data by hand: your instance subscribes automatically to the data types required by the modules you have installed. If you have Radar, it subscribes to BDNS regulatory bases and awards; if you have Incidencia Política, to parliamentarians; and so on for each module.

1. Open Federación Futuh → Configuración Federación → Subscriptions activas.
2. Review the list: you will see one subscription per data type your modules consume (four or more in a typical installation).
3. Each subscription declares the destination model and the source route in the Hub, and shows its health state.

Which categories you have available depends on the sector bundle contracted with Futuh. The daily pull cron (Step 3) synchronizes the updates of all active subscriptions.

Step 3: First full synchronization

The first time you activate a canonical dataset, the cron downloads the complete historical catalog. This may take several minutes depending on the volume.

1. Open Federación Futuh → Configuración Federación → Histórico de syncs.
2. Verify that the first pull appears with status OK or Partial.
3. If it shows Failed or Hub Unreachable, open the detail to see the reason (the most common cause is a timeout: relaunch it using the Sincronizar ahora button on the subscription).

From the second cron onwards, pulls are incremental: only updates since the last synchronization are downloaded. This is fast (a few seconds) except on days of major canonical updates.

What comes from outside vs what is your own

The distinction matters for understanding what happens when you edit a record manually:

• What arrives from the Hub carries an internal marker called canonical_signature, an MD5 signature of the canonical content the Hub sent. This marker allows your instance to distinguish a federated record from one created by your organization.
• What your organization adds on top is flagged with manually_edited=True. When the daily cron detects a canonical update on a record you have edited, it does not overwrite it: it passes it by and logs a notice.

This means you can adapt any template to your context, adjust the analysis of a regulatory base, or customize an Agent Pack, without fear that the next synchronization will erase your changes.

How to return to the canonical version after a manual edit

If you want the Hub to update a record you edited again (because your local change has become outdated), you currently need to clear the Editado localmente flag on the record, which requires developer mode or the help of the Futuh team. A one-click “revert to canonical” button is on the roadmap.

Cost model: Tier 0 vs Tier 1

The federation works with two tiers:

• Tier 0: public-domain or Futuh-community-produced canonical data. Includes analyzed BDNS regulatory bases, CAD/ODA markers, ODS Agenda 2030, official vocabularies. Available to any instance at no additional cost beyond the Futuh subscription.
• Tier 1: proprietary Futuh value-added canonical data. Includes canonical document templates drafted by the team, pre-trained Agent Packs, European parliamentary contacts enriched with HowTheyVote. Requires an active Tier 1 subscription.

The annual Futuh subscription your organization pays (calculated from your triennial income, in five bands up to 25 M€) covers the full federation, with no per-consumption billing. There is no download limit, no surcharge per call tracked, no per-template fee. The canonical project reasoning is that if the federation delivers on its promise, there is no point in charging you for using it.

If you decide not to renew your subscription, the modules continue working with the last data they synchronized, but they no longer receive new canonical updates. The Futuh code is free and downloadable without federation; federated services are the filter that distinguishes the subscription from a bare installation.

Verify the cron

1. Open Settings → Technical → Scheduled actions.
2. Find the entry Futuh Federation: pull canon diario.
3. Verify that it is active and that its next run appears scheduled.
4. If you need to force an immediate pull, open the entry and click Run now.

The logs of each run are in Federación Futuh → Configuración Federación → Histórico de syncs, with metrics: number of records received, created, updated, and skipped due to manual editing.

How this flow fits with the rest

Module	What it consumes from the Hub	Detail
Federación Futuh	The layer that organizes the synchronization itself	Federación Futuh
Radar	Analyzed BDNS regulatory bases + awards	Radar de ayudas
Silvio	Canonical Agent Pack out of the box	Silvio
Recepción Inteligente	Canonical document type catalog	Plataforma de Recepción Inteligente
Incidencia Política	Canonical parliamentary contacts (Tier 1)	Incidencia Política
Gestión de ayudas	Document templates for project stages	Gestión de ayudas

Learn more

• Connect your instance to the Hub Central for the technical detail of the setup.
• Federación Futuh to understand the hub-and-spoke architecture.
• Glossary for the canonical terms: Hub Central, canonical documentation, canonical signature.