Foundations
The containers and platform resources Nenjo runs inside — projects, packages, models and tools, and scopes.
Foundations are the containers and platform resources everything else runs inside. They are not composed into a prompt like primitives, and they do not orchestrate work like workflows — they scope it, package it, power it, and govern it.
Think of foundations as the runtime environment for everything else: where work is scoped, how behavior is packaged and shipped, which models and tools agents can call, and which platform capabilities they are allowed to touch.
When to reach for each foundation
| Situation | Start here |
|---|---|
| You need to isolate memory, context, and runtime for a product, client, or initiative | Projects |
| You want to version, share, or install a bundle of agents, knowledge, and workflows | Packages |
| You are wiring LLMs, MCP servers, or script-backed tools into agents | Models & Tools |
| You need least-privilege access to dashboard MCP tools for a resource family | Scopes |
How foundations relate to the rest of Nenjo
- Projects define the boundary for a unit of work — tasks, memory, and runtime context live here.
- Packages move versioned bundles of primitives and workflows between projects, environments, and machines.
- Models & Tools are configured once, then assigned where agents need them.
- Scopes gate which platform MCP tools an agent may call inside a project.
Primitives answer what an agent knows and does. Workflows answer how multiple steps run together. Foundations answer where that work runs, how it ships, what powers it, and what it is allowed to touch.
| Foundation | Job |
|---|---|
| Projects | Scope the runtime, memory, and context for a unit of work |
| Packages | Versioned containers that bundle primitives and workflows, installed via nenpm |
| Models & Tools | The LLMs (and external/script tools) agents act through |
| Scopes | Least-privilege permissions that grant agents platform MCP tools |
Typical setup path
Most workspaces grow in this order:
- Create a project for the initiative you are building.
- Install or author packages that carry agents, knowledge, and routines.
- Assign models and tools where agents need provider or MCP access.
- Tighten scopes so each agent only receives the platform tools it needs.
If you are onboarding a new workspace, pair this section with Onboarding for trusted devices and worker setup, and Installation for getting nenjo run onto your infrastructure.