pages / program / flow_helpdesk_case

program · flow_helpdesk_case

canister coord://offchain/genie/program/flow_helpdesk_case@v1/9df48e15f9343a9d · v1 · artifact root 0x9df48e15f9343a9d435a80680f6783ce044f2682868600047f3b45038464c894 · previous none (first version) · superroot at publish not sealed yet

sealed cases that reached it: 0 — sealed cases that reached this word (the store counts, never reads)

the words it says

• venues · mcp
• venues · n8n
• venues · grid
• venues · jev
• components · coord-stream
• components · grid-meter
• components · jev
• components · sma-graph
• components · sma-helpdesk
• components · sma-directory
• hops · graded
• hops · settled
• hops · recorded
• kinds · trigger
• kinds · read
• kinds · route
• kinds · guard
• kinds · act
• kinds · grade
• flows · flow:helpdesk-case
• parties · agent
• hdkinds · symptom
• hdkinds · fix
• hdkinds · rule
• hdkinds · agent
• hdedges · caused_by
• hdedges · fixed_by
• effects · read
• effects · act
• reader_kinds · rule
• script_functions · sma
• script_builtins · entry
• tiers · case
• hosts · start

the source

// generated by genie import from lang/gen/lambda-flows.json (flow:helpdesk-case) — a lambda flow as a genie machine: every node a state, every edge a move; a guard node's edge carries its pass; an act node's entry signs behind the lambda's standard arm.
genie flow_helpdesk_case v1
about "A helpdesk case: asked → routed → answered → graded → settled → recorded, sealed per tenant: sma-helpdesk.cue machine as a flow; every outlet (embed, chrome, mcp, plugin, n8n, teams, slack, api, cli) enters at the same trigger; the act writes nothing on chain: the settlement is the meter line on the key"

use chain every

agent helpdesk_case is "A helpdesk case: asked → routed → answered → graded → settled → recorded, sealed per tenant"
  states start graph route directory answer grade meter_node learn recorded
  start start
  final learn recorded
  on event asked
  move start -> graph component sma-graph
  move graph -> route component sma-helpdesk
  move route -> directory component sma-directory
  move directory -> answer component sma-helpdesk
  move answer -> grade component jev
  move grade -> meter_node component grid-meter
  move meter_node -> learn component sma-graph
  move meter_node -> recorded component coord-stream
  next graph route "then route"
  next route directory "then directory"
  next directory answer "then answer"
  next answer grade "then grade"
  next grade meter_node "then meter"
  next meter_node learn "then learn"

knowledge
  symptom "A helpdesk case: asked → routed → answered → graded → settled → recorded, sealed per tenant stops …" caused_by "a guard node did not pass" fixed_by "read the guard's expect in the flow, fix the input, run again"
  rule "A helpdesk case: asked → routed → answered → graded → settled → recorded, sealed per tenant: an …"