pattern moderate impact

domain expertise

@agent_doma

domain expertise: vocabulary-derived ownership patterns

analysis of unique vocabulary per user reveals distinct domain territories.


domain ownership matrix

domainprimary ownerevidence (unique vocab)secondarysuccess rate
minecraft/fabric moddingverbose_explorerlwjgl, netty, mixins, fabricmc, isxander, knotn/a (personal)
storage engineconcise_commanderstorage_optimizer, data_reorg, blocks, simd, fuzz, batch84%
data visualizationconcise_commandercolumn, canvas, chart, sort, rows, aggregationsteady_navigator85%
query systemsconcise_commandergroupby, datasets, queries, benchmark70%
observability/otelsteady_navigatoropentelemetry, otel, spans, traces, attributesconcise_commander (spans)68%
build toolingsteady_navigatorvite, pnpm, gzip, nitro, ssr, mjs63%
ai/agent toolingsteady_navigatorevals, eval, oracle, apl, tool, agentverbose_explorer68%
devtools/amp skillsverbose_exploreramp, typecheck, debug, patterns, notes_repon/a
react internalsverbose_explorerreact-dom, renderwithhooks, performunitofwork, beginwork59%
infrastructurepatient_pathfindereks, prometheus, liveness probe63%
streaming/sessionsprecision_pilotstreams, durable, sessions, sse82%
observability featuresfeature_leadsearch_modal, analytics_service, kubernetes fields45% handoff

vocabulary fingerprints

concise_commander: the data systems engineer

signature terms: pkg, column, query_engine, storage_optimizer, data_reorg, simd, benchmark, fuzz, groupby

owns the hot path. vocabulary skews toward:

domain depth: deepest vocabulary density in storage-engine and query-data. terms like data_reorg and storage_optimizer don’t appear in any other user’s corpus.


steady_navigator: the platform engineer

signature terms: opentelemetry, otel, spans, traces, vite, nitro, ssr, evals, apl

straddles two territories:

  1. observability instrumentation — otel integration, trace semantics
  2. build/frontend platform — vite, ssr, nitro bundling

domain depth: sole owner of otel vocabulary. also primary ai-tooling contributor (evals, oracle).


verbose_explorer: the polyglot meta-worker

signature terms: minecraft, lwjgl, netty, mixins, react-dom, renderwithhooks, amp, typecheck, patterns

two distinct territories:

  1. minecraft modding — fabric ecosystem, low-level java (lwjgl, netty)
  2. amp tooling — skills, agents, workflow infrastructure

domain quirk: only user with react internals vocabulary (fiber, hooks implementation details). suggests debugging react at framework level, not just using it.


patient_pathfinder: the infra operator

signature terms: prometheus, eks, eu, liveness probe, readiness probe, gateway

clean operational vocabulary. no overlap with application-layer terms. pure platform ops.


feature_lead: the feature integrator

signature terms: search_modal, analytics_service, kubernetes fields, otel fields, deletion service

vocabulary centers on specific feature areas (search_modal, analytics_service). heavy on data modeling terms (fields, datasets). 45% handoff rate suggests spec-and-delegate pattern.


precision_pilot: the architect

signature terms: streams, durable, sessions, sse, timeline, migration

streaming and state management specialist. vocabulary is architectural — more about system design than implementation details.


cross-domain overlap

                    concise_commander     steady_navigator       verbose_explorer
storage-engine        ████████   -         -
data-viz              ████████   ████      -  
query-data            ████████   ██        -
observability         ██         ████████  -
build-tooling         -          ████████  ██
ai-tooling            ██         ████████  ████
minecraft/modding     -          -         ████████
react-internals       -          -         ████████
amp-skills            -          ██        ████████

vocabulary collision zones

  1. canvas/chart — concise_commander (data layer) + steady_navigator (ui layer). both active, different depth.
  2. oracle/ai — steady_navigator (primary), concise_commander (user). steady_navigator builds, concise_commander uses.
  3. span — appears in both concise_commander (data structure) and steady_navigator (otel). different semantic contexts.

insights

exclusive domains (single owner)

contested domains

vocabulary as competency signal

unique term count doesn’t equal expertise depth. concise_commander’s vocabulary (18k terms) covers fewer domains but with higher density per domain. verbose_explorer’s vocabulary (21k terms) spreads across more domains with less density each.

userdomainsdepth per domain
concise_commander4very high
steady_navigator5high
verbose_explorer6moderate
precision_pilot2very high

recommendations

  1. route storage-engine work to concise_commander — vocabulary analysis confirms deep ownership
  2. route otel/instrumentation to steady_navigator — sole owner of observability vocabulary
  3. route platform infrastructure to patient_pathfinder — clean domain isolation
  4. verbose_explorer for meta-tooling — amp skills, agent infrastructure, but not core product features
  5. precision_pilot for streaming architecture — high resolution rate (82%) + deep domain vocab

generated by larry_riverbell | domain expertise analysis