Modes describe how the initialization procedure behaves when applied to a target. The six-stage sequence — Inspect, Determine, Create, Configure, Validate, Report — remains the same across all modes, but the mode governs what the procedure is permitted to do: whether it mutates the target, creates artifacts, and how it handles an already-initialized state. A template may support one or more modes, and may define additional modes when the target category warrants it.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/bitwikiorg/init.md/llms.txt
Use this file to discover all available pages before exploring further.
Active
Inspect the target and perform applicable initialization work. Active mode is the standard initialization mode. The procedure runs the full six-stage sequence, creates artifacts, applies configuration, validates the result, and produces a final report. Use active mode when the target is new, incomplete, or not yet operational and you are ready to apply changes. Active mode is appropriate when:- the target is being initialized for the first time
- the target exists but has never been properly set up
- you have already reviewed a dry-run report and are ready to proceed
- the target is a development or non-production environment where changes are expected
Dry Run
Inspect the target, determine requirements, and report proposed work without changing the target. Dry-run mode performs the INSPECT and DETERMINE stages fully, then produces a report describing exactly what Active mode would do — which artifacts would be created, which configuration would be applied, which validation steps would run — without actually making any of those changes. The target is left completely unmodified. Dry-run mode is appropriate when:- the target is shared, sensitive, or production-adjacent
- you want to review the initialization plan before committing
- the procedure is being evaluated for a new target type
- a stakeholder needs to approve the proposed changes before they are applied
DRY_RUN_COMPLETE. See Result States for details.
Repair
Inspect an existing target, identify missing or invalid initialization elements, and correct what applies. Repair mode is designed for targets that were previously initialized but have since degraded: files were deleted, configuration drifted, dependencies went out of sync, or instructions became inconsistent. The procedure inspects the existing state, identifies which initialization elements are missing or broken, and corrects only those elements without disturbing what is already valid. Repair mode is appropriate when:- an initialized target has stopped working correctly
- some but not all initialization artifacts are present
- configuration files exist but contain errors or stale references
- dependencies have fallen out of sync with their manifests
- the target was partially initialized and needs the remaining work completed
Reinitialize
Re-evaluate an already initialized target after substantial changes to its purpose, environment, dependencies, ownership, or operating model. Reinitialize mode treats a fully initialized target as if it needs to be assessed from scratch — but with full awareness that prior initialization work exists. The procedure re-runs the full six-stage sequence, evaluates whether existing artifacts are still valid, and produces new or updated initialization work to reflect the changed state of the target. Reinitialize mode is appropriate when:- the target’s purpose or scope has changed substantially
- the target has moved to a new environment (e.g., different server, cloud provider, or runtime)
- ownership or operating team has changed and existing instructions no longer apply
- major dependency or platform upgrades have changed what the target requires
- the existing initialization is so far out of date that repair would be more disruptive than reinitializing
Mode comparison
| Mode | Mutates target | Creates artifacts | Validates result | Produces report |
|---|---|---|---|---|
| Active | Yes | Yes | Yes | Yes |
| Dry Run | No | No | No (proposed only) | Yes |
| Repair | Yes (targeted) | Partial | Yes | Yes |
| Reinitialize | Yes | Yes (replaces or updates) | Yes | Yes |