← decisions

Decision

A single call, in full — the subject it hangs off, its linked context, and the metadata around it. Answer here and the daemon that asked pulls your answer and carries on.

flower from brief #196 for · flower-refine

Conductor case

For the conductor/lounge/vodmanager job-routing need specifically: agree flower's role is coordination/memory (multi-project briefs + cross-project recall), while the job-routing mechanism itself is conductor's code problem?

your call

Yes — flower = coordination/memory; job-routing is conductor's code

No — I want to explore flower doing more here

Split it: track/coordinate in flower, but let's also discuss the routing design

subject

brief #196 Multiple project / cross-project support/usage How might we envision Multiple project / cross-project support/usage How might we envision something like that? A perfect example is right now - I have two projects, `lounge` and `vodmanager` that I both want to use `conductor` via `conductor-client`. So that's effectively 4 projects that are all actively in development around a single set of functions/processes and all of them needing massaging to get integrated. Right now conductor works, client works in lounge and it's functional. But there's things that don't support the idea of t...

metadata

type: single_choice
status: open
project: flower
assigned to: flower-refine
asked by: flower-refine
round: 1
asked: 1 day ago