Seventeen terms that recur across the platform, the methodology paper, and the reporting surface. Plain definitions, no marketing wrapper.
Community intelligence is the practice of treating an audience as a structured, scorable population — not a feed to listen to. Every account is ranked across archetypes, filtered for authenticity, and converted into a decision queue. Listening tools tell you what is being said; community intelligence tells you who to talk to next, and what to do with them.
Archetype scoring is the CommunityOS classification method. Every account in a scan receives a score against four archetypes — Champion, Amplifier, Builder, Early Adopter. Scoring is deterministic: 60 percent linguistic features, 40 percent normalized vanity metrics. The same inputs always produce the same outputs.
A Champion is an account that speaks about you with substance and conviction. They write threads, they argue your case in replies, they defend the brand without prompting. Champions carry the brand's voice forward in rooms you cannot enter.
An Amplifier carries reach. They share, quote, and distribute. Their archetype score is driven by audience size normalized against engagement quality — not raw follower count. Amplifiers move messages into adjacent rooms quickly.
A Builder ships things. Original content, working tools, threads with original analysis. Builders are the highest-density signal in a community — small in number, large in influence on what gets considered serious.
An Early Adopter shows up before it's obvious. They follow at low follower counts, they engage on cold posts, they test new surfaces first. Early Adopters are the signal that a community is forming, not just an audience.
Bot-Kill is a pre-campaign filtering layer that removes bots, engagement farms, and inactive shells before scoring runs. It catches activity-floor failures, follower-to-following imbalances, farm-cluster posting patterns, and linguistic uniformity across networks. Accounts removed by Bot-Kill never appear in the Act Now queue and never influence reports.
A Light scan is the standard analysis pass. It pulls follower lists, recent posts, and engagement metrics for every account in the surface, runs Bot-Kill, scores survivors across the four archetypes, and lands accounts in the five action buckets. The Light scan is what feeds the Act Now queue.
A Deep scan is an expanded analysis on a subset of high-scoring accounts. It pulls extended post history, thread structure, and topical depth across a longer window. Deep scans are advisory — they add evidence to a profile without changing the bucket assignment from the Light scan.
The Loop is the six-stage cycle that defines the CommunityOS workflow: People → Intelligence → Activation → Proof → Reward → Report. Every stage feeds the next, and nothing counts as done until it is verified through Proof Review.
Mission Ops is the activation surface. Operators run outreach missions from inside the Act Now queue — drafted openers, suggested next actions, and per-account context all live in the same view. Mission Ops never sends automatically; every interaction is operator-driven.
Proof Review is the verification layer. Operators approve completed missions against real artifacts — a posted thread, a real reply, real engagement. Approved missions release the reward. Rejected missions return to the queue with a reason. Nothing enters the report until it has passed Proof Review.
The Act Now queue is the decision page. It is a ranked, time-bounded list of accounts who deserve an operator's attention this week. Every row carries the reason it ranked and the suggested next action. The queue is the surface an operator works from; the rest of the platform exists to keep it accurate.
A micro-amplifier is a real community member — not a paid KOL — who carries an audience large enough to move a campaign and small enough to remain authentic. CommunityOS's purpose is to find, score, and activate micro-amplifiers as a replacement for KOL spend.
A Snapshot is a saved scan state. Snapshots let operators compare audience composition across time — for example, how many new Champions appeared between two campaigns, or how the Amplifier mix shifted after a launch. Snapshots are the audience delta in the ROI Report.
A Cohort is a saved selection of accounts inside a scan. Cohorts can be exported, imported into outreach tools, or scored against future scans to track movement. Common cohorts: top 100 Champions, all Builders in the last 90 days, Early Adopters who turned into Amplifiers.
Audience delta is the composition change between two scans. It answers: who is new, who left, who moved archetypes, and how the mix shifted. Audience delta is the part of the ROI Report a CFO can read in 30 seconds — specific, traceable, comparable quarter to quarter.
Every term above corresponds to a surface in the operator app. Join the waitlist to walk through the live build.