Organization Knowledge

Give Caddie approved organization context without exposing secrets.

Organization knowledge gives Caddie context about your team, workflows, connectors, conventions, and prior outcomes. It helps Caddie make better plans and debug faster while staying inside the organization's access boundary.

Knowledge Sources

Source type	Examples
Workflow	Existing workflow definitions, titles, descriptions, props, and patterns
Connector	Provider names and available connector types without revealing secrets
Memory	Useful facts extracted from prior Caddie interactions or workflow outcomes
Manual	Curated notes added by the organization
Run pattern	Repeated runtime behavior, failures, or successful execution patterns

Retrieval Flow

graph LR
Context[User request] --> Query[Build retrieval query]
Query --> Search[Search org knowledge]
Search --> Rank[Rank relevant chunks]
Rank --> Agent[Caddie context]
Agent --> Plan[Workflow plan or answer]

What to Store

Good organization knowledge is operational and non-secret:

Store	Avoid
Naming conventions	API tokens
Preferred chains and assets	Wallet signing material
Approved Slack channels	Webhook secrets
Wallet policy notes	Raw connector credentials
Customer or protocol routing metadata	Sensitive personal data not needed for automation
Incident and runbook summaries	Internal secrets or privileged prompts

Store facts like "large transfers require review" or "alerts go to #protocol-ops." Keep secret material in connectors, API keys, service accounts, or wallet controls.

Caddie Profile

An organization Caddie profile can describe preferences such as tone, default chains, operational rules, naming conventions, review requirements, and workflow style. Keep it concise and directive.

md
Default chain: BasePreferred alert channel: protocol-opsBefore wallet transactions: add a policy branch and require a test runNaming: use verb-object names for workflow titles

Maintenance

Remove stale facts when provider accounts, wallet policy, or org structure changes.
Prefer short, specific knowledge entries over long internal documents.
Avoid copying secrets or private incident data into knowledge.
Use successful templates as reusable knowledge instead of repeatedly explaining the same pattern.
Review knowledge when Caddie starts making outdated assumptions.

Was this page helpful?

Previous MCP Server

Next Organizations