SAService Architect Back to designer
SAService ArchitectDocumentation
Code GenerationGenerated project structure
Code generation project root

Workspace layout

The root joins generated services, contracts, local infrastructure and operations into one reproducible workspace.

When to use

Use this reference when generating, reviewing or operating a Service Architect project.

Behavior

  • Each lowercased whitespace-free Service.name becomes a deployable service directory.
  • Each Module.name becomes a module directory whose contents depend on references from public types, connectors and public functions.
  • A module referenced by an HTTP connector receives OpenAPI contracts; a module referenced by a gRPC connector receives protobuf contracts.
  • A module referenced by public types receives shared type and serde code.
  • graph stores the generated project topology snapshot.
  • scripts contains merge, Kubernetes, dependency-cache and Temporal orchestration.
  • kubernetes contains project-level chart values and local cluster configuration.
  • Each service owns its own graph snapshot, configuration, docs, dashboards and Helm chart.

Generated root directories

Common directories and files emitted for the canonical graph.

PathOwnershipDescription
<normalize(Service.name)>/Mixed

Independent service project with generated runtime wiring and preserved business functions.

<Module.name>/Generated + extension

User-named module. It may contain shared types, public functions, OpenAPI schemas, protobuf schemas or any combination selected by graph references.

<Module.name>/openapi/Generated schema source

Present when an HTTP connector references this Module through DataConnector.module.

<Module.name>/proto/Generated schema source

Present when a gRPC connector references this Module through DataConnector.module.

graph/<normalize(Project.name)>.generated.yamlGenerated

Full project graph snapshot used for inspection and traceability.

scripts/*.generated.*Generated

Workspace automation for merge, Kubernetes, cache and Temporal.

kubernetes/Generated

Local k3s, registry and infrastructure values.

docker-compose.ymlOverwrite list

Canonical local runtime topology.

docker-compose.*.generated.ymlGenerated

Specialized runtime, build, integration or dependency-cache topology.

dependency-cache/Generated

Nexus and Git mirror configuration and documentation.

spec/Preserved

Business tasks, implementation guidance and progress material.

.servicegen/Tool state

Merge logs and generated migration checklists.

Workspace tree template

<normalize(Project.name)>/
  Makefile + make.generated.mk
  graph/<normalize(Project.name)>.generated.yaml
  docker-compose.yml
  scripts/ + kubernetes/ + dependency-cache/
  <normalize(Service A.name)>/
  <normalize(Service B.name)>/
  <Module A.name>/
  <Module B.name>/