Overview
At the top level, a workspace can contain:
- An agent-configuration area for local instructions, skills, and specialist definitions.
- An active area for generated outputs and current work.
- A hidden temporary area for short-lived intermediate files.
- An environment file for credentials and configuration values.
- A concise local instruction file describing the workspace.
- Separate project, client, or life-domain folders when the workspace covers multiple areas.
The root should remain small. Random scripts, images, data files, reports, and temporary artifacts should not accumulate beside the core configuration. Instead, each skill or workflow should specify the exact directory and naming convention for its outputs. This removes the need for repeated agentic searches and makes cleanup predictable.
Hierarchies should reflect the real boundary of the work. A business workspace can contain one folder per client, each with its own environment values, project instructions, and project-specific skills. A personal workspace can use domains such as health, citizenship, or learning. The purpose is not to imitate an organization chart. It is to keep context and credentials aligned with the task that needs them.
Periodic cleanup is part of the system. The agent can inspect loose files in the active area, delete incomplete or temporary artifacts, and move durable outputs into meaningful subfolders. This preserves a logical structure for both the human and future agent sessions.
Portability is another organizational concern. Heavy dependence on one vendor-specific instruction filename, skill layout, or interface creates a single point of failure. The underlying project knowledge can be maintained in a form that is easy to duplicate or synchronize into the instruction format expected by another harness.