version: 1.0
description: CASAN H6 per-step hallucination signal tracking

tracking:
  enabled: true
  method: cross_reference_check
  log_path: .specify/logs/cost/metrics.jsonl
  field_name: hallucination_signals

steps_with_tracking:
  - step: step-1-srs
    reference_docs:
      - docs/input/okr-requirement.md
    signals:
      - ungrounded_feature_claim
      - invented_requirement
      - undefined_acronym
    keywords_indicating_hallucination:
      - "I assume"
      - "typically"
      - "usually includes"
      - "standard practice suggests"

  - step: step-3-spec
    reference_docs:
      - docs/output/ipa-docs/srs/
      - docs/output/ipa-docs/bd/
    signals:
      - invented_api_endpoint
      - schema_mismatch
      - undefined_term
      - ungrounded_business_rule
    keywords_indicating_hallucination:
      - "assumed from context"
      - "common pattern would be"
      - "likely the intent is"

  - step: step-6-plan
    reference_docs:
      - docs/output/specs/
    signals:
      - invented_dependency
      - wrong_module_assignment
      - unspecified_library
    keywords_indicating_hallucination:
      - "might need"
      - "could potentially use"
      - "I believe"

  - step: step-10-implement
    reference_docs:
      - docs/output/specs/
    signals:
      - undocumented_endpoint
      - wrong_field_type
      - missing_required_field
      - hardcoded_value_not_in_spec
    keywords_indicating_hallucination:
      - "// TODO: confirm"
      - "// assumed"
      - "// placeholder"

  - step: step-11-review-code
    reference_docs:
      - docs/output/specs/
      - backend/
      - frontend/
    signals:
      - false_security_clearance
      - invented_test_result
      - unverified_compliance_claim

thresholds:
  warn: 3
  block: 7
  note: "warn=log warning; block=force retry of step"