Overview
Knowledge base and help center platform. Modus mines each brand you select and keeps that context current.
What Modus reads
- 1Brand
- 2Category
- 2Article
- 3Section
You select the level Modus is allowed to mine. Everything below it is discovered automatically; everything outside it is never touched.
4context types mined
1agent tool groups
1connection method
4security controls
Context types
Each object Modus mines produces typed context items, addressed by their position in the hierarchy. This is what an agent actually receives.
Brand metadata
Names, structure, and relationships for each Brand.
Category metadata
Names, structure, and relationships for each Category.
Section metadata
Names, structure, and relationships for each Section.
Article metadata
Help Center article identity leaf.
Connection method
Connect once. Modus stores credentials in a managed secret store, rotates what it can, and never asks an agent to handle them.
Managed credentials
The credential Modus asks for when you connect. It is stored as a secret and never handed to an agent.
Security & governance
Governance is applied once, at the layer every agent runs through, so it holds no matter which agent asks.
Metadata-first mining
Modus learns from structure and usage, not bulk data. Raw records stay in your environment; only the metadata needed to understand the system is stored.
Scoped selection
You choose exactly which schemas, folders, spaces, or boards Modus is allowed to see. Nothing outside the selection is ever mined.
Group access by sensitivity
Map your identity groups to sensitivity tiers so each team only ever composes context at or below its clearance.
Read-only by default
Mining runs on a read-only credential. Any tool that writes back is a separate, explicitly granted action.