| name | haipipe-data-case |
| description | Stage 3 (Case) specialist: builds/runs/reviews TriggerFn / CaseFn, inspects 3-CaseStore, loads case-layer assets, runs multi-partition in parallel (embarrassingly parallel). Called by /haipipe-data; direct invocation works stage-scoped. |
| argument-hint | [function] [args...] |
| allowed-tools | Bash, Read, Write, Edit, Grep, Glob |
| metadata | {"version":"0.1.3","last_updated":"2026-07-08","summary":"Stage 3 (Case) specialist with multi-partition + parallel support."} |
Skill: haipipe-data-case
Stage 3 specialist.
Owns CaseFn work and the 3-CaseStore layer.
Called by the /haipipe-data orchestrator; can also be invoked directly.
Function axis: dashboard | load | cook | design-chef | design-kitchen | review
Commands
/haipipe-data-case -> dashboard: 3-CaseStore status
/haipipe-data-case dashboard -> same
/haipipe-data-case load -> load and inspect existing Case_Set
/haipipe-data-case cook -> run Case_Pipeline with config
/haipipe-data-case design-chef -> create new CaseFn via builder
/haipipe-data-case design-kitchen -> modify Case_Pipeline infrastructure
/haipipe-data-case review [file_path] -> structural review of a Case-layer file
Dispatch Table
Invocation This skill's ref Umbrella's fn doc
---------------- --------------------------- ---------------------------------------------------
dashboard ref/concepts.md ../haipipe-data/fn/fn-0-dashboard.md
load ref/concepts.md ../haipipe-data/fn/fn-1-load.md
cook ref/concepts.md ../haipipe-data/fn/fn-2-cook.md
design-chef ref/concepts.md +
../haipipe-data-aidata/
ref/concepts.md ../haipipe-data/fn/fn-3-design-chef.md
design-kitchen ref/concepts.md ../haipipe-data/fn/fn-4-design-kitchen.md
review ref/concepts.md ../haipipe-data/fn/fn-review.md
(no fn arg) ref/concepts.md (ref-only mode)
design-chef reads ../haipipe-data-aidata/ref/concepts.md because a CaseFn must produce keys/shapes that TfmFn / SplitFn can consume.
Step-by-Step Protocol
Step 0: Read ../haipipe-data/ref/0-overview.md.
Mandatory.
Step 1: Parse args after /haipipe-data-case.
Step 2: Read this skill's ref/concepts.md for stage-3 specifics.
Step 3: Read the umbrella fn doc.
Step 4: For design-chef, also read ../haipipe-data-aidata/ref/concepts.md.
Step 5: Execute, scoped to Stage 3.
Step 6: Emit the structured tail.
Stage Scope
Owns:
- CaseFn builders in the project's
NN_case_fn_develop_<cohort>/ task folder (legacy workspaces: code-dev/1-PIPELINE/3-Case-WorkSpace/)
- Generated
code/haifn/fn_case/
_WorkSpace/3-CaseStore/ cases (cohort sampling)templates/config.yaml for Case_Pipeline runs
Upstream dependency (Stage 2):
Reads _WorkSpace/2-RecStore/. Empty cases usually mean upstream record
rows didn't satisfy the trigger condition.
Hand-off contract (Stage 3 -> 4):
Each Case must expose the fields TfmFn will tensorize. Verify against
../haipipe-data-aidata/ref/concepts.md.
Partition Support
Case follows RecordSet partitions.
Each RecordSet partition (@i{i}n{n}) produces one independent CaseSet.
Embarrassingly parallel — each partition loads a small RecordSet (~100MB), no shared state.
CLI:
python -m scripts.haistepcli.case --config <config> --num-partitions 0 --num-workers 4
python -m scripts.haistepcli.case --config <config> --num-partitions 0 --partition-index 5
--num-partitions 0 = auto-discover from 2-RecStore/{name}/@i*n*.
Notebook parameters: NUM_PARTITIONS, PARTITION_INDEX, NUM_WORKERS
Parallelism:
--num-workers 4 gives ~4x speedup (each worker: ~100MB memory)- Safe because each partition is fully independent (no shared data)
- Notebook mode: sequential by default; set
NUM_WORKERS > 1 for parallel
Output naming: 3-CaseStore/{RecSet}/@i{i}n{n}/@v{ver}CaseSet-{Trigger}/
Discovery: glob.glob(LOCAL_RECORD_STORE/{name}/@i*n*) sorts by partition index.
