Skip to main content

hardkas why

hardkas why​

Synopsis (Generated)​

Purpose: Explain the causal lineage of an artifact resolved by exact artifactId, artifact file path, or a namespaced identifier (--plan, --signed, --tx, --workflow)

Arguments​

  • <artifact> (Optional): Exact 64-hex artifactId (the recomputed contentHash) or absolute/workspace-relative path to the artifact .json file

Options​

  • --artifact <id-or-path>: 64-hex artifactId or workspace path (same as the positional)
  • --plan <planId>: Resolve a plan by its derived label (verified against its hash)
  • --signed <signedId>: Resolve a signed transaction by its derived label (verified)
  • --tx <txId>: Resolve the submission receipt for a txId (never the signed)
  • --workflow <workflowId>: Resolve a workflow run by its correlation id
  • --json: Output lineage graph in JSON format
  • --workspace <path>: Override workspace root directory

Semantic Contract (Curated)​

  • Environments: Local Workspace
  • Reads: Artifact JSON file, Parent artifacts in lineage
  • Writes:
  • Produces:
  • Accepted Identifiers: explicit filepath, exact canonical artifactId, --plan <planId>, --signed <signedId>, --tx <txId>, --workflow <workflowId>
  • Evidence Semantics: Extended causal tracing. Identical constraints to explain.

Known Limitations​

  • A bare label, txId or workflowId is refused with NAMESPACE_REQUIRED; name its namespace flag. The --tx namespace returns the submission receipt, never the signed transaction.