Adoption Phases
A practical path from drop-in outputs to deeper runtime integration — without disrupting existing SDLC, CI/CD, and compliance workflows. Teams can adopt per workload, per product, or per team.
The two operating modes
Export Mode
Wantware generates traditional source code or compiled artifacts that pass through existing CI/CD pipelines, scanning tools, and deployment frameworks unchanged. Nothing in your tooling has to change; Essence becomes a generator whose output your existing systems already know how to handle.
Essence Runtime Mode
Execution occurs dynamically within Essence. Fixed builds may still be generated when required for compliance scanning, validation, or certification workflows — but the primary execution path uses governed runtime rather than static binaries.
The adoption phases
Phase 1 · Export Mode (Fast Path)
Wantware generates source code or compiled artifacts that flow through your existing pipeline.
What Plugs In Directly
- Version control: Git, GitHub, GitLab as-is
- Build: Jenkins, GitHub Actions, GitLab CI, Azure DevOps
- Security scanning: SAST, DAST, dependency scanners, license checks
- Artifacts: Nexus, Artifactory, container registries
- Deploy: your current targets — VMs, containers, cloud
Teams that want immediate compatibility and governance with minimal change.
Phase 2 · Hybrid (Export + Controlled Runtime)
Keep standard builds for compliance where needed, while introducing controlled runtime behaviors for specific workloads.
What Changes
- Two outputs: fixed scan-ready builds plus runtime-optimized execution where appropriate
- Policy gates: choose which workloads are fixed vs adaptive
- Validation: artifacts and proofs generated per pilot workload
- Observability: clearer who / what / when / why audit trails
- Team workflow: collaborative iterations without breaking existing repo discipline
Regulated teams that need a clean compliance path while proving runtime value.
Phase 3 · Essence Runtime Mode (Deep Integration)
Execution occurs dynamically within Essence, with controls for trust, traceability, and operational governance.
What Governed Runtime Enables
- Runtime governance: policies, access controls, and declared-purpose enforcement
- Traceability: lineage and audit across versions, forks, and owners
- Security posture: trust plus validation enforced continuously, not only at build time
- Performance: adaptive optimization per device and execution conditions
- Interoperability: still supports exporting fixed builds when required
Organizations pursuing maximum operational leverage and runtime assurance.
These phases can be adopted per team, per product, or per workload. You don't need a big-bang migration. Compliance workflows can stay in Phase 1 while exploratory pipelines move to Phase 3 — all backed by the same Essence source base.
Adoption is a continuum, not a cliff. Start where your risk tolerance and compliance constraints allow, prove value on bounded workloads, and expand the runtime footprint as operational readiness grows.