Dedupe the dataverse inputs and label them as the spec's compiled form - #6
Merged
Conversation
…ed form - Delete dataverse/eppc-sessions-seed.yaml, a stale duplicate of dataverse/eppc-sessions.yaml (the canonical, commented seed input), so the seed skill can't be fed the wrong file. - AGENTS.md + specs/dataverse-schema.md: state that dataverse/*.yaml is the executable form compiled from the specs, the specs are the source of truth, and the YAML is regenerated (never diverged) when a spec changes. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
This PR removes a stale duplicate Dataverse seed input and documents the intended relationship between prose specs and the dataverse/*.yaml “executable” inputs that the Dataverse skills run, reducing drift/ambiguity risk for live scaffolding/seeding.
Changes:
- Deleted
dataverse/eppc-sessions-seed.yamlto avoid having multiple seed inputs for the same table. - Updated
specs/dataverse-schema.mdto explicitly link todataverse/eppc-schema.yamlas the compiled/executable form fordataverse-scaffold-tables. - Updated
AGENTS.mdto clarify thatdataverse/*.yamlfiles are compiled/executable forms derived from the specs and should be regenerated when specs change.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| specs/dataverse-schema.md | Adds an explicit link and guidance tying the schema spec to its compiled dataverse/eppc-schema.yaml input for the scaffold skill. |
| dataverse/eppc-sessions-seed.yaml | Removes a stale duplicate seed file to prevent accidental use of the wrong input. |
| AGENTS.md | Documents that dataverse/eppc-schema.yaml / dataverse/eppc-sessions.yaml are the executable skill inputs derived from specs and must not drift. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Acts on the "do we even need the
dataverse/folder?" question. We keep it (the skills need a precise machine contract the prose spec deliberately doesn't match, and a pre-verified input de-risks Beat 2, the earliest/most fragile beat), but we remove the genuine smell: unlabelled duplication with a stale copy.Changes
dataverse/eppc-sessions-seed.yaml— a stale duplicate ofdataverse/eppc-sessions.yaml(the canonical, header-commented seed input). One seed file means the create-records skill can't be fed the wrong one.AGENTS.mdandspecs/dataverse-schema.md:dataverse/*.yamlis the executable form compiled from the specs; the specs are the source of truth; regenerate the YAML when a spec changes, never let it diverge.Why keep the folder rather than generate live
The schema is frozen for the demo, so the drift risk this guards against is near-zero in practice, while having the agent translate the whole schema + 20-row seed live would put a cheap model's mistranslation right on Beat 2. Pre-verified input wins for a live demo. On stage you can still say "this is just the spec compiled into what the skill runs."
Independent of PRs #4 and #5 (no overlapping files).
🤖 Generated with Claude Code