work-intake-node-shaping

name	work-intake-node-shaping
description	Classify a single operator WorkIntent's signal vector (coupling, context pressure, skill boundary, review independence, budget, operator burden) into exactly one of the seven topology archetypes (node, scout, chain, DAG-workgroup, tournament, ambient-watcher, human-gate), and audit that legacy launch verbs (spawn/dispatch/sortie/conjure/nightshift) stay compatibility metadata instead of writing independent Agent Node/session/transcript state. Use when routing a new WorkIntent to a topology before any Agent Node is materialized, auditing whether a launch path secretly opens parallel governance state, or reviewing a control-plane PR that adds a new legacy-verb compatibility shim. NOT for the inter-agent protocol mechanics once a workgroup or tournament is actually summoned (use swarm-invocation-designer), decomposing the work into sub-tasks or building/scheduling the DAG graph after a DAG-workgroup archetype is chosen (use task-decomposer or next-move), picking which specific skill or subagent fills a chosen node (use skillful-subagent-creator), or designing the approval mechanics of a chosen human-gate archetype (use human-gate-designer).
license	Apache-2.0
allowed-tools	Read,Write,Edit,Bash,Grep,Glob
metadata	{"category":"Agent & Orchestration","tags":["work-intake","topology-archetype","single-operator-action","legacy-verb-compat","agent-node-governance"],"provenance":{"kind":"first-party","owners":["port-daddy"]},"pairs-with":[{"skill":"swarm-invocation-designer","reason":"Once a chain/dag-workgroup/tournament archetype is chosen, this skill hands off the actual inter-agent invocation and coordination mechanics to it."},{"skill":"task-decomposer","reason":"A dag-workgroup or chain archetype still needs its sub-tasks decomposed; this skill only proves the archetype call itself is singular and legacy-safe."},{"skill":"next-move","reason":"next-move's synthesizer picks a planning/runtime topology per subtask; this skill is the upstream gate proving the operator-level WorkIntent resolved to one archetype before that DAG is even built."}],"io-contract":{"kind":"deliverable","consumes":["[Truncated]","[Truncated]"],"produces":["[Truncated]","[Truncated]"]}}

Work Intake Node Shaping

Route one operator WorkIntent to exactly one topology archetype, and keep legacy launch verbs as compatibility metadata instead of a second, ungoverned path to an Agent Node.

Use This For

• Classifying a new WorkIntent's signal vector into exactly one of the seven topology archetypes before any Agent Node is materialized.
• Auditing a spawn/dispatch/sortie/conjure/nightshift compatibility shim to confirm it routes into the shared WorkIntent -> WorkPlan pipeline instead of writing its own session/transcript state.
• Reviewing a control-plane PR that adds a new launch entrypoint, to catch a second, independent archetype decision hiding behind a different verb.
• Deciding whether ambiguous work (a "quick fix" vs. a "long research chain" vs. a "recurring watcher") should be a node, scout, or ambient-watcher before committing budget and skills to it.
• Grading a proposed WorkIntent-to-archetype mapping against the "exactly one archetype" invariant before it reaches the daemon.

Do Not Use This For

• Inter-agent protocol/IPC mechanics once a workgroup or tournament is actually summoned (swarm-invocation-designer).
• Decomposing the work into sub-tasks or building/scheduling the DAG graph after a DAG-workgroup archetype is chosen (task-decomposer, next-move).
• Picking which specific skill or subagent fills a chosen node, or designing a chosen human-gate's approval mechanics (skillful-subagent-creator, human-gate-designer).

Decision Model

flowchart TD
  A[Operator WorkIntent + six-signal vector] --> B{Score coupling, context pressure, skill boundary, review independence, budget, operator burden}
  B --> C{Exactly one archetype fits?}
  C -->|Zero or many tie| D[Reject: rescore the signal vector, do not launch multiple]
  C -->|Yes| E[Select one: node / scout / chain / dag-workgroup / tournament / ambient-watcher / human-gate]
  E --> F{Legacy verb reachable? spawn/dispatch/sortie/conjure/nightshift}
  F -->|Yes| G{Does it write its own Agent Node/session/transcript?}
  G -->|Yes| H[FAIL: legacy verb bypasses the shared WorkPlan pipeline]
  G -->|No| I[OK: legacy verb is compatibility metadata only]
  F -->|No| I
  I --> J[Materialize exactly one governed Agent Node]

1. Capture the WorkIntent's six-signal vector — coupling, context pressure, skill boundary, review independence, budget, operator burden. See references/seven-archetypes.md for what each signal measures.