Runtime Relationship & Process

This page focuses on two things:

• how the four roles collaborate
• how runtime processes are started and connected

1. Role Relationship

• console is the control center: manages agent registry and receives config/service/extension operational commands.
• agent is the execution center: handles message/task/tool execution and persistence in each project.
• service is the core domain layer: provides primary business workflows.
• extension is the optional capability layer: provides shared enhancements across agents.

In one line:

console governs, agent runs, service/extension provide capabilities.

2. Process Startup Model

1. Start console: city console start
2. Start agent in project: city agent start
3. Agent runtime loads config layers (project ship.json.services.* + console-global ~/.ship/ship.db extensions_config.* + global model pool)
4. Inbound messages/tasks enter agent scheduling
5. Agent invokes service/extension to complete execution
6. Runtime traces are persisted to .ship/*

3. Operational Checklist

city console status
city agent status .
city service list
city extension list

Related Docs

• Architecture Logic Map
• Service vs Extension
• Service Runtime
• Extension Runtime
• city console
• city agent