cursus.mcp.tools.author

author.* — the agent step-authoring guidance namespace (FZ 31e1d3f5).

Under Design B a step is authored as ONE .step.yaml + ONE config class + ONE script; the builder is synthesized and the registry is derived by construction (writing the .step.yaml IS the registration). This small namespace gives an authoring agent the SOP + restrictions + a constructibility proof, WITHOUT a generator (the agent writes the files with its own Write tool) and WITHOUT duplicating any enforcement logic:

  • author.checklist(sagemaker_step_type[, step_assembly]) — the ordered author→validate→integrate SOP as DATA naming the existing tools to call at each step. The routing branch is derived from the live strategy_registry so the “which handler / which assembly” answer can’t drift.

  • author.rules(topic) — the restriction set, by INTROSPECTING the live enforcement objects (PASCAL_CASE_PATTERN, the two distinct _REQUIRES enums, _KINDS / _SDK_CLASSES / _ASSEMBLIES / _SAGEMAKER_STEP_TYPES, the source_dir packaging fact). Guidance is definitionally equal to enforcement; a conformance/identity test keeps it from drifting.

  • author.preflight_step(step_name | all) — the offline constructibility proof: a FLAT list of the same gates CI runs as its merge gate (interface validation + registry-snapshot parity + RegistryBindingValidator B3 + resolve_strategy routability). SDK-delegation rows report skip-not-error offline. This proves a step is CONSTRUCTIBLE (binds + synthesizes), not merely parseable, before a code review.

All three are read-only, stateless, and offline-safe. They compose existing engines/constants — they add no new validation logic of their own.