Skip to content

refactor(agents)!: consolidate the Data Science workstream into skill-primary coach jobs - #2612

Open
Bill Berry (WilliamBerryiii) wants to merge 39 commits into
mainfrom
2610-ds-workstream-consolidation
Open

refactor(agents)!: consolidate the Data Science workstream into skill-primary coach jobs#2612
Bill Berry (WilliamBerryiii) wants to merge 39 commits into
mainfrom
2610-ds-workstream-consolidation

Conversation

@WilliamBerryiii

Copy link
Copy Markdown
Member

Pull Request

Description

Consolidates the Data Science workstream from an agent-primary surface into a skill-primary one governed by data-workstream-coach.

The five Data Science specialist agents delegated work that either belongs to a skill (durable, reusable conventions) or is already served by built-in VS Code Copilot tooling (notebook and dashboard scaffolding). Research confirmed the durable capability in those agents was authoring convention, not orchestration, so it is absorbed into skills and the retired agent surfaces are dropped rather than rehomed.

Retired agents

Removes five specialist agents under .github/agents/data-science/:

  • eval-dataset-creator
  • gen-data-spec
  • gen-jupyter-notebook
  • gen-streamlit-dashboard
  • test-streamlit-dashboard

New skills

  • ds-analysis-authoring — EDA notebook sequencing and analytical dashboard authoring conventions, including a plot-selection table, axis-scale thresholds, cache_data versus cache_resource guidance, and interaction latency budgets.
  • ds-evaluation-design — evaluation dataset design for AI systems, including an interview and review protocol, metric selection, provenance requirements, and a dataset contract template. It sets a 30-pair floor and a category distribution with a per-category floor, and deliberately does not freeze an evaluator catalog.

Extended skills

  • ds-catalog gains dataset profile contract coverage.
  • ds-dataops gains persistence and versioning coverage.

Coach and registry

  • data-workstream-coach reduces its agents: frontmatter from six entries to one (Experiment Designer), and now states that coaching governs decision ownership rather than abstention from producing work.
  • The job registry replaces the analysis job target with ds-analysis-authoring, adds an evaluation job routed to ds-evaluation-design, and moves from five-skill to seven-skill boundaries.

Catalog and evals

  • marketplace.json updates the data-science and hve-core-all packages to the new membership, with matching component maturity across both packages.
  • Behavior conformance stimuli, expectations, and surface signatures for the retired agents are removed; sixteen skill stimuli cover the new and extended surfaces.

Related Issue(s)

Closes #2610

Type of Change

Select all that apply:

Code & Documentation:

  • Bug fix (non-breaking change fixing an issue)
  • New feature (non-breaking change adding functionality)
  • Breaking change (fix or feature causing existing functionality to change)
  • Documentation update

Infrastructure & Configuration:

  • GitHub Actions workflow
  • Linting configuration (markdown, PowerShell, etc.)
  • Security configuration
  • DevContainer configuration
  • Dependency update

