create-artifact

Load dh:dh-cli-usage before using <sam_cli/> or <dh_scripts/>.

Create Artifact

Register your deliverable through the configured content provider with mcp__plugin_dh_backlog__artifact_register, or use the artifact register CLI subcommand in scripting contexts. Pass the content in the registration call and return only its logical ID.

Storage boundary

• artifact_register writes through the selected provider; agents do not choose or access its storage layer.
• artifact_read(item_id, artifact_type) retrieves the current artifact through the same boundary.
• Background agents return the logical ID instead of repeating the document in their completion message.

Invocation

MCP:

mcp__plugin_dh_backlog__artifact_register(
    item_id=<int | str>,          # Backlog item identifier — REQUIRED
    artifact_type=<str>,          # Artifact type string — REQUIRED (see table below)
    artifact_id=<str>,            # Logical identifier — REQUIRED
    status="current",             # Lifecycle status: draft | current | superseded | archived
    agent=<str>,                  # Name of the producing agent (default: "")
    content=<str>,                # Non-empty full artifact content — REQUIRED
)

CLI equivalent (scripting/dispatch contexts):

<sam_cli/> artifact register \
  --item-id <identifier> \
  --artifact-type <str> \
  --artifact-id <str> \
  --status "current" \
  --agent <str> \
  --content <str>

--status and --agent are optional (same defaults as the MCP form). The examples below use the MCP form; substitute the same values into the CLI flags above for a scripting context.

Return value: dict with keys registered (bool), artifact_count (int), action ("added" or "updated"), content_stored (bool), messages, warnings. Check action in your STATUS: DONE report — do NOT paste the full content.

Parameters

artifact_type

The registry of recognised type strings, the agent permitted to register each, and which types a gate reads is dh_core/artifact_registry.py. The decomposition-exit gate imports it, and a test holds every shipped registration against it, so it is the only place a type is added or its writer changed. A call naming a (type, agent) pair it does not declare fails that test. The rules governing the registry — ownership, registration, discovery — are in docs/artifact-registry.md.