Purpose

The guidelines and principles for which Zarf is both developed as well as future changes should stem from a set of design principles such that new requests or development can be measured for adherence with the design principles.

This also mitigates new feature suggestions that may have unforeseen implications from being seen as subjectively reviewed (for what does or does not get implemented) and instead may provide more objectives measures for reference and review.

Following inspirations from sources such as:

• aeron

Potential Targets

• Airgap native: Ensuring all functionality in zarf supports an airgapped ecosystem by default. Configurations can be exposed which rely on external/host dependencies - but no new functionality should ever prohibit zarf from being able to perform the lifecycle of actions without said dependency.
• Tooling Inclusion: Selection of tools which get vendored into Zarf and the justification