# Configuration Management

> Use when you must manage DO-178C software configuration: establish configuration baselines, record and process problem reports, control changes to baselined data, and maintain archive and recovery procedures for software lifecycle data. Determine when independent approval of changes applies, which is required at levels A and B, and gate software release on closed problem reports, a current baseline, and an archive capability. Trigger: DO-178C configuration management, configuration baselines, problem reports, change control, change control board, archive and recovery, software release.

- Skill: `ashfordeou/configuration-management-2` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add ashfordeou/configuration-management-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ashfordeou/configuration-management-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: Apache-2.0
- Author: ashfordeOU (https://skillmd.com/u/ashfordeou)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/ashfordeou/configuration-management-2

---


# DO-178C Configuration Management (avionics/do178c/configuration-management)

Use when the task is DO-178C configuration-management work: keeping the
software lifecycle data controlled, traceable, and recoverable.

## Domain quick reference

- Configuration management (DO-178C): baselines, problem reporting,
  change control, and archive/recovery of software lifecycle data.
- Baselines freeze a consistent set of lifecycle data; changes to
  baselined data are reviewed at every software level.
- Problem reports record defects and discrepancies; release requires
  them to be analyzed and closed.
- Levels A and B require independent approval of changes.
- Archive and recovery preserve the ability to reconstruct released
  software and its data.

## Workflow

1. Establish configuration baselines for software lifecycle data.
2. Record problem reports; analyze and close them.
3. Control changes to baselined data; levels A/B add independent
   approval.
4. Maintain archive and recovery procedures.
5. Gate release: current baseline, closed problem reports, archive
   capability in place.

## Pitfalls

- Releasing with open problem reports.
- Changes applied without review of baselined data.
- No archive/recovery path for released software.
- Missing independence for change approval at level A or B.

## Behavior contract (gate 3)

The baseline, change-control, and release-gate logic is exercised by the
gate 3 contract test: scripts/test_cm.py against scripts/cm_logic.py
(stdlib unittest, offline). Run: python3 scripts/test_cm.py

## Compliance

- Standards referenced, not reproduced: DO-178C / ARP4754A / ARP4761A text
  is proprietary (RTCA/SAE); summary-only per standards-map.yaml and brief 06.
- compliance: STANDARDS-REF, gated: false.