Busabase × IronClaw
Knowledge Base for IronClaw
Shared records behind an explicit extension boundary
IronClaw provides its own agent runtime and memory. Busabase adds Docs and Bases for facts that a team must share, maintain and review. Keep runtime memory for execution, and read the current shared record before making a business decision.
Connection guide →
Secure execution still needs accountable knowledge
Sandboxing, network controls and credentials govern tool execution. Knowledge records explain the source, accountable owner and accepted conclusion. A safely executed tool does not establish that its information is current. Carry the source, scope and owner together so the next task can judge applicability.
Put operating guidance in a Doc and maintained facts in a Base. Link each fact to its explanation and evidence, with an owner, current state and open questions. IronClaw reads that set before execution and returns output links and actual checks afterward, allowing another task to continue from records instead of guessing what the previous run did.
What belongs where
Policy Doc
The complete policy, audience, exceptions and source. Its owner maintains the explanation.
Knowledge Base
One record per maintained fact: stable key, value, source URL, owner, scope and state. Link it to the policy Doc.
Update Skill
The reading, evidence and proposal procedure. It guides the agent without granting data access.
Result record
Link the task to its output, the decision and unresolved checks. The next run reads the actual result.
Choose a supported route before checking data access
The current Busabase guide uses Skill/CLI or REST through shell execution. Resolve local-tool availability first, allow the required endpoint through network controls, and use minimum necessary credentials. The MCP extension guide is not an arbitrary-URL installer, and another service’s extension does not establish that a Busabase extension exists.
Separate access failures from missing knowledge
An inaccessible record is not an absent record: identify the object and permission needed. If evidence is weak despite access, state which source is missing and who should supply it. After recovery, reread the current version before resuming. Preserve the investigation instead of broadening access or duplicating the knowledge base to bypass the problem.
Leave a checkable handoff
A useful handoff identifies the exact record that was read, the source that supported the answer, and the applicable scope. For a proposed edit, return the ChangeRequest link and the fields it would change. When a change is accepted, return the canonical record and verify the resulting value. Keep these outcomes distinct so the next agent can tell what it can rely on.
Start with one fact you already maintain
- 01
Select an existing policy or fact with a known source. Assign its owner before asking the agent to change it.
- 02
Read the current record and have the agent return the source, applicable scope and version. Check those before allowing a write.
- 03
Propose a bounded update with old and new values, the reason and evidence. When review is required, keep it as a proposal until an authorized decision.
- 04
Read the accepted record again from a fresh task. Check the value and source, and keep rejected or unresolved changes out of the answer.
Connection and permission boundaries
IronClaw exposes remote MCP tools through packaged extensions using HTTP(S); its official guide explicitly excludes stdio transport. Installing or activating an extension does not grant arbitrary record access. A trusted Skill is execution guidance, not a data permission. Use only a connection route your deployed runtime supports; keep CLI/REST alternatives separate from a claimed MCP compatibility test. For Busabase, the documented route is Skill/CLI or REST through enabled local shell tools, not an arbitrary MCP URL.
An instruction to adapt
Read the shared operating procedure and linked records with the current account. List inaccessible sources separately. Propose only the supported corrections, retain their evidence, and return the canonical record after an authorized merge.
Questions before you connect
Can I add the Busabase MCP URL as an arbitrary server?
The documented IronClaw path uses packaged MCP extensions. For Busabase follow the Skill/CLI or REST route in the connection guide, with local tools and network access enabled as required.
Will this replace native memory?
Keep native context for execution and private preferences. Share only the knowledge that another person needs to read, verify or maintain.
How do I check one useful cycle?
Read one existing record and return its link and source. Propose one supported correction, inspect the change, then read the accepted record again. A proposal link is not proof that the record changed.