OOpenclawnet
  • Introduction
  • Docs
      • 20260425 concept review
      • 20260503 repo split decision
      • Agent runtime
      • Components
      • Glossary
      • Jobs
      • Memory service proposal
      • Nemoclaw mapping
      • Openclaw mapping
      • Overview
      • Provider model
      • Runtime flow
      • Scenarios s4 s5 plan
      • Secrets vault admin ui
      • Secrets vault azure readiness
      • Secrets vault evolution
      • Secrets vault lifecycle phase4
      • Secrets vault lifecycle phase5
      • Secrets vault phase5
      • Secrets vault phase6
      • Secrets vault threat model
      • Source of truth rules
      • Storage
  • Scripts
  • Sessions
    • RELEASE CHECKLIST
    • Session 2 guide es
    • Session 2 guide
    • Session 3 guide es
    • Session 3 guide
    • Session 4 guide es
    • Session 4 guide
    • Session 5 guide es
    • Session 5 guide
    • Speakers
  • Src
  • Tests
Powered by Docsbook
Docs/Architecture/20260425 concept review
IntroductionPrevious20260503 repo split decisionNext

On this page

  • 1. Executive Summary
  • 2. Conceptual Model — Walkthrough
  • 2.1 Entity Relationship Diagram
  • 2.2 Model Providers
  • 2.3 MCP Tools (External)
  • 2.4 Internal Tools
  • 2.5 Agents (Agent Profiles)
  • 2.6 Job Definitions (ScheduledJob)
  • 2.7 Job Runs
  • 2.8 Channels
  • 3. Validate Bruno's Mental Model
  • Statement 1: "We have a collection of available LLMs models in the Model Provider section"
  • Statement 2: "We have a collection of MCP tools"
  • Statement 3: "We have a collection of internal tools"
  • Statement 4: "Each agent will use a model provider, and can choose which tools may use"
  • Statement 5: "Each agent can also choose which MCP tools will be used"
  • Statement 6: "Note: explain how the tool approval system works here?"
  • Statement 7: "We have a collection of job definitions"
  • Statement 8: "Each job is a prompt action that will use an Agent, and will run in different modes: run-once, scheduled, webhook"
  • Statement 9: "Question: Is the job definition supposed to have a state active, disabled, cancelled, deprecated?"
  • Statement 10: "Should we also keep an history of the job definition state change logs?"
  • Statement 11: "We have a collection of job runs, that represents the total execution of a job run"
  • Statement 12: "Note: how the chat feature applies here? Can be considered a job run?"
  • Statement 13: "Each job definition is also considered a channel, so in the channel website we can browse and see the jobs history and more details"
  • 4. Open Questions — Bruno's Direct Questions
  • 4a. Tool Approval System
  • 4b. Job Definition State Machine
  • 4c. Chat as Job Run?
  • 4.5 Recommendations Adopted (Implementation Plan)
  • 5. Improvement Opportunities
  • 🔒 Security
  • ✨ UX
  • 🎤 Demo Storytelling
  • 🧪 Tests
  • 📚 Docs
  • 6. Recommended Next Sprint (5–7 Issues)
  • Appendix: Key File References

Was this page helpful?