Code Workspace
The Code Workspace is FORGE’s working filesystem and execution context for one software job.
It gives the build a coherent project tree instead of treating each generated file as an isolated code block.
Workspace contents
A workspace can contain:
- source files
- configuration
- package/dependency manifests
- generated assets
- validation scripts/configuration
- repository snapshot material
- intermediate repair changes
Workspace vs artifact
The workspace is where work happens. An artifact is the durable packaged output that survives the build according to retention policy.
Do not assume every temporary workspace file becomes part of the final artifact.
Existing repositories
For repository-backed work, the workspace should represent a defined source revision before modifications begin. This allows the build and repair engine to reason about a consistent project state.
File operations
FORGE can create, modify, rename, or remove files only within the permissions and tooling exposed by the build environment.
A tool being capable of file deletion does not mean every build should receive unrestricted destructive access.
Workspace limits
Limits can include:
- maximum file count
- maximum total size
- per-file size
- execution duration
- allowed commands/tools
- concurrent build count
The active plan and Control Center configuration are the source of truth for effective values.
Workspace cleanup
Temporary workspace storage can be cleaned after completion or failure according to platform policy. Durable outputs should be represented as artifacts or project resources rather than depending on an internal temporary path.
Never build an external integration around undocumented internal workspace paths. Use Starfire file/artifact resources and supported downloads instead.
