ModuLix overview

ModuLix is the Automation Content product in the Lightning IT portfolio. Its conceptual verb is Build: it organizes reusable automation content so teams can review, version, test, and compose infrastructure changes.

ModuLix is a peer of IO, Wunderbox, and Atlas. The products can interact, but none is a child of another.

What belongs to ModuLix

The public ModuLix model separates four concerns:

1. Collections package related automation content under a stable namespace.
2. Roles implement a bounded, reusable automation responsibility.
3. Building blocks combine content, inputs, execution context, and evidence.
4. Blueprints describe a reviewed composition without turning an environment inventory or secret into public documentation.

This documentation explains those concepts and the safe workflow around them. Code-specific variables, compatibility statements, and contributor commands remain with the public component repository and release that owns them.

Public component surface

The public source surface currently includes:

• ModuLix automation for reusable automation entry points;
• ModuLix launcher for its published launcher implementation and repository-specific instructions;
• sanitized inventory examples that demonstrate structure without representing a real environment; and
• the public Lightning IT Ansible collections listed in Collections.

Repository presence proves that source is public; it does not prove that a particular version is deployed or supported in an environment. Use the selected release's own compatibility and test evidence for that decision.

Choose a path

• New to the model: start with Concepts and Building blocks.
• Selecting content: review Collections and Roles.
• Preparing a controlled evaluation: follow Installation, then Usage.
• Contributing: use Development and Testing.
• Reviewing risk: read Security and Lifecycle.

Publication boundary

Public examples use documentation-only names and addresses. Real inventories, credentials, customer procedures, recovery material, deployment evidence, and environment-specific troubleshooting records do not belong on this site. The public documentation boundary applies even when a value looks harmless in isolation.