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/Openclaw mapping
Nemoclaw mappingPreviousOverviewNext

On this page

  • Overview
  • Core Concepts Mapping
  • Architecture Layers
  • 1. Orchestration Layer (AppHost)
  • 2. Gateway Layer — Control Plane
  • 3. Agent Layer (Agent + Runtime)
  • 4. Provider Layer (Models)
  • 5. Tool Layer (Tools)
  • 6. Memory Layer (Memory + Embeddings)
  • 7. Persistence Layer (Storage)
  • 8. UI Layer (Blazor Web App)
  • 9. Channel Layer (Adapters)
  • Data Flow Example: Chat Request
  • Data Flow Example: Channel Message (Teams)
  • Key Design Decisions
  • 1. Interface-Driven Everything
  • 2. Local-First, Cloud-Optional
  • 3. Gateway as Control Plane
  • 4. Workspace-Aware Sessions
  • 5. Safety by Design
  • 6. Educational Structure
  • 7. Pluggable DI Architecture
  • Comparison Table: OpenClaw Pillar → .NET Realization
  • Future Evolution
  • Conclusion

Was this page helpful?