Organization knowledge gives B3OS reusable context about your business, policies, schemas, examples, and preferences. Use it to make Caddie-assisted workflows more consistent without hardcoding secrets into prompts or workflow payloads.

Knowledge-grounded workflow draft
groundingrequestinspect before publish Organization knowledge Policies, examples, glossary, preferred patterns Builder prompt Outcome and constraints from the user Draft workflow Workflow graph, props, connectors, branches Human review Validate schemas, side effects, public paths

What to Store

Good knowledgeAvoid
Business rules and approval policiesWallet signing material, API tokens, recovery phrases
Preferred chains, tokens, and connector namesRaw provider credentials
Common workflow examplesCustomer data that does not need to be reused
Glossary and naming conventionsTemporary debugging notes

Prompt the Builder

text
Build a workflow that checks the organization's preferred treasury wallet for high-value inbound ERC20 transfers on Base, enriches the token with market data, and sends a Slack alert. Use the organization's normal alerting channel and require human approval before any wallet write action.

Operate the Knowledge Base

1

Create focused knowledge entries

Keep one policy, schema, or example per entry so updates are easy to review.

2

Pin canonical guidance

Pin the few entries that should dominate Caddie workflow generation and troubleshooting.

3

Review Caddie-assisted workflows

Treat Caddie output as a draft. Validate schemas, connectors, wallet boundaries, and side effects before publishing.

Caddie

Learn how Caddie creates, repairs, and explains workflows.

Learn More
Organization Knowledge

Manage knowledge settings, entries, and grounding behavior.

Learn More
Security

Keep secrets, connectors, and wallet capabilities out of public docs and prompts.

Learn More
Ask a question... ⌘I