The pipeline spec system describes, validates, and compiles configuration states along pipelines and phases.

What it is

  • the pipeline-config-spec-php library
  • a rule and execution system for YAML loading, manifest validation, and config compilation
  • the layer that makes phase and source logic explicit

What it is not

  • not the end product itself
  • not the public work docs
  • not only a file location for defaults

Why

  • app and deployment paths need verifiable config boundaries
  • the project should not hide pipeline and phase logic implicitly in code

Structure

  • YAML loader
  • manifest logic
  • source and policy checks
  • compiler for config snapshots

Manifest metadata

  • meta.desc gives a short functional description of one parameter.
  • meta.example shows an example value.
  • meta.notes carries short local hints about that parameter.
  • Validation-relevant parameter dependencies should not remain free text in meta.notes; they belong in a dedicated rule path such as J01-37.

Roles

  • library and app developers
  • operators of build, runtime, and deploy paths

Interfaces

Current state and target picture

  • Current state:
    • config order and manifest basics are documented
  • Target picture:
    • project-wide clear and testable phase boundaries

Parent systems

Child systems

  • manifest model
  • source and compiler logic

Sources

  • pipeline-config-spec-php/README.de.md
  • lebenslauf-web-vorlage/docs/ENVIRONMENTS.md
  • CLI / Build
  • J01-105