Use “Add a cross-node task dependency” in Recued. Stores the explicit string tuple that represents a dependency beyond the local reference namespace.
Add a cross-node task dependency
Use “Add a cross-node task dependency” in Recued. Stores the explicit string tuple that represents a dependency beyond the local reference namespace.
Complete workflow
Federated Projects
22 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. Setup: add your peer's Recued server as a connection, choose it at install, then set two values on it. project_ref is the project you share with them. peer_contract_id is the inbound token you minted for them, not one you hold. Without it this pack accepts their updates but cannot reply.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
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.
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 “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, and active status for one participant.
Show all 22 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 “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.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (23 steps)
project_ref
trim
Trim whitespace from setting project ref
project_ref_required
template
Generate text from a template
fail: step.project_ref is_empty
task_ref
trim
Trim whitespace from setting task ref
task_ref_required
template
Generate text from a template
fail: step.task_ref is_empty
peer_id
trim
Trim whitespace from setting peer id
peer_id_required
template
Generate text from a template
fail: step.peer_id is_empty
peer_source_id
trim
Trim whitespace from setting peer source id
peer_source_id_required
template
Generate text from a template
fail: step.peer_source_id is_empty
remote_task_id
trim
Trim whitespace from setting remote task id
remote_task_id_required
template
Generate text from a template
fail: step.remote_task_id is_empty
task
?
task_found
template
Generate text from a template
fail: step.task.found equal false
task_project_matches
compare
Check if task entity parent project id equals project ref
task_project_guard
template
Generate text from a template
fail: step.task_project_matches equal false
peer
?
peer_found
template
Generate text from a template
fail: step.peer.record.id is_empty
peer_project_matches
compare
Check if peer record project ref equals project ref
peer_project_guard
template
Generate text from a template
fail: step.peer_project_matches equal false
peer_source_matches
compare
Check if peer record source id equals peer source id
peer_source_guard
template
Generate text from a template
fail: step.peer_source_matches equal false
write
?
read
?
rows
default
Apply default
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
note
setting
=
state
setting
=
unknown
peer id
setting
=
[object Object]
blocking
setting
=
true
task ref
setting
=
[object Object]
project ref
setting
=
[object Object]
peer source id
setting
=
[object Object]
remote task id
setting
=
[object Object]