Who it is for
Software maintainers preparing patches, builds, tests, and provenance for human review.
Proposed roadmap application
Thirteenfold Forge
Controlled software analysis, patch preparation, builds, tests, packaging, dependency inventories, and provenance.
Proposed roadmap application; name and implementation remain under review.
Why it is planned
A practical role in the family.
Example use
A repository needs a proposed patch and test evidence, but merge, signing, deployment, and release must remain separate.
Intended benefit
Could produce more reviewable software candidates with clearer build, dependency, and test provenance.
Intended workflow
How the work would flow.
This describes the planned experience. It does not establish that these capabilities are available.
Authorize the exact workspace, task, dependencies, and permitted operations.
Prepare the patch and run bounded builds, tests, packaging, and software bill of materials (SBOM) generation.
Present an unsigned candidate and evidence packet to the human or separate release system.
Scope and relationships
Clear ownership of the work.
Data and authority boundaries
Would use explicitly selected workspaces, build environments, and dependency metadata; it would not hold merge, signing, deployment, or release credentials.
How it fits with the family
Forge would manage the source-to-candidate software workflow; Compute would manage and evaluate local runtimes and computational workloads.
Explore Thirteenfold Compute