Dataset Intelligence Router
Ask only for the source path or URI and desired outcome if they are not already
present. Do not require the user to choose a schema, adapter, backend, index, or
provenance vocabulary.
- Invoke
dataset-intake and return a concise recommendation containing:
assumptions, rationale, privacy/locality/network implications, materialized
artifacts, and safe defaults.
- Route assessment to
dataset-source-assess, capability composition to
dataset-capability-recommend, and approval preparation to
dataset-plan-review.
- Route an approved plan to
dataset-ingest; route inspection to
dataset-trace or dataset-verify; route portable output to
dataset-export; route removal to dataset-retire.
- Carry stable intake, plan, run, checkpoint, approval, verification, and
evidence references between phases. Never rely on conversation state as the
record of authority.
Every operational step delegates to aiwg dataset. This router must not read a
source, execute a connector, write an index, advance a checkpoint, or delete
data. Indexes and Fortemi shards are derived, never canonical persistence.
SDLC, research, knowledge-base, media, marketing, ops, and project-local callers
all use the same intake and handoff contracts; domain additions are namespaced.
1---2namespace: aiwg3name: dataset-intelligence4description: Route any dataset, custom indexing, traceability, provenance, lineage, synchronization, or retirement request through one governed workflow. Use when a user points AIWG at data and wants an outcome without knowing schema or indexing terminology.5version: 1.0.06platforms: [all]7kernel: true8aliases: [dataset, data steward, data onboarding, custom indexing, dataset workflow]9triggers: [use this data, make this searchable, index my files, build a knowledge index, trace this dataset, show data provenance, sync this source, retire this dataset, point AIWG at data, use a dataset offline, write a source adapter, migrate index graphs]10metadata:11 source: https://skillmd.com/skills/jmagly-ai-writing-guide/dataset-intelligence12---1314# Dataset Intelligence Router1516Ask only for the source path or URI and desired outcome if they are not already17present. Do not require the user to choose a schema, adapter, backend, index, or18provenance vocabulary.19201. Invoke `dataset-intake` and return a concise recommendation containing:21 assumptions, rationale, privacy/locality/network implications, materialized22 artifacts, and safe defaults.232. Route assessment to `dataset-source-assess`, capability composition to24 `dataset-capability-recommend`, and approval preparation to25 `dataset-plan-review`.263. Route an approved plan to `dataset-ingest`; route inspection to27 `dataset-trace` or `dataset-verify`; route portable output to28 `dataset-export`; route removal to `dataset-retire`.294. Carry stable intake, plan, run, checkpoint, approval, verification, and30 evidence references between phases. Never rely on conversation state as the31 record of authority.3233Every operational step delegates to `aiwg dataset`. This router must not read a34source, execute a connector, write an index, advance a checkpoint, or delete35data. Indexes and Fortemi shards are derived, never canonical persistence.3637SDLC, research, knowledge-base, media, marketing, ops, and project-local callers38all use the same intake and handoff contracts; domain additions are namespaced.