Skip to content

Source baseline

This page records the exact source state used for the current documentation review. It prevents the wiki from silently claiming coverage of code that was added after the review.

Captured: 2026-07-25T12:51:02Z

Codebase baseline

Source Branch Reviewed commit Commit date Working tree at capture
CIEL Lab v2 feature/release-pipeline-notifications 9341a28 2026-07-20T15:04:42-03:00 Dirty — 28 changed paths, including 0 untracked
CIEL scripts main 86e95b3 2026-07-19T10:54:51-03:00 Dirty — 2 changed paths, including 1 untracked

Full commit identifiers

CIEL Lab v2: 9341a28202cddaf647ddff9236177c863abae55f
CIEL scripts: 86e95b35f7cd0fd21632173160bb4e90272be3d8

The initial baseline included local changes

Both working copies contained local changes when the first documentation review was captured. The versioned source-baseline.yml records the dirty state, changed-path counts, tracked-diff fingerprints, and the untracked content fingerprint where applicable. A commit identifier alone does not represent those local changes.

Review changes since this baseline

Use the comparison links for a quick remote review:

For local working copies, run:

.venv/bin/python scripts/source_baseline.py report

The report shows:

  • commits after the stored baseline;
  • the file-level diff summary;
  • the current branch and HEAD;
  • uncommitted or untracked paths that are not represented by a commit.

Incremental documentation cycle

  1. Run the baseline report.
  2. Review only the commits and changed paths after the stored commit.
  3. Inspect new Slack material after 2026-07-24.
  4. Update affected feature, architecture, troubleshooting, and script pages.
  5. Build and review the wiki.
  6. Move the baseline only after the documentation review is complete.

To record clean reviewed working copies:

.venv/bin/python scripts/source_baseline.py capture --confirm-reviewed

The capture command refuses dirty codebases by default. If local uncommitted changes were intentionally part of the review, make that decision explicit:

.venv/bin/python scripts/source_baseline.py capture \
  --confirm-reviewed \
  --allow-dirty

Review the resulting source-baseline.yml diff before committing it.

Evidence dates

The code hashes describe code coverage. Slack and issue evidence have their own review-through dates in source-baseline.yml; they should be advanced only after the corresponding new material has been reviewed.

Evidence source Reviewed through
Private CIEL Lab Slack conversation 2026-07-24
Wiki issue 2609 2026-07-24