DIXI Spec Kit documentation Español · Source on GitHub

/dixi.compliance

Purpose

Map compliance obligations and the evidence still missing.

Map the obligations of the framework or regulation in $ARGUMENTS to project evidence.

Generated by scripts/build-command-reference.py from the packaged command text; do not edit by hand.

Invocation

Argument: <framework or regulation>. Angle brackets mark a required value and square brackets an optional one. In the steps, $ARGUMENTS is the text written after the command.

Example

The text after the command is the request; change it to match your project.

When to use it

Steps

  1. If no framework is given (for example GDPR, SOC 2, HIPAA, PCI DSS), ask and stop.
  2. Write 23-compliance/<framework>.md: each applicable obligation, the project artifact that evidences it, its owner and its status (evidenced, partial, missing).
  3. Never declare certification or legal conformity; state that the map supports, and does not replace, an auditor or legal advice.
  4. Do not include personal data or secrets as evidence.
  5. Suggest the commands that produce missing evidence (/dixi.data, /dixi.threat-model, /dixi.operate).

Files read and written

Paths named by the command text:

Stops and human gates

Closing

Run dixi check before finishing and report: files touched, checks (run, failed, not run), open items and the suggested next command.

Next step