guide-board is a certification and compliance preparation framework. It turns standards, conformance, regulatory, and repository-quality claims into structured evidence that can be reviewed, repeated, compared, and used during assessments.

The root project owns the framework contracts. Domain-specific work lives in extensions.

Local Baseline

The first core is intentionally dependency-light. From a clean checkout:

PYTHONPATH=src python3 -m guide_board extensions list
PYTHONPATH=src python3 -m guide_board extensions validate
PYTHONPATH=src python3 -m guide_board profile validate-target profiles/targets/sample-repository.json
PYTHONPATH=src python3 -m guide_board profile validate-assessment profiles/assessments/sample-noop.json
PYTHONPATH=src python3 -m guide_board plan \
  --target profiles/targets/sample-repository.json \
  --assessment profiles/assessments/sample-noop.json
PYTHONPATH=src python3 -m guide_board run \
  --target profiles/targets/sample-repository.json \
  --assessment profiles/assessments/sample-noop.json
PYTHONPATH=src python3 -m unittest discover -s tests

The sample-noop extension exercises the guide-board contracts without invoking an external harness. open-cmis-tck is the first real seed extension.

See: