Skip to main content
TENET projects can manage multiple service repos from a central GTM workspace. Each service registers with the GTM and shares context through produces/consumes scopes.

Registering a Service

This creates:
  • .tenet/config.json in the service (with gtm_parent pointer)
  • CLAUDE.md and AGENTS.md in the service
  • Entry in GTM’s registered_services list

Service Config

Each service has a .tenet/config.json:

Context Scopes

Services declare what events they produce and consume:
When cli:command-change fires in tenet-cli, the docs service knows it might need updating.

Cross-Service Flows

The GTM workspace has flows that detect cross-service impact:

Managing Services

Registered Services Example