Skip to content

feat: provenance-drift check + re-pin for project→assistant refer-back #44

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Jammy2211 merged 1 commit into from
Jul 10, 2026
Merged

feat: provenance-drift check + re-pin for project→assistant refer-back #44

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions skills/start-new-project.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -102,6 +102,9 @@ Resolve the assistant clone, in order: `$AUTOLENS_ASSISTANT` → sibling `../aut
→ else clone `https://github.com/PyAutoLabs/autolens_assistant` into `sources/autolens_assistant/`
(gitignored). Read its `AGENTS.md` and follow its constitution (safety invariants, conventions,
modes); use its `skills/` and `wiki/` as the how-to and reference.
After resolving, compare the clone's commit to `project.yaml`'s `assistant_ref.commit`; if they
differ, mention the provenance drift and offer to re-pin — never block on it and never check
out the pinned commit.

## This project
- Context / decisions / results: `wiki/project/` (dated journal + `profile.md`).
Expand Down Expand Up @@ -197,6 +200,8 @@ on two things only — **no transcript/hash machinery**:
2. **Dated journal** → `wiki/project/YYYY-MM-DD-<slug>.md` (use the existing `_template.md`
shape: Context / What I did / Outcome), each entry referencing its `run_id`. This is the
same `wiki/project/` mechanism the assistant already uses — do not invent a parallel log.
An accepted `assistant_ref` re-pin (from the provenance-drift check in "Locating the
assistant from a project" below) is one line in the day's entry, not a new log.

---

Expand Down Expand Up @@ -249,6 +254,15 @@ the gitignored `sources/autolens_assistant/` — then read `skills/` and `wiki/`
mirrors the source-of-truth `sources/` clone-on-demand pattern in `AGENTS.md`; the project
depends on no vendored copy of the assistant.

**Provenance-drift check (non-blocking).** After resolving, compare the clone's commit
(`git -C <resolved> rev-parse HEAD`) to `project.yaml`'s `assistant_ref.commit`. If they
differ, tell the user once per session — both commits, and what the drift means (the toolchain
moved since the project was pinned; a provenance note, not a correctness problem) — and offer
to **re-pin**: update `assistant_ref.commit` to the resolved HEAD and note the re-pin in the
day's `wiki/project/` journal entry. Never hard-block on drift and never check the clone out
to the pinned commit — day-to-day operation always uses the resolved current clone, and the
per-run manifest's `assistant.commit` remains the record of what was actually used.

## Example projects (registry)

Real science projects built with this skill — clone-and-adapt one as the Create scaffold source
Expand Down
Loading