data-science-engineering-foundation
State, resume, reconstruction, job-lifecycle, transition, and flow-state mechanics for the Data Science and Engineering Coach. Loaded by the coach; not a user entry point.
- License 许可
- CC-BY-4.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 355
01 前言 Front Matter
- name
- data-science-engineering-foundation
- license
- CC-BY-4.0
- metadata
- { "authors": "microsoft/hve-core", "last_updated": "2026-08-03", "spec_version": "1.0" }
- description
- State, resume, reconstruction, job-lifecycle, transition, and flow-state mechanics for the Data Science and Engineering Coach. Loaded by the coach; not a user entry point.
- user-invocable
- false
02 资源文件 5
- 参考文档references/flow-state.md5.3 KB
- 参考文档references/job-registry.md17.8 KB
- 参考文档references/lifecycle-classes.md4.0 KB
- 参考文档references/session-state.md6.9 KB
- 参考文档references/transition-protocol.md3.0 KB
03 SKILL.md 正文
Data Science and Engineering Foundation
Goal
Keep Data Science and Engineering Coach orchestration consistent across job changes and sessions without duplicating job-specific guidance. The coach loads this index at initialization and resume, then reads the reference for the current coaching moment.
Reference index
| Reference | When to read |
|---|---|
| job-registry.md | Before offering or selecting a job, routing to a skill or specialist, or naming a durable output |
| lifecycle-classes.md | When starting, pausing, resuming, completing, or re-invoking a job |
| transition-protocol.md | When a topic shift, explicit request, or completion suggests moving between jobs |
| session-state.md | Before initialization, validation, mutation, resume, recovery, or reconstruction of coaching state |
| flow-state.md | Before interrupting work, crossing a gate, writing a durable artifact, or offering post-job choices |
Success criteria
- Each orchestration rule has one owner in this package.
- State and lifecycle mechanics remain independent of job-specific methods.
- The coach reads the applicable reference before acting on its contract.
Constraints
- Keep catalog guidance in
data-catalog, the durable data-catalog workflow for entities, declared relationships, lineage, and ERD-ready model semantics. - Keep feasibility guidance in
feasibility, the evidence-led data and ML feasibility-study workflow with lifecycle and interchange traceability. - Keep pipeline and testing guidance in
dataops, the DataOps reference for tier behavior, pipeline invariants, validation placement, tests, drift, and operational signals. - Keep general experiment guidance in
experiment-design, the reusable workflow for candidate selection, hypotheses, vetting, minimum scope, and result evaluation. - Keep ML-specific experiment guidance in
ml-experimentation, the reference for ML environments, reproducibility, tracking, evaluation, abstractions, and production readiness. - Keep notebook and dashboard guidance in
analysis-authoring, the reference for EDA notebook and analytical dashboard composition, visualization selection, and dashboard validation. - Keep AI-system evaluation guidance in
evaluation-design, the reference for evaluation dataset design, difficulty balance, metric selection, and tooling fit. - Treat this package as internal foundation knowledge, not a user-selectable workflow.
- Preserve the skill authority boundaries and cross-cutting concerns defined in the job registry.
Stop rules
- Stop before a state mutation when the session-state protocol has not been loaded or project identity is uncertain.
- Stop before a job switch when the user has not confirmed the transition.
- Stop and report the missing owner when requested behavior belongs to neither this foundation nor a registered job capability.
Attribution
This package is repository-original orchestration guidance licensed under CC BY 4.0. It does not reproduce or summarize an external standard.
04 同仓库更多 Skills
statistical-hypothesis-testing
Compare binary rates or average values across affected and unaffected cohorts during root cause analysis. Use when root-cause-analysis selects an applicable affected-versus-unaffected cohort comparison.
root-cause-analysis
Investigate incidents, software defects, and data or process failures by forming falsifiable hypotheses, executing tests against available evidence, and iterating to a verified causal explanation or an explicit evidence blocker. Use when performing root cause analysis, incident investigation, or postmortem analysis, with cost and model choice confirmed before a full investigation.
causal-evidence-likelihood
Assess how one evidence item changes an RCA hypothesis using an uncalibrated, model-elicited likelihood-ratio band. Use when root-cause-analysis selects an eligible hypothesis-evidence pair.
untrusted-content-boundary
Untrusted-content boundary: treat ingested external content as data, not instructions, and refuse embedded authority changes. Preloaded by agents that read external, tracker, or user-supplied content.
telemetry-foundations
Declarative OpenTelemetry-aligned telemetry vocabulary and instrumentation conventions for traces, metrics, logs, and PII handling
pr-reference
Generates PR reference XML with commit history and unified diffs between branches, with extension and path filtering. Use when creating pull request descriptions, preparing code reviews, analyzing branch changes, discovering work items from diffs, or generating structured diff summaries.