Architecture

Neksus JobSpec is structured as a reusable local-first core with thin interfaces.

Runtime layers

1. CLI layer (neksus-jobspec)
2. argument parsing
3. human/json output formatting

4. thin delegation to app use cases

5. Core app/use-case layer (neksus_jobspec.app)

6. orchestrates validate/render/export/feed/project flows

7. shared by CLI and MCP

8. Domain layer (neksus_jobspec.jobspec)

9. parser, Pydantic models, validation, rendering, exports, lint

10. Project layer (neksus_jobspec.project)

11. project discovery, config, checks, initialization

12. MCP adapter layer (neksus_jobspec_mcp)

13. local stdio tools mapped to the same core use cases

Pipeline

YAML -> parser/loader -> Pydantic JobSpec model -> app use cases -> render/export/feed/MCP/CLI

Principle

Keep CLI and MCP thin; place behavior and orchestration in core services.