Platform type vs Interaction mode

NetTree stores two separate fields on each public link source. They answer different questions:

Workflow routing uses Interaction mode first. Changing Platform type alone does not move a queue item between Directory Submit, Comment Assistant, Guest Pitch, or Content Publish.

Platform type — classification and matching

Platform type describes the role of the destination in the broader ecosystem. It powers Plaza browsing, filters, fit scoring, and ops taxonomy — not the day-to-day workflow screen.

Common values:

Used for:

• Plaza Type column and kind-based filters
• Site–source match and recommendation priors
• Ops remarks and import provenance
• Default Interaction mode when mode is empty (see below)

Platform type does not by itself decide which workflow picker lists a queued item.

Interaction mode — workflow routing

Interaction mode describes the operator action NetTree expects on that destination. It maps 1:1 to a workflow:

Used for:

• Which workflow list shows a site queue item
• Draft templates and step copy per workflow
• Tracker workflow type on synced records
• Value stored on sitesourcequeue.interaction_mode when you Add to site

When you open Directory Submit and do not see an expected destination, check Interaction mode before Platform type.

Why both fields exist

Many destinations do not have a strict 1:1 mapping between “what the site is” and “how you use it”:

Platform type supports library organization and matching. Interaction mode supports execution and routing. Keeping both avoids forcing every edge case into a single dropdown.

How routing is resolved (queue → workflow)

When NetTree decides which workflow owns a queue item, it evaluates (in order):

1. linksources.interactionmode on the source (if set)
2. sitesourcequeue.interaction_mode captured at add-to-queue time
3. Legacy workflowTag in ops notes (import metadata)
4. Domain rules (e.g. known publishing platforms → owned channel)
5. Default from Platform type if nothing else is set

flowchart TD
  A[Queue item] --> B{Source interaction_mode set?}
  B -->|Yes| C[Use source mode]
  B -->|No| D{Queue interaction_mode?}
  D -->|Yes| E[Use queue mode]
  D -->|No| F[Infer from domain + platform type]
  C --> G[Map to workflow]
  E --> G
  F --> G

Important: Ops notes such as workflowTag: directorylisting in import sheets are not read by the workflow picker. Only persisted interactionmode fields (and kind/domain fallbacks) drive routing.

Default Interaction mode from Platform type

When Interaction mode is empty, NetTree infers:

Known publishing domains (Tumblr, Medium, GitHub, etc.) can override to owned_channel regardless of type.

Changing Platform type in admin — what updates automatically

In Admin → Public sources (/admin/sources/[id]):

• Updating Platform type alone does not clear an existing Interaction mode.
• If Interaction mode was already set (e.g. blog_comment from an earlier community type), it stays until you change it manually.
• Interaction mode is only re-inferred when it was previously null/empty.

This prevents accidental rerouting of in-flight queue items, but it explains cases like:

Platform type = launchplatform, Interaction mode still = blogcomment → item stays in Comment Assistant, not Directory Submit.

Operator checklist

After fixing Interaction mode, reload the target workflow with the site filter, or open Site queue → continue into the correct workflow.

Example: startupfa.me

Correct pairing for a product launch listing site: launchplatform + directorylisting.

Related

• Workflows overview — four workflow screens and shared steps
• Link libraries — Plaza, queue, and add-to-site behavior
• Glossary — status and product terms
• Admin source editor: /admin/sources (platform admins only)