Glossary

Glossary

The working lexicon. This page mirrors the canonical glossary in Lokomotif_AI_Positioning_Brief.md § 11 — keep them in sync. Voice gate is intentionally skipped on this page because the retired-phrases section documents the very phrases the gate blocks.

Terms the firm owns

These are named frameworks and category terms. Use them as proper-noun concepts; capitalize when referenced as concepts.

  • Corporate AI Adoption Partner — the firm’s category claim.
  • The Lokomotif Method — umbrella name for the firm’s proprietary approach.
  • RTCSG — the five-layer prompt architecture (Role, Task & Format, Context & Constraint, Style & Tone, Guardrail).
  • The AI Maturity Spectrum — the four-state diagnostic model (AI-Absent, AI-Curious, AI-Integrated, AI-Native).
  • The Three-Horizon Adoption Journey — the practice architecture (Adoption Sprint, Workflow Rewire, Agentic Scale), entered via Diagnostic.
  • Adoption Sprint, Workflow Rewire, Agentic Scale — the three named practices.
  • The Diagnostic — the fixed-scope entry engagement.
  • Open Programs — productized public trainings. Not Academy. Not courses.
  • The Leveraged Agency Model — the five-year product ladder (Services → Productized Service → Product, with audience underneath).
  • Komünite — always spelled with Turkish diacritics. Not translated.
  • Komünite Space — the physical hub. Always capitalized.

Industry taxonomy

The 16 entries the schema accepts in industry. Extending requires an RFC.

finance · banking · insurance · retail · e-commerce · logistics · healthcare · manufacturing · energy · telco · media · hr · legal · public-sector · education · cross-industry

Phrases to use

Operational category vocabulary that should appear naturally across surfaces — without feeling repeated.

  • operating model design
  • workflow redesign / workflow rewire
  • agentic transformation / agentic scale / agentic workflows
  • measurable transformation
  • methodology-led
  • frontier-connected
  • community-powered
  • baseline, delta, and ROI case
  • operating rhythm
  • guardrails and observability
  • the adoption gap
  • from AI-absent to AI-native
  • the Phase 3 shift

Phrases to retire

Legacy phrases from the AI-solutions and AI-academy era. They weaken the category claim and are removed from every public surface, including archived content where feasible.

  • “AI solutions” — generic, category-blind.
  • “AI training academy” — positions the firm as training-first.
  • “End-to-end AI services” — positions the firm as a dev shop.
  • “Digitize your business” — era-incorrect; AI is not digitization.
  • “Simplify your complex processes” — generic consulting language.
  • “Integrations in days” — velocity framing typical of agencies.
  • “MVP in 12 weeks” — dev-shop framing.
  • “Your trusted AI partner” — parity language, no differentiation.
  • “AI-powered” as a modifier applied to generic offerings.
  • “Revolutionary” / “next-gen” / “cutting-edge” — all hype-category.
  • “Empower your team” — generic; specific outcomes replace this.
  • “Certificate of completion” as a primary value proposition on training pages.

The voice gate scans every MDX page for the strings above (case-insensitive). A page that needs to reference them — like this one — opts out via voice_gate: skip in its frontmatter.

Bilingual surface guidance

Two language rules govern Turkish and English surfaces:

  • Technical category terms stay in English. RTCSG, agentic, operating model, workflow rewire, Agentic Scale, Adoption Sprint, Open Program — these do not translate. They are proper nouns in both languages. Komünite stays in Turkish in both languages.
  • Surrounding prose is written native, not translated. Turkish surfaces are written in native Turkish, by Turkish writers, with English category terms embedded. Direct translation from English to Turkish (or vice versa) produces surfaces that feel imported in both directions.
RFCsHoş Geldiniz