Recued
Menu
← Back to recipes

My federated day

by recued-core v2 158 views

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.

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.

My federated day
This recipe

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.

pack:federated-projectsfederated-projectagendamy-tasks
by recued-core pinned v2

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.

pack:federated-projectsfederated-projectbootstrapnative-project
by recued-core pinned v3

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.

pack:federated-projectsfederated-projectboardlargest-recipe
by recued-core pinned v2

Use “Show a federated project” in Recued. Reads one project beside its pack-private federation record and peer inventory.

pack:federated-projectsfederated-projectdetail
by recued-core pinned v2

Use “Add a federated participant” in Recued. Records an accepted invitation and active Limited to the approved agreement participant in one Records batch.

pack:federated-projectsfederated-projectparticipantinvitation
by recued-core pinned v2

Use “Update a federated participant” in Recued. CAS-updates role, display label, task-assignee identity, contract binding, and active status for one participant.

pack:federated-projectsfederated-projectparticipantcas
by recued-core pinned v4
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.

pack:federated-projectsfederated-projectpeersource
by recued-core pinned v2

Use “Define a federated workflow state” in Recued. Adds one deterministic allowed task state for a project.

pack:federated-projectsfederated-projectworkflowstate
by recued-core pinned v2

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.

pack:federated-projectsfederated-projectworkfloweditable-table
by recued-core pinned v4

Use “Transition a federated task” in Recued. Validates the project-owned workflow vocabulary before changing native task state and progress.

pack:federated-projectsfederated-projecttaskworkflow
by recued-core pinned v3

Use “Log federated task effort” in Recued. Creates or CAS-updates the exact fixed-point effort row for one native task.

pack:federated-projectsfederated-projecteffortdecimal
by recued-core pinned v4

Use “Report federated project effort” in Recued. Aggregates exact estimates and actuals and shows the task-level rows behind the totals.

pack:federated-projectsfederated-projecteffortaggregate
by recued-core pinned v2

Use “Add a cross-node task dependency” in Recued. Stores the explicit string tuple that represents a dependency beyond the local reference namespace.

pack:federated-projectsfederated-projectdependencycross-node
by recued-core pinned v2

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.

pack:federated-projectsfederated-projectdependencyhealth
by recued-core pinned v2

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.

pack:federated-projectsd-232federated-projectpeer-receiver
by recued-core pinned v4
Peer: list one federated project
Background automation

Use “Peer: list one federated project” in Recued. Limited to the approved agreement peer list. It returns an array only after participant authorization.

pack:federated-projectsfederated-projectpeer-receiverread
by recued-core pinned v2
Peer: read a federated project
Background automation

Use “Peer: read a federated project” in Recued. Authorized peer read for exactly the configured project.

pack:federated-projectsfederated-projectpeer-receiverread
by recued-core pinned v2
Peer: update a federated project
Background automation

Use “Peer: update a federated project” in Recued. Limited to the approved agreement peer write for manager/owner/contributor roles.

pack:federated-projectsfederated-projectpeer-receiverwrite
by recued-core pinned v3
Peer: list federated tasks
Background automation

Use “Peer: list federated tasks” in Recued. Limited to the approved agreement peer list for tasks under one authoritative project.

pack:federated-projectsfederated-projectpeer-receiverread
by recued-core pinned v2
Peer: my federated day
Background automation

Use “Peer: my federated day” in Recued. It uses the connections and settings you choose when you run it.

pack:federated-projectsfederated-projectpeer-receiverread
by recued-core pinned v2
Peer: read a federated task
Background automation

Use “Peer: read a federated task” in Recued. Authorized peer read that verifies task parentage before rendering.

pack:federated-projectsfederated-projectpeer-receiverread
by recued-core pinned v2
Peer: update a federated task
Background automation

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.

pack:federated-projectsfederated-projectpeer-receiverwrite
by recued-core pinned v3
View pack details, dependencies, and permissions →

Your own tasks across every federated project you own, read straight from local records — no peer, no connection, no contract. It is the same question Peer: my federated day answers for someone else, asked by you, and it deliberately does not go through that recipe: that one is a receiver whose job is to authorize an inbound caller, and an owner running on their own server is not one. Leave the day empty to use the server day, or supply an exact local midnight pair when you know your own. The result always states how many tasks it scanned against how many exist, so a truncated agenda never reads as a complete one.

