Skip to content
markdown-contract

INFERENCE-INIT-08: Inline vs split, and place with --out/--force

What it demonstrates

Section titled “What it demonstrates”

–inline collapses the meta-config to one self-contained file, while –out and –force control where it lands and whether it overwrites.

Builds on: INFERENCE-INIT-04: Emit a corpus meta-config with –meta

How it’s done

Section titled “How it’s done”

A terminal session: the command as you’d run it, followed by the output it prints; trailing comments note the exit status.

Terminal window
# one self-contained markdown-contract.yaml (each rule carries its contract def inline),
# written under ./config, overwriting any existing scaffold there
markdown-contract init ./docs --meta --inline --out ./config --force
#   init: inferred N contract(s); wrote 1 file(s):  markdown-contract.yaml
# without --inline: a router + contracts/<name>.contract.yaml per group
# without --force: refuses to clobber an existing config (exit 2):
#   markdown-contract: refusing to overwrite <path> (pass --force to overwrite)

Surfaces exercised

Section titled “Surfaces exercised”
  • InferOptions.inline (emitMetaFiles inline vs split)
  • --out placement
  • --force clobber guard