AI Artifacts:

  • Reviewed contribution with hve-builder and addressed all actionable findings
  • Copilot instructions (.github/instructions/*.instructions.md)
  • Copilot prompt (.github/prompts/*.prompt.md)
  • Copilot agent (.github/agents/*.agent.md)
  • Copilot skill (.github/skills/*/SKILL.md)
  • Copilot hook (.github/hooks/*/*.json)
  • Eval spec added/updated for changed AI artifacts (evals/)

Other:

  • Script/automation (.ps1, .sh, .py)
  • Other: marketplace package membership and component maturity

Sample Prompts (for AI Artifact Contributions)

User Request:

"Help me build an evaluation dataset for our retrieval-augmented support assistant."

Execution Flow:

  1. data-workstream-coach matches the request to the evaluation job in the job registry.
  2. The registry routes the job to ds-evaluation-design.
  3. The skill runs its interview protocol to establish the system boundary, failure modes, and success criteria.
  4. It applies the category distribution and per-category floor to size the dataset, then selects metrics against the declared failure modes.
  5. It emits the dataset contract and supporting documents, recording provenance for every pair.

Output Artifacts:

An evaluation dataset contract from templates/evaluation-dataset-contract.md, covering system boundary, category distribution, metric selection with rationale, provenance, and review disposition.

Success Indicators:

The contract meets the 30-pair floor, every category satisfies its floor, each selected metric ties to a declared failure mode, and every pair carries provenance.

Testing

Local validation on the merged branch:

  • npm run lint:marketplace — pass
  • npm run lint:plugin-output — pass
  • npm run validate:skills — pass
  • npm run lint:frontmatter — pass
  • npm run lint:md — pass
  • npm run lint:yaml — pass
  • npm run lint:json — pass
  • npm run lint:asset-docs — pass

Diff hygiene:

  • No date-only Markdown changes at any level. Staged (125 modified Markdown files), unstaged, and the full PR diff against main (35 modified Markdown files) each report zero date-only diffs.
  • docs/reference/ pages are regenerated through npm run docs:generate; generated regions are not hand-edited.

CI-owned lanes are deferred to this PR's checks rather than run locally: the eval lint lanes (vally, schema, text, safety), stimulus presence, changed-artifact execution, and content moderation.

Checklist

Required Checks

  • Documentation is updated (if applicable)
  • Files follow existing naming conventions
  • Changes are backwards compatible (if applicable) (No: five Data Science agents are intentionally removed)
  • Tests added for new functionality (if applicable)

AI Artifact Contributions

  • Used hve-builder review mode to review contribution
  • Addressed all actionable findings from the hve-builder review
  • Verified contribution follows common standards and type-specific requirements

Required Local Checks

The following local-safe validation commands must pass before merging:

  • Local validation aggregate: npm run validate:local (Targeted checks were run individually; the aggregate was not accepted as final evidence)
  • Documentation validation (if docs changed): npm run validate:docs (Docusaurus installation not current in this working tree)
  • Spell checking: npm run spell-check (Introduced findings were fixed; the repository-wide run has pre-existing failures from other in-flight work)
  • Link validation: npm run lint:md-links (Not accepted as final aggregate evidence)

Security Considerations

  • This PR does not contain any sensitive or NDA information
  • Any new dependencies have been reviewed for security issues (N/A: no dependency added)
  • Security-related scripts follow the principle of least privilege

Additional Notes

…ounded in the CSE playbook

- author two MIT-grounded reference packs with provenance and derivation labels
- migrate MVE methodology from the experiment-designer instruction into the skill
- add permissive-license and mixed-content classes to the licensing posture
- declare both packs MIT AND CC-BY-4.0 and correct reproduction claims
- register in data-science and experimental collections with 9 eval stimuli

📚 - Generated by Copilot
- normalize CRLF to LF before drift, ms.date, and orphan-scaffold comparisons
- stop false drift that rewrote every reference page on a CRLF checkout
- restore orphaned-scaffold removal that a CRLF template tail suppressed
- add Test-DocContentEqual and CRLF regression tests

🔧 - Generated by Copilot
- add EDA section sequence, plot selection, and scale thresholds
- add dashboard components, caching rules, and validation budgets
- add evaluation interview, difficulty balance, and dataset contract
- record external evaluator vocabulary as cite-only provenance

📊 - Generated by Copilot
- add DS_CATALOG_V1 entity, relationship, and profile contracts
- add evidence-led feasibility study and interchange traceability
- split ML reproducibility and readiness from experiment framing
- extend ds-dataops with derived-dataset persistence conventions

📚 - Generated by Copilot
…tion

- relocate experiment-design out of the data-science collection
- add an experiment-readiness reference for scoping and vetting
- add a feasibility-to-PRD handoff to requirements-author

🧪 - Generated by Copilot
- remove gen-data-spec, gen-jupyter-notebook, and gen-streamlit-dashboard
- remove test-streamlit-dashboard and eval-dataset-creator
- route analysis and a new evaluation job to owning skills
- expand the coach skill-boundary table from five to seven

♻️ - Generated by Copilot
…rtions

- remove five per-agent stimulus, expectation, and signature files
- assert seven-skill boundaries and skill-primary job routing
- add behavior-conformance stimuli for both new skills
- regenerate agent inventory and behavior spec from source

✅ - Generated by Copilot
- render a declared catalog model as an entity relationship diagram
- validate catalog input and reject unsafe rendering payloads
- commit a uv-managed dependency set with tests

📐 - Generated by Copilot
- update the canonical deck reference and coaching state handling
- align the dt-coach agent and canonical-deck prompt

🎨 - Generated by Copilot
- harden the adr-author sensitive-content scanner and its tests
- update licensing-posture and disclaimer-language guidance

🔒 - Generated by Copilot
- remove five retired specialist agents from the themed manifest
- register ds-analysis-authoring and ds-evaluation-design
- regenerate the canonical manifest and collection regions

📦 - Generated by Copilot
…ents

- rewrite the data-scientist role and three lifecycle guides
- drop retired agents from the agent catalog and installer sample
- regenerate reference pages and author the new skill page tails

📝 - Generated by Copilot
- regenerate plugin trees for the new and relocated skills
- drop per-agent outputs for the retired specialists
- record third-party attribution for the new reference packs

🔧 - Generated by Copilot
…nsolidation

# Conflicts:
#	.github/plugin/marketplace.json
#	.github/skills/installer/hve-core-installer/SKILL.md
#	collections/data-science.collection.md
#	collections/data-science.collection.yml
#	collections/experimental.collection.md
#	collections/experimental.collection.yml
#	collections/hve-core-all.collection.md
#	collections/hve-core-all.collection.yml
#	collections/project-planning.collection.md
#	docs/reference/README.md
#	docs/reference/instructions/README.md
#	docs/reference/skills/README.md
#	evals/behavior-conformance/skill-behavior.eval.yaml
#	plugins/data-science/.github/plugin/plugin.json
#	plugins/data-science/README.md
#	plugins/experimental/.github/plugin/plugin.json
#	plugins/experimental/README.md
#	plugins/hve-core-all/.github/plugin/plugin.json
#	plugins/hve-core-all/README.md
#	plugins/project-planning/README.md
#	scripts/tests/docs/Generate-AssetDocs.Tests.ps1
@github-actions

github-actions Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Scorecard details
PackageVersionScoreDetails
pip/atheris 3.1.0 🟢 6.1
Details
CheckScoreReason
Packaging⚠️ -1packaging workflow not detected
Maintained⚠️ 23 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
Token-Permissions🟢 10GitHub workflow tokens follow principle of least privilege
SAST⚠️ 0no SAST tool detected
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Binary-Artifacts🟢 10no binaries found in the repo
Code-Review🟢 7Found 23/30 approved changesets -- score normalized to 7
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Fuzzing🟢 10project is fuzzed
License🟢 10license file detected
Signed-Releases⚠️ -1no releases found
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Security-Policy🟢 10security policy file detected
Branch-Protection⚠️ 0branch protection not enabled on development/release branches
pip/attrs 26.1.0 UnknownUnknown
pip/colorama 0.4.6 UnknownUnknown
pip/coverage 7.15.3 UnknownUnknown
pip/iniconfig 2.3.0 UnknownUnknown
pip/jsonschema 4.26.0 UnknownUnknown
pip/jsonschema-specifications 2025.9.1 UnknownUnknown
pip/packaging 26.2 UnknownUnknown
pip/pluggy 1.6.0 UnknownUnknown
pip/pygments 2.20.0 UnknownUnknown
pip/pytest 9.1.1 UnknownUnknown
pip/pytest-cov 7.1.0 UnknownUnknown
pip/pyyaml 6.0.3 UnknownUnknown
pip/referencing 0.37.0 UnknownUnknown
pip/rpds-py 2026.6.3 UnknownUnknown
pip/ruff 0.16.1 UnknownUnknown
pip/tomli 2.4.1 UnknownUnknown
pip/typing-extensions 4.16.0 UnknownUnknown
pip/atheris 3.1.0 🟢 6.1
Details
CheckScoreReason
Packaging⚠️ -1packaging workflow not detected
Maintained⚠️ 23 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
Token-Permissions🟢 10GitHub workflow tokens follow principle of least privilege
SAST⚠️ 0no SAST tool detected
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Binary-Artifacts🟢 10no binaries found in the repo
Code-Review🟢 7Found 23/30 approved changesets -- score normalized to 7
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Fuzzing🟢 10project is fuzzed
License🟢 10license file detected
Signed-Releases⚠️ -1no releases found
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Security-Policy🟢 10security policy file detected
Branch-Protection⚠️ 0branch protection not enabled on development/release branches
pip/attrs 26.1.0 UnknownUnknown
pip/colorama 0.4.6 UnknownUnknown
pip/coverage 7.15.3 UnknownUnknown
pip/iniconfig 2.3.0 UnknownUnknown
pip/jsonschema 4.26.0 UnknownUnknown
pip/jsonschema-specifications 2025.9.1 UnknownUnknown
pip/packaging 26.2 UnknownUnknown
pip/pluggy 1.6.0 UnknownUnknown
pip/pygments 2.20.0 UnknownUnknown
pip/pytest 9.1.1 UnknownUnknown
pip/pytest-cov 7.1.0 UnknownUnknown
pip/pyyaml 6.0.3 UnknownUnknown
pip/referencing 0.37.0 UnknownUnknown
pip/rpds-py 2026.6.3 UnknownUnknown
pip/ruff 0.16.1 UnknownUnknown
pip/tomli 2.4.1 UnknownUnknown
pip/typing-extensions 4.16.0 UnknownUnknown
pip/pyyaml >= 6.0 UnknownUnknown
pip/atheris 3.1.0 🟢 6.1
Details
CheckScoreReason
Packaging⚠️ -1packaging workflow not detected
Maintained⚠️ 23 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
Token-Permissions🟢 10GitHub workflow tokens follow principle of least privilege
SAST⚠️ 0no SAST tool detected
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Binary-Artifacts🟢 10no binaries found in the repo
Code-Review🟢 7Found 23/30 approved changesets -- score normalized to 7
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Fuzzing🟢 10project is fuzzed
License🟢 10license file detected
Signed-Releases⚠️ -1no releases found
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Security-Policy🟢 10security policy file detected
Branch-Protection⚠️ 0branch protection not enabled on development/release branches
pip/colorama 0.4.6 UnknownUnknown
pip/coverage 7.15.3 UnknownUnknown
pip/iniconfig 2.3.0 UnknownUnknown
pip/packaging 26.2 UnknownUnknown
pip/pluggy 1.6.0 UnknownUnknown
pip/pygments 2.20.0 UnknownUnknown
pip/pytest 9.1.1 UnknownUnknown
pip/pytest-cov 7.1.0 UnknownUnknown
pip/pyyaml 6.0.3 UnknownUnknown
pip/ruff 0.16.1 UnknownUnknown
pip/tomli 2.4.1 UnknownUnknown

Scanned Files

  • .github/skills/data-science/ds-catalog/uv.lock
  • .github/skills/data-science/ds-feasibility/uv.lock
  • .github/skills/hve-core/architecture-diagrams/pyproject.toml
  • .github/skills/hve-core/architecture-diagrams/uv.lock

@codecov-commenter

Codecov Comments Bot (codecov-commenter) commented Aug 6, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 95.88183% with 46 lines in your changes missing coverage. Please review.
✅ Project coverage is 86.96%. Comparing base (7523b50) to head (301b3c5).

Files with missing lines Patch % Lines
...nce/ds-feasibility/scripts/validate_feasibility.py 93.31% 21 Missing ⚠️
...nning/adr-author/scripts/scan_sensitive_content.py 95.02% 12 Missing ⚠️
...rchitecture-diagrams/scripts/render_catalog_erd.py 97.05% 10 Missing ⚠️
...ata-science/ds-catalog/scripts/validate_catalog.py 98.64% 3 Missing ⚠️
Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #2612      +/-   ##
==========================================
+ Coverage   82.85%   86.96%   +4.11%     
==========================================
  Files         166      105      -61     
  Lines       22508    12077   -10431     
  Branches       29       29              
==========================================
- Hits        18648    10503    -8145     
+ Misses       3857     1571    -2286     
  Partials        3        3              
Flag Coverage Δ
docusaurus 95.07% <ø> (ø)
pester 86.22% <ø> (-0.01%) ⬇️
pytest 90.55% <95.88%> (+10.67%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
scripts/docs/Generate-AssetDocs.ps1 86.12% <ø> (+0.13%) ⬆️
...ata-science/ds-catalog/scripts/validate_catalog.py 98.64% <98.64%> (ø)
...rchitecture-diagrams/scripts/render_catalog_erd.py 97.05% <97.05%> (ø)
...nning/adr-author/scripts/scan_sensitive_content.py 94.77% <95.02%> (+6.93%) ⬆️
...nce/ds-feasibility/scripts/validate_feasibility.py 93.31% <93.31%> (ø)

... and 65 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@github-actions

github-actions Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Eval Execution

Status: Passed — no merge-blocking failures (96 advisory assertion failure(s) present)

  • Artifacts evaluated: 21
  • Specs run: 21
  • Assertions passed: 65
  • Assertions failed (blocking): 0
  • Assertions failed (advisory): 96
  • Failed specs (merge-blocking): 0
Artifact Kind Status Specs Passed Failed (blocking) Failed (advisory)
data-workstream-coach agent ⚠️ advisory-fail 1 0 0 60
dt-coach agent ⚠️ advisory-fail 1 4 0 1
experiment-designer agent ⚠️ advisory-fail 1 7 0 3
prd-builder agent ✅ pass 1 5 0 0
experiment-designer instruction ✅ pass 1 3 0 0
licensing-posture instruction ✅ pass 1 3 0 0
disclaimer-language instruction ⚠️ advisory-fail 1 1 0 2
untrusted-content-boundary instruction ✅ pass 1 3 0 0
dt-canonical-deck prompt ✅ pass 1 3 0 0
data-workstream-foundation skill ⚠️ advisory-fail 1 1 0 2
ds-analysis-authoring skill ⚠️ advisory-fail 1 0 0 3
ds-catalog skill ⚠️ advisory-fail 1 0 0 3
ds-dataops skill ⚠️ advisory-fail 1 6 0 6
ds-evaluation-design skill ⚠️ advisory-fail 1 1 0 2
ds-feasibility skill ⚠️ advisory-fail 1 3 0 3
ml-experimentation skill ⚠️ advisory-fail 1 0 0 3
customer-card-render skill ⚠️ advisory-fail 1 7 0 2
architecture-diagrams skill ✅ pass 1 3 0 0
adr-author skill ✅ pass 1 3 0 0
experiment-design skill ⚠️ advisory-fail 1 9 0 6
requirements-author skill ✅ pass 1 3 0 0

Legend — ✅ clean · ⚠️ advisory failures only (non-blocking) · ⏭️ skipped · ❌ merge-blocking failure

Only Failed specs (merge-blocking) gates this PR. Advisory assertion failures are signal-quality checks captured during iteration; review them, but they do not block merge and may be acceptable.

@github-actions github-actions Bot mentioned this pull request Aug 6, 2026
- reject YAML aliases, anchors, explicit tags, and merge keys

- bound input size and validate RFC 3339 timestamps

- detect lineage cycles with a three-colour depth-first search

- pin jsonschema format-nongpl extras for format assertions

* - Generated by Copilot
- seed ds-catalog, ds-feasibility, and architecture-diagrams harnesses

- cover valid, malformed, duplicate-key, and missing-block parser paths

- unblock the Fuzz Tests lane that requires tests/corpus to exist

* - Generated by Copilot
- move budgets to budgets.json with target, ceiling, and rationale

- warn above target and fail only above ceiling

- stop shared instruction growth from failing unrelated changes

- require a rationale whenever a ceiling exceeds its target

* - Generated by Copilot
- resolve broken Docusaurus links to numbered design-session pages

- replace two terms the inclusive-language gate rejects

- add data-science vocabulary and stems to the cspell word list

* - Generated by Copilot
…nsolidation

# Conflicts:
#	docs/reference/README.md
#	docs/reference/skills/README.md
#	evals/behavior-conformance/skill-behavior.eval.yaml

@jkim323 Jamie Kim (jkim323) left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the exceptionally thorough work on this PR! I especially appreciate the effort to make the new skill-first model explicit rather than simply moving content around. Once the remaining contract and package-closure issues are addressed, this should provide a much stronger and more maintainable Data Science workstream foundation.

Comment thread .github/plugin/marketplace.json
Comment thread .github/agents/data-science/data-workstream-coach.agent.md Outdated
Comment thread .github/agents/data-science/data-workstream-coach.agent.md
Comment thread .github/skills/data-science/ml-experimentation/references/ml-checklists.md Outdated
@jkim323

Copy link
Copy Markdown
Collaborator

I noticed a licensing inconsistency that I hope to have a better understanding of... The new ds-dataops provenance and licensing-posture.instructions.md classify the Microsoft Code With Engineering Playbook documentation as CC BY 4.0, with MIT applying only to upstream code samples. However, several new design-session documents describe the Playbook content as MIT-licensed and recommend license: MIT in skill frontmatter.

Is the intended policy that these skills are CC-BY-4.0 because they derive from Playbook documentation, with MIT used only when reproducing upstream code samples? If so, I think we should consider updating the stale design-session guidance and the sample frontmatter to avoid steering future authors toward the wrong declaration...

Comment thread .github/skills/data-science/ds-catalog/scripts/validate_catalog.py

@jkim323 Jamie Kim (jkim323) left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One more...! Thank you for working on it :)

…dback

- ship privacy-standards, telemetry-foundations, architecture-diagrams, and adr-author in the data-science package
- route privacy-standards from the catalog and pipeline job-registry rows
- add experiment-design to the experimental, hve-core-all, and project-planning recipes
- reduce reproduced upstream checklist text and refresh Data Science skill contracts
- regenerate package documentation and reference pages

🔒 - Generated by Copilot
The Data Workstream Coach requires the shared disclaimer instructions during
initialization, but the standalone data-science recipe omitted them, so the
reference resolved in the monorepo and dangled after package installation.

- add rules/shared/disclaimer-language.instructions.md to the data-science recipe
- regenerate package documentation

🔒 - Generated by Copilot
…nderer

Adjacent string literals inside list displays are deliberate line wraps, but
CodeQL cannot distinguish them from a missing comma. Explicit parentheses
express the grouping without changing behavior.

- wrap eight multi-line string expressions in render_catalog_erd.py

🔒 - Generated by Copilot
…ections

The handoff examples cited section names that do not exist in the shipped
feasibility-study template, so a producer following them could not satisfy the
validation rule requiring every entry to resolve to a named study section.

- replace invented section names with template sections and FS-### anchors

🔒 - Generated by Copilot
…rose

- extract the feasibility profile block by deterministic scanning so many
  unterminated begin markers cannot force quadratic backtracking
- convert recursive parser exhaustion into the documented validation error in
  both the catalog and feasibility validators
- evaluate narrative anchors and requirement headings against prose only,
  blanking the authoritative block and fenced code
- add regression tests for bounded extraction, nesting depth, and fenced content

🔒 - Generated by Copilot
…workstream-consolidation

# Conflicts:
#	.github/agents/data-science/eval-dataset-creator.agent.md
#	evals/agent-behavior/expectations/eval-dataset-creator.expectations.yml
Port population coverage, validation provenance, detecting-metric guidance, and responsibility/safety metric vocabulary from the retired evaluation agent into ds-evaluation-design. Keep assessment ownership with rai-planner and extend the existing knowledge stimulus.

🔒 - Generated by Copilot
Replace three supporting Markdown outputs with one sectioned evaluation guide while preserving curation notes, metric selection, tooling recommendations, review checkboxes, and the risks-and-detecting-metrics boundary.

BREAKING CHANGE: ds-evaluation-design now emits one evaluation guide instead of three separate supporting Markdown documents.

🔒 - Generated by Copilot
Replace the remaining plural supporting-document references after ds-evaluation-design consolidated its curation, metric, and tooling material into one evaluation guide.

🔒 - Generated by Copilot
- drop all ten design-session documents from the repository

- resolve the Playbook licensing contradiction at its source rather than in place

🗑️ - Generated by Copilot
- replace the extra with base jsonschema in ds-catalog and ds-feasibility

- re-lock both skills, removing 14 extra-only packages including MPL-2.0 and GPL-compound licenses

- allowlist pkg:pypi/pyyaml, whose PyPI metadata declares no SPDX expression

🔒 - Generated by Copilot
- rename the top-level evidence_refs field to evidence_sections with a closed section set

- scope candidate evidence_refs to FS-### display references and keep study_item_id as the durable UUID

- replace the single global rule with field-specific validation and align both examples and the PRD consumer

🔗 - Generated by Copilot
- replace 33 fundamentals items with one applicability summary per section heading

- regroup 11 production items into five repository-original readiness domains

- correct the skill and provenance claims that asserted item labels were preserved

📄 - Generated by Copilot
@WilliamBerryiii

Copy link
Copy Markdown
Member Author

Thanks for catching this, and sorry for the delayed reply. Responding to your licensing question above.

Your reading of the policy is the correct one. licensing-posture.instructions.md and THIRD-PARTY-NOTICES both treat the Code With Engineering Playbook documentation as CC BY 4.0, with MIT applying only to upstream code samples through the project's separate LICENSE-CODE file. Skills derived from Playbook documentation therefore declare CC-BY-4.0, which is what ml-experimentation, ds-dataops, and data-workstream-foundation already do.

The design-session documents contradicted that, and when I inventoried them the problem was wider than the two files first identified: the MIT claim appeared across seven of the ten documents, including two copyable license: MIT frontmatter samples.

Rather than correct them in place, we removed the design-session content from the repository entirely (56240063). They were working artifacts rather than shipped guidance, so deleting them removes both the incorrect claims and the copy targets at their source.

Separately, the Dependency Review license gate now passes. The six incompatible-license findings came from jsonschema[format-nongpl], whose name means "no GPL" rather than "no copyleft" and still pulled fqdn (MPL-2.0), rfc3987-syntax, and lark. The only asserted format in either schema is date-time, and both validators already carry a local RFC 3339 checker, so the extra was removed rather than allowlisted around (adfca287).

Close the stimulus-presence gap that failed all four Eval Execute lanes after this branch modified the licensing-posture instruction.

🧪 - Generated by Copilot
- PyYAML timestamp construction raises a bare ValueError for out-of-range dates, bypassing the yaml.YAMLError conversion and the CatalogRenderError contract

- re-raise CatalogRenderError first, since it subclasses ValueError, then convert remaining scalar errors

- add a regression test for out-of-range day, month, and day-of-month values

🐛 - Generated by Copilot
- PyYAML timestamp construction raises a bare ValueError for out-of-range dates, bypassing the documented validation-error contract

- completes the A9 defect class across ds-catalog, ds-feasibility, and architecture-diagrams

- add regression tests for out-of-range day, month, and day-of-month values

🐛 - Generated by Copilot
- stage the agent as workspace instructions with its two declared skills
- replace two order-coupled graders with six semantic invariants
- add generator environment and grader regression coverage
- clarify smoke, functional, and A/B coverage ownership

🔬 - Generated by Copilot
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Consolidate the Data Science workstream: retire five specialist agents into skill-primary coach jobs

4 participants