Skip to content

📚 Knowledge Categories

Three types. Three owners. One goal: move fast without getting blocked.

We organize knowledge by who owns it and how you use it—from the tools you master to the domains you operate in.

🛠️ The Three Types

🔧 1. Extensive Knowledge (Your Craft)

The tools, languages, and platforms you need to do your job. Think: programming languages, design tools, cloud platforms, frameworks, protocols.

  • Who owns it: You do. Your responsibility to grow.
  • What we provide: Context on how we use these tools.
  • Measured by: KAI—your proficiency in the tech stack.

Example: A backend engineer needs Python, Docker, Postgres. A designer needs Figma and prototyping tools.

🌐 2. Realm Knowledge (Domain Expertise)

The broader concepts and domains that shape how we think about problems.

  • What it covers: Privacy tech, mobile hardware, open-source ecosystems, dev relations, etc.
  • Who needs it: Managers and senior ICs who operate across areas.
  • Measured by: Leadership frameworks requiring proficiency in Realms.

Example: A PM on BraX3 needs to understand hardware constraints, privacy regulations, and user behavior.

🏛️ 3. Organizational Knowledge (How We Work)

Everything about how Brax operates:

  • What our products do and how they work
  • How teams collaborate and ship
  • Processes, rituals, and systems
  • Strategic priorities and how your work connects

Who owns it: We do—training and onboarding ensure everyone has context.

Why it matters: Tech people need to understand the business. Non-tech people need to understand the tech. Everyone needs the "why."

📝 How We Share Knowledge

People learn in different ways. We support two formats:

  1. Self-serve docs → Our internal wiki for reference, how-tos, and decision records
  2. Live sessions → Learning Day for deeper dives, hands-on practice, and Q&A

✅ What Good Knowledge Management Solves

🚧 Problems We Avoid

  • One-to-one bottlenecks → Experts aren't trapped answering the same question 50 times
  • Lost in chat → Context isn't buried in Slack threads
  • Outdated docs → Pages have owners; stale content gets flagged
  • Tribal knowledge → Critical info isn't stuck in one person's head
  • Onboarding chaos → New hires get clear paths, not random tips

❌ Where Knowledge Should NOT Live

  • Only in someone's head
  • Scattered across email threads
  • In forgotten PDFs nobody can find
  • In outdated manuals that mislead

✅ Where Knowledge SHOULD Live

  • In searchable, tagged, owned docs
  • In decision records that explain the "why"
  • In runbooks, guides, and templates
  • In experts' heads—and written down for everyone

\