Skip to main content
Register, monitor, and coordinate service repos that share context through a parent GTM workspace.

​
Usage

tenet services list                    # Show registered services
tenet services register <path>         # Register a service repo
tenet services status                  # Health check all services
tenet services deps                    # Show dependency graph

​
How Services Work

A TENET workspace can have child services — separate repos that share context: 
GTM (parent workspace)
├── .tenet/config.json         # lists registered services
├── knowledge/                 # shared context
│
├── api-service/               # child service
│   └── .tenet/config.json     # type: "service", gtm_parent: "../"
│
└── web-app/                   # child service  
    └── .tenet/config.json

​
Registering a Service

cd my-gtm-workspace
tenet services register ../api-service
This:
  1. Creates .tenet/config.json in the service with type: "service"
  2. Registers the service in the parent GTM config
  3. Sets up scope-based event routing between them

​
Service Scopes

Services declare what they produce and consume: 
{
  "scopes": {
    "produces": ["api:schema-change"],
    "consumes": ["auth:user-created"]
  }
}
When one service produces an event, consuming services get notified.

​
See Also