Project Idea
Sync Steward — Attributing and Rewarding the Work that Advances Raids
Project Submitted By
aphilos.eth
Summary
As Sync Steward I propose to advance threads by guiding RaGuild meetings. To do this effectively over time, we need a way to recognize and reward peoples’ work. Meetings will be paired with a simple attribution cycle: a member says what they did, the meeting affirms it by consensus, it's published to a public record, and it pays out when the thread becomes a funded raid. We have the tools now to do this, but they’re fragmented and untrained; As Sync Steward I will sync these tools so administration is minimal and we focus on next steps.
https://www.youtube.com/shorts/RYeNu159Sgc
Why should we build this?
To harness our great discussions.
People want to work with us, we want to work with each other. We can’t see their work, they can’t see ours. We are more than capable. We want to synchronize. We love to talk about our visions. Discussion becomes endless, we are another voice swimming to the surface, building becomes easier. There are infinite ways to build, we want the version that fits, that’s composable.
We have agents to record our meetings, agents to sort our discussions, agents to interpret our statements, agents to connect our work, agents to find what we’re looking for, agents to talk to agents.
To synchronize is subtle. A gentle reminder here, a conclusion there. There are so many of us, in so many conversations, all around the world. We need a common medium, a way to sync effortlessly, a way to swarm. We want to discuss, make small corrections, act, discuss, recognize, reward, rinse and repeat.
Attribution is a medium we can swarm in. The more time it takes to agree on attribution, the thicker the medium, the harder it is to swim and swarm. Attribution must be automated.
How it works — the attribution cycle
The whole system is one cycle. As Sync Steward I will train our agents by guiding people at meetings. Guidance ensures agents have what they need, building ensures agents use what we give them:
-
Capture. A member tells QueenRaida what they’ve been working on, through whatever medium is convenient. Members say what they did on a thread — an intro, a follow-up, a call. No forms, no gatekeeping. The contribution is now on the record. Sync steward supports capture by education and building capture tools.
-
Affirm. At regular meetings, QueenRaida reads back the contributions captured that week, and RaidGuild members affirm them by consensus. Sync steward initiates that review, and guides it so it's quick and fair. Affirmation creates canon.
-
Publish. Affirmed contributions post to a public record, so everyone can see who advanced which thread. Credit is visible long before any money moves.
-
Realize. When a thread has a crystallization event, the reward pool is split among the affirmed contributors who moved it there. Effort finally bears fruit — on the record, in proportion to the work.
Each turn of the cycle also produces the thing we're missing today: a clear, progressive next step. A member leaves the meeting knowing which thread they can move one notch further before we meet again.
Anything else you'd like to add?
Underneath the cycle, a thread keeps one identity from first contact to paid raid and carries a running log of who did what at each step — so contributions accumulate over the thread's whole life and can be replayed fairly at payout. It runs on rails the Guild already operates: QueenRaida, the Monk's Office action list, the weekly meeting for consensus, the BD Agent.
Raid Party Skills Needed
- Agent dev: host the BD agent under RaidGuild infra, connect with QueenRaida and the action list
- Data modeling: thread record and per-step contribution log
- Front-end / data-viz: Horizon: the public record and attribution view
- BD / relationship contributors: RaidGuild members sourcing and advancing threads
- Coordination: the Sync Steward function itself
Cost (in USD)
$2,000 per quarter, renewable by quarter., in line with the standard Steward budget:
- two-thirds for implementation
- one-third to Steward coordination.
Project Idea
Sync Steward — Attributing and Rewarding the Work that Advances Raids
Project Submitted By
aphilos.eth
Summary
As Sync Steward I propose to advance threads by guiding RaGuild meetings. To do this effectively over time, we need a way to recognize and reward peoples’ work. Meetings will be paired with a simple attribution cycle: a member says what they did, the meeting affirms it by consensus, it's published to a public record, and it pays out when the thread becomes a funded raid. We have the tools now to do this, but they’re fragmented and untrained; As Sync Steward I will sync these tools so administration is minimal and we focus on next steps.
https://www.youtube.com/shorts/RYeNu159Sgc
Why should we build this?
To harness our great discussions.
People want to work with us, we want to work with each other. We can’t see their work, they can’t see ours. We are more than capable. We want to synchronize. We love to talk about our visions. Discussion becomes endless, we are another voice swimming to the surface, building becomes easier. There are infinite ways to build, we want the version that fits, that’s composable.
We have agents to record our meetings, agents to sort our discussions, agents to interpret our statements, agents to connect our work, agents to find what we’re looking for, agents to talk to agents.
To synchronize is subtle. A gentle reminder here, a conclusion there. There are so many of us, in so many conversations, all around the world. We need a common medium, a way to sync effortlessly, a way to swarm. We want to discuss, make small corrections, act, discuss, recognize, reward, rinse and repeat.
Attribution is a medium we can swarm in. The more time it takes to agree on attribution, the thicker the medium, the harder it is to swim and swarm. Attribution must be automated.
How it works — the attribution cycle
The whole system is one cycle. As Sync Steward I will train our agents by guiding people at meetings. Guidance ensures agents have what they need, building ensures agents use what we give them:
Capture. A member tells QueenRaida what they’ve been working on, through whatever medium is convenient. Members say what they did on a thread — an intro, a follow-up, a call. No forms, no gatekeeping. The contribution is now on the record. Sync steward supports capture by education and building capture tools.
Affirm. At regular meetings, QueenRaida reads back the contributions captured that week, and RaidGuild members affirm them by consensus. Sync steward initiates that review, and guides it so it's quick and fair. Affirmation creates canon.
Publish. Affirmed contributions post to a public record, so everyone can see who advanced which thread. Credit is visible long before any money moves.
Realize. When a thread has a crystallization event, the reward pool is split among the affirmed contributors who moved it there. Effort finally bears fruit — on the record, in proportion to the work.
Each turn of the cycle also produces the thing we're missing today: a clear, progressive next step. A member leaves the meeting knowing which thread they can move one notch further before we meet again.
Anything else you'd like to add?
Underneath the cycle, a thread keeps one identity from first contact to paid raid and carries a running log of who did what at each step — so contributions accumulate over the thread's whole life and can be replayed fairly at payout. It runs on rails the Guild already operates: QueenRaida, the Monk's Office action list, the weekly meeting for consensus, the BD Agent.
Raid Party Skills Needed
Cost (in USD)
$2,000 per quarter, renewable by quarter., in line with the standard Steward budget: