Triggering the Pipeline
The production pipeline is activated through commands — issued via the CLI, the web IDE's interface, or the REST API. Each command type corresponds to a distinct pipeline workflow, optimised for the specific task at hand.
Generation
The generate command is the primary entry point for creating new packages. It accepts a natural language description, a specification file, or a combination of both. The pipeline processes the input through the full eight-stage sequence: specification refinement, agent swarm consensus, security audit, optimisation, compilation, and distribution.
For complex projects, a specification file provides more control than a single-line description. The file format supports structured sections for functional requirements, access control rules, economic parameters, and deployment preferences.
Composition
The compose command combines multiple existing packages into a unified application. The composition engine resolves dependencies, detects interface conflicts, and produces a merged deployment configuration. Packages can be referenced by their registry identifier or by a local file path.
The composition engine performs a compatibility analysis before merging. If two packages define conflicting storage slots, use incompatible compiler versions, or implement overlapping interface methods, the engine reports the conflicts with suggested resolution paths.
Translation
The translate command converts an existing contract from one blockchain language to another. The input can be a source file, a deployed contract address (from which the platform retrieves the verified source), or a package generated by a previous pipeline run.
Translation produces a full package for each target language, including the translated contract source, a test suite that validates semantic equivalence with the original, and deployment configuration for the specified target chain.
Deployment
The deploy command takes a generated package and deploys it to the specified chain. The platform handles wallet integration, gas estimation, transaction signing, and deployment verification. Post-deployment, the command outputs the contract address, the transaction hash, and a link to the block explorer.
Deployment to mainnet is a permanent action. The platform prompts for explicit confirmation and displays a deployment summary — including estimated gas cost and the security audit status — before executing.