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---2name: dataset-intelligence3description: 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.4---56# Dataset Intelligence Router78Ask only for the source path or URI and desired outcome if they are not already9present. Do not require the user to choose a schema, adapter, backend, index, or10provenance vocabulary.11121. Invoke `dataset-intake` and return a concise recommendation containing:13 assumptions, rationale, privacy/locality/network implications, materialized14 artifacts, and safe defaults.152. Route assessment to `dataset-source-assess`, capability composition to16 `dataset-capability-recommend`, and approval preparation to17 `dataset-plan-review`.183. Route an approved plan to `dataset-ingest`; route inspection to19 `dataset-trace` or `dataset-verify`; route portable output to20 `dataset-export`; route removal to `dataset-retire`.214. Carry stable intake, plan, run, checkpoint, approval, verification, and22 evidence references between phases. Never rely on conversation state as the23 record of authority.2425Every operational step delegates to `aiwg dataset`. This router must not read a26source, execute a connector, write an index, advance a checkpoint, or delete27data. Indexes and Fortemi shards are derived, never canonical persistence.2829SDLC, research, knowledge-base, media, marketing, ops, and project-local callers30all use the same intake and handoff contracts; domain additions are namespaced.
jmagly