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-11-02T13:14:33Z

Codebase baseline

Source	Branch	Reviewed commit	Commit date	Working tree at capture
CIEL Lab v2	main	ce2c349	2026-11-02T01:00:43-03:00	Clean
CIEL scripts	main	2a42682	2026-10-24T09:24:45-03:00	Clean
OCL skills	main	24c04d0	2026-08-21T15:29:47-03:00	Clean

Full commit identifiers

CIEL Lab v2: ce2c34969ab590bfaa7708f3e6c27d9a46010f41
CIEL scripts: 2a4268245419ebbeebf12357cd8fbc6db45aea80
OCL skills: 24c04d07a0675972d6fbe84d9a9cf83a121622ee

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:

• CIEL Lab changes since the baseline
• CIEL scripts changes since the baseline
• OCL skills changes since the baseline

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-11-02.
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-11-02
Wiki issue 2609	2026-08-26
OCL skills guide issue 2680	2026-08-24