How it works 86 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (86 steps)
■ caller_contract default
Apply default
■ caller_is_owner compare
Check if caller contract is one of absent,user_self,stdio_local
■ owner_only_guard template
Generate text from a template
fail: step.caller_is_owner equal false
■ requested_refs default
Apply default
■ requested_count count
Count items in requested refs
■ has_requested compare
Check if requested count is greater than 0
◆ federation_page recued-core.federated-projects.federation.search
Search federation on federated projects
■ federation_rows default
Apply default
■ federations_requested filter
Filter by condition
■ federations ternary
Apply ternary
■ federation_count count
Count items in federations
■ project_refs pluck
Extract project_ref from each item
■ owner_contract_refs pluck
Extract owner_contract_ref from each item
◆ owner_participant_page recued-core.federated-projects.participant.search
Search participant on federated projects
■ owner_participant_rows default
Apply default
■ owner_in_scope filter
Filter by condition
■ owner_emails_trimmed map
Extract assigned_contact_id from each item
■ owner_emails_lowered map
Extract email_trimmed from each item
■ owner_emails_named filter
Filter by condition
■ owner_emails_plucked pluck
Extract email from each item
■ derived_identity unique
Remove duplicates from
■ owner_email_input trim
Trim whitespace from setting owner email
■ owner_email_override lowercase
Convert owner email input to lowercase
■ has_override compare
Check if owner email override has data
■ override_identity split
Split owner email override into parts
■ identity_set ternary
Apply ternary
■ identity_count count
Count items in identity set
■ has_identity compare
Check if identity count is greater than 0
■ day_start_text trim
Trim whitespace from setting day start at
■ day_end_text trim
Trim whitespace from setting day end at
■ day_start_given compare
Check if day start text has data
■ day_end_given compare
Check if day end text has data
■ window_any_given any
Check if any of the conditions are true
■ window_both_given all
Check if all conditions are true
■ window_not_both not
Apply not
■ window_half_given all
Check if all conditions are true
■ window_pair_guard template
Generate text from a template
fail: step.window_half_given equal true
■ supplied_start_ms date_parse
Parse setting day start at as a date
■ supplied_end_ms date_parse
Parse setting day end at as a date
■ supplied_start_ok compare
Check if supplied start ms exists
■ supplied_end_ok compare
Check if supplied end ms exists
■ supplied_window_ok all
Check if all conditions are true
■ window_offset_guard template
Generate text from a template
skip: step.window_both_given equal false
fail: step.supplied_window_ok equal false
■ server_day date_period
Apply date_period
■ server_start_ms date_parse
Parse server day start as a date
■ server_end_ms date_parse
Parse server day end as a date
■ day_start_ms ternary
Apply ternary
■ day_end_ms ternary
Apply ternary
■ day_basis ternary
Apply ternary
■ cap_clamped clamp
Clamp setting limit between 1 and 200
■ cap round
Round cap clamped to 0 decimal places
◆ task_reads core.work-entity.list
List work entity
■ task_groups map
Extract from each item
■ task_rows flatten
Flatten nested lists in
■ task_rows_trimmed map
Extract assigned_contact_id from each item
■ task_rows_keyed map
Extract assignment_trimmed from each item
■ assigned_tasks filter
Filter by condition
■ open_assigned_tasks filter
Filter by condition
■ dated_open_tasks filter
Filter by condition
■ overdue_tasks filter
Filter by condition
■ due_from_start filter
Filter by condition
■ due_today_tasks filter
Filter by condition
■ overdue_sorted sort
Sort by
■ due_today_sorted sort
Sort by
■ all_open_sorted sort
Sort by
■ today_tasks flatten
Flatten nested lists in
■ show_all_open compare
Check if setting scope equals all_open
■ agenda_source ternary
Apply ternary
■ agenda_tasks map
Extract from each item
■ agenda_count count
Count items in agenda tasks
■ agenda_task_ids pluck
Extract id from each item
◆ dependencies recued-core.federated-projects.remote_dependency.search
Search remote dependency on federated projects
skip: step.agenda_count equal 0
■ dependency_rows default
Apply default
■ agenda_dependencies map
Extract from each item
■ project_totals map
Extract from each item
■ project_task_total sum
Sum values in
■ scanned count
Count items in task rows
■ truncated compare
Check if scanned is less than project task total
■ open_assigned_count count
Count items in open assigned tasks
■ overdue_count count
Count items in overdue tasks
■ due_today_count count
Count items in due today tasks
■ blocking_count count
Count items in agenda dependencies
■ payload default
Apply default
■ card to_summary
Format results as a summary card
■ agenda_table to_table
Format results as a data table
■ health to_checklist
Format results as an actionable checklist
▼
Output
summary card
table agenda_tasks
table agenda_dependencies
checklist health
json payload
Settings 6 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

limit setting = 100
scope setting = today
day end at setting = [object Object]
owner email setting = [object Object]
day start at setting = [object Object]
project refs setting =

Uses (4 operations)

Pack operation Search federation on federated projects recued-core.federated-projects.federation.search
Pack operation Search participant on federated projects recued-core.federated-projects.participant.search
Tasks & notes List work entity core.work-entity.list
Pack operation Search remote dependency on federated projects recued-core.federated-projects.remote_dependency.search

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

Read Pack Federated Projects read-only
Read: federation.search · No approvalRead: participant.search · No approvalRead: remote_dependency.search · No approval
Read Tasks & notes core.work-entity.list read-only

Data it touches

SurfacesTasks & notes

About

Tags

pack:federated-projectsfederated-projectagendamy-taskstodaypersonalowner-surfacelocal-read

Details

86 steps 6 configurable settings recipe_id: my-federated-day