Use “Initialize a federated project” in Recued. Creates the authoritative project and atomically seeds federation policy, the owner participant, invitation evidence, and a four-state workflow.
Initialize a federated project
Use “Initialize a federated project” in Recued. Creates the authoritative project and atomically seeds federation policy, the owner participant, invitation evidence, and a four-state workflow.
Complete workflow
Federated Projects
23 pinned recipes
Use Federated Projects in Recued for project management, federation, records, and work entity. It includes 46 actions and 14 ready-to-run workflows. Actions that change data use Recued's approval controls. It works on its own: one person can run every project here with nothing to connect. Add the people you work with by email, assign them work, and track effort. Install Federated Project Peer later, when someone you work with runs their own Recued.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
Use “Federated project command board” in Recued. It provides a complete workspace with project and tasks plus participants, peers, workflow, effort tracking, dependencies across peers, filter controls, actions, and diagnostic details.
Use “My federated day” in Recued. Reads every federated project you own and returns the open work assigned to you — overdue first, then due today — with no peer, connection, or contract involved.
Use “Show a federated project” in Recued. Reads one project beside its pack-private federation record and peer inventory.
Use “Add a federated participant” in Recued. Records an accepted invitation and active Limited to the approved agreement participant in one Records batch.
Use “Update a federated participant” in Recued. CAS-updates role, display label, task-assignee identity, contract binding, and active status for one participant.
Show all 23 recipes
Use “Register a federated peer” in Recued. Adds the local policy row that names a connected peer Source and its contract.
Use “Define a federated workflow state” in Recued. Adds one deterministic allowed task state for a project.
Use “Edit the federated workflow” in Recued. Loads the project workflow into an editable schema-derived grid and applies every submitted row atomically with Records CAS.
Use “Transition a federated task” in Recued. Validates the project-owned workflow vocabulary before changing native task state and progress.
Use “Log federated task effort” in Recued. Creates or CAS-updates the exact fixed-point effort row for one native task.
Use “Report federated project effort” in Recued. Aggregates exact estimates and actuals and shows the task-level rows behind the totals.
Use “Add a cross-node task dependency” in Recued. Stores the explicit string tuple that represents a dependency beyond the local reference namespace.
Use “Check cross-node dependencies” in Recued. Shows active remote pointers and the native tasks they can block; missing remote rows are never interpreted as deletion.
Use “Apply a peer's federated project update, then answer” in Recued. It carries out the named workflow using the connections and settings you choose. Changes remain behind Recued's approval controls.
Use “Peer: list one federated project” in Recued. Limited to the approved agreement peer list. It returns an array only after participant authorization.
Use “Peer: read a federated project” in Recued. Authorized peer read for exactly the configured project.
Use “Peer: update a federated project” in Recued. Limited to the approved agreement peer write for manager/owner/contributor roles.
Use “Peer: list federated tasks” in Recued. Limited to the approved agreement peer list for tasks under one authoritative project.
Use “Peer: my federated day” in Recued. It uses the connections and settings you choose when you run it.
Use “Peer: read a federated task” in Recued. Authorized peer read that verifies task parentage before rendering.
Use “Peer: update a federated task” in Recued. Limited to the approved agreement peer write that validates membership, task parentage, and optional workflow state before mutation.
Use “Records runtime” in Recued. It helps you complete this workflow using the connections and settings you choose.
You do not need anyone else on Recued to use this. A federated project run by one person is the normal starting point; peering is something you add later, and the owner contract is already filled in for you. Creates the native work fact first, then writes all pack-owned policy rows in one Records batch. If the batch fails, the native project remains visible and can be reconciled deliberately; no partial policy graph is committed.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (20 steps)
title
trim
Trim whitespace from setting title
title_required
template
Generate text from a template
fail: step.title is_empty
owner_contract_ref
trim
Trim whitespace from setting owner contract ref
owner_contract_ref_required
template
Generate text from a template
fail: step.owner_contract_ref is_empty
owner_name
trim
Trim whitespace from setting owner name
owner_assigned_contact_input
trim
Trim whitespace from setting owner assigned contact id
owner_assigned_contact_id
lowercase
Convert owner assigned contact input to lowercase
now_iso
date_add
Add 0 seconds to
target_completion_day
split
Split setting target completion at into parts
project_create
core.work-entity.project.create
Create work entity project
project_ref
default
Apply default
invitation_id
sha256
Apply sha256
participant_id
sha256
Apply sha256
state_specs
default
Apply default
state_ids
sha256
Apply sha256
state_ops
map
Extract from each item
base_ops
default
Apply default
bootstrap_ops
flatten
Flatten nested lists in
bootstrap
recued-core.federated-projects.federation.bootstrap
Bootstrap federation on federated projects
card
to_summary
Format results as a summary card
▼
Output
summary
card
json
project_create.project
table
state_specs
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
title
setting
=
[object Object]
currency
setting
=
USD
owner name
setting
=
Owner
description
setting
=
owner contract ref
setting
=
user_self
target completion at
setting
=
[object Object]
owner assigned contact id
setting
=
[object Object]
Uses (2 operations)
Tasks & notes
Create work entity project
core.work-entity.project.create
Pack operation
Bootstrap federation on federated projects
recued-core.federated-projects.federation.bootstrap
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.
What it's allowed to do
Write
Tasks & notes
core.work-entity.project.create
external change
Write
Pack
Federated Projects
external change
Write: federation.bootstrap · No approval