Skip to content

.content-state.yaml Schema

Persistent tracking file for IMS content development. Lives in the V004 IMS Handbuch repo root. Created by /vt-v-cwp init, updated by /vt-v-cwp and /vt-v-sprint.

Location

/Users/rolf/01-repositories/03-VisiTrans/V004-VisiTrans Handbuch -dev/.content-state.yaml

Top-Level Fields

version: 1                     # Schema version
created_at: "2026-02-24T..."   # ISO 8601 timestamp
updated_at: "2026-02-24T..."   # Updated on every write

Metrics Sections

baseline

Snapshot taken when .content-state.yaml was initialized. Never changes after creation.

baseline:
  scan_date: "2026-02-24"
  compliance_score: 88.3
  content_depth:
    complete: 374
    partial: 239
    skeleton: 70
    empty: 2
  cross_ref_rate_pct: 7.7
  review_coverage_pct: 96.6
  approval_coverage_pct: 92.6
  total_files: 685

current

Latest metrics, updated after each CWP completion.

current:
  scan_date: "2026-02-28"       # Date of last scan
  compliance_score: 90.1        # Updated after each CWP
  content_depth:
    complete: 420
    partial: 210
    skeleton: 53
    empty: 2
  cross_ref_rate_pct: 15.2
  review_coverage_pct: 97.0
  approval_coverage_pct: 94.0
  total_files: 685

targets

From PRD/constitution. Used by dashboard to show gap.

targets:
  compliance_score: 85
  content_depth_complete_pct: 80
  cross_ref_rate_pct: 60
  review_coverage_pct: 90
  approval_coverage_pct: 95

CWP Status Section

cwp_status:
  CWP-01:
    name: "Richtlinien (IMS)"
    layer: 1
    domain: IMS
    content_type: richtlinie     # Primary filter field
    filter_extra: null            # Additional filter (e.g., norm, chapter prefix)
    file_count: 55               # Expected file count
    batch_size: 5
    status: pending              # pending | in_progress | review | completed | blocked
    dependencies: []             # CWP IDs this depends on
    human_tasks:                 # Description of what humans need to do for this CWP
      - "Verify reifegrad claims match actual implementation"
      - "Confirm policy approval dates"
    progress:
      total_files: 55
      files_written: 0           # Files AI has enriched
      files_reviewed: 0          # Files that passed /ims-review
      files_escalated: 0         # Files needing human decision
    started_at: null
    completed_at: null
    sprint_branch: null          # e.g., "feature/ims-content-cwp-01"
    metrics_before: null         # Compliance score before CWP work
    metrics_after: null          # Compliance score after CWP work

Status Values

Status Meaning
pending Not started, may have unmet dependencies
in_progress Active work via /ims-sprint --cwp
review AI work done, waiting for human review/actions
completed All files done and reviewed, metrics recorded
blocked Cannot proceed (dependency or human action required)

Human Actions Section

Cross-cutting actions that humans must perform. Not tied to a single CWP.

human_actions:
  - id: HA-01
    description: "Reifegrad-Workshop: Review AI-suggested reifegrad for ISMSI controls"
    status: pending              # pending | in_progress | completed
    cwps: [CWP-04, CWP-05, CWP-06, CWP-07, CWP-08, CWP-09]
    notes: null                  # Free-text notes from user
    created_at: "2026-02-24T..."
    completed_at: null

Pre-defined Human Actions

ID Description Blocking CWPs
HA-01 Reifegrad-Workshop for ISMSI controls CWP-04..09
HA-02 VVT completeness check CWP-12
HA-03 Supplier contract verification CWP-15
HA-04 KPI target value setting CWP-16
HA-05 Management review data CWP-19

Note: HA items do not hard-block CWPs. AI can still draft content; the human action is needed to finalize/verify. The blocked status is set manually when the CWP genuinely cannot proceed without the human input.

Sprint History Section

Appended after each sprint completes.

sprints:
  - id: 1
    date: "2026-02-25"
    cwp: CWP-01
    batches_processed: 11
    files_processed: 55
    duration_minutes: null       # Optional
    metrics_delta:
      compliance_score: +1.2
      cross_ref_rate_pct: +3.5

Example: Reading State for Dashboard

To generate the /ims-cwp status dashboard:

  1. Read current metrics and compare to targets
  2. Group cwp_status by layer
  3. For each CWP: show name, file_count, status, progress fraction
  4. Count pending human_actions
  5. Identify next actionable CWP (pending with all dependencies completed)