Conformance corpus

{
  "id": "complete-001",
  "version": 3,
  "status": "approved",
  "userGoal": "Retry failed evidence syncs automatically",
  "objective": "Support engineers on the integrations rota lose the first twenty minutes of every shift reconciling overnight sync failures by hand, because a failed run leaves no retry and no alert.",
  "problemSeverity": "high",
  "outcomes": [
    "A failed connector run is retried within one minute with no human touch",
    "Morning reconciliation drops from about twenty minutes to zero on days with no permanent failure"
  ],
  "constraints": ["Permanent failures must never retry silently forever"],
  "scope": {
    "inScope": ["Transient connector failures"],
    "outOfScope": ["Alerting on permanent failures"]
  },
  "edgeCases": [
    {
      "id": "ec-1",
      "scenario": "Connector credentials expired",
      "expectedBehavior": "Retry stops after one attempt and the run is marked needs-attention"
    }
  ],
  "verification": [
    "Run the test suite, all green",
    "Force a connector failure in staging and confirm the retry fires within one minute"
  ],
  "healthMetrics": ["Retry success rate"],
  "evidence": [
    {
      "id": "INT-4471",
      "type": "friction",
      "excerpt": "Ticket INT-4471 and its three linked duplicates: overnight sync failures reconciled by hand.",
      "anchors": ["objective"]
    }
  ]
}

---
id: frontmatter-only-001
status: validated
objective: "Analysts re-filter the weekly export by hand every Monday because the export ignores the active view filters."
outcomes:
  - "The export respects the active filters with no manual re-filtering"
verification:
  - "Export from a filtered view and confirm the row count matches the view"
---

# Anything down here is free-form and contributes nothing to the model.

## Outcomes

This prose has no list items, so it does not override the frontmatter array.

{
  "id": "minimal-001",
  "status": "draft",
  "objective": "Analysts re-filter the weekly export by hand every Monday because the export ignores the active view filters.",
  "outcomes": ["The export respects the active filters with no manual re-filtering"]
}

{
  "id": "no-evidence-001",
  "status": "draft",
  "objective": "Operators cannot tell which nightly job failed without opening each log by hand.",
  "outcomes": ["A failed job is identifiable from the run list alone"],
  "verification": ["Fail a job in staging and confirm the run list marks it"]
}

---
id: retry-failed-syncs
status: draft
---

# Retry failed evidence syncs automatically

<!-- Guidance comments must not become content. -->

## Objective

Support engineers on the integrations rota lose the first twenty minutes of every shift
reconciling overnight sync failures by hand.

## Outcomes

- [ ] A failed connector run is retried within one minute with no human touch
- [ ] Morning reconciliation drops from about twenty minutes to zero

## Constraints

- Permanent failures must never retry silently forever

## Edge Cases

- **Connector credentials expired**: retry stops after one attempt and the run is marked needs-attention

## Evidence References

- Ticket INT-4471 and its three linked duplicates

## Verification

**Fastest check**:
- [ ] Run the test suite, all green

**Manual check**:
- [ ] Force a connector failure in staging and confirm the retry fires within one minute

Rejected because Malformed YAML frontmatter fails the whole document. A consumer must not fall back to reading the body. SPEC.md section 2.

---
id: broken
status: "draft
objective: unterminated quote above
---

<!-- _reason: Malformed YAML frontmatter fails the whole document. A consumer must not fall back to reading the body. SPEC.md section 2. -->

## Outcomes

- This must not rescue the document

Rejected because An edgeCases item requires both 'scenario' and 'expectedBehavior'. A failure mode with no expected behavior is a worry, not an edge case.

{
  "_reason": "An edgeCases item requires both 'scenario' and 'expectedBehavior'. A failure mode with no expected behavior is a worry, not an edge case.",
  "id": "invalid-004",
  "status": "draft",
  "objective": "Analysts re-filter the weekly export by hand every Monday.",
  "outcomes": ["The export respects the active filters"],
  "edgeCases": [{ "scenario": "The saved view was deleted" }]
}

Rejected because An evidence item requires both 'type' and 'excerpt'. See SPEC.md section 6: in a repo-safe document the excerpt is a summary or reference, but it must be present.

{
  "_reason": "An evidence item requires both 'type' and 'excerpt'. See SPEC.md section 6: in a repo-safe document the excerpt is a summary or reference, but it must be present.",
  "id": "invalid-005",
  "status": "draft",
  "objective": "Analysts re-filter the weekly export by hand every Monday.",
  "outcomes": ["The export respects the active filters"],
  "evidence": [{ "type": "friction" }]
}

Rejected because Missing the required 'objective' field.

{
  "_reason": "Missing the required 'objective' field.",
  "id": "invalid-001",
  "status": "draft",
  "outcomes": ["Something observable changes"]
}

Rejected because 'outcomes' must be an array of strings, not a string.

{
  "_reason": "'outcomes' must be an array of strings, not a string.",
  "id": "invalid-003",
  "status": "draft",
  "objective": "Analysts re-filter the weekly export by hand every Monday.",
  "outcomes": "The export respects the active filters"
}

Rejected because Sections carry the lists, but id and status have no section form, so this is not yet a valid document. SPEC.md section 3.

<!-- _reason: Sections carry the lists, but id and status have no section form, so this is not yet a valid document. SPEC.md section 3. -->
# Retry failed syncs

## Objective

Support engineers lose twenty minutes a shift to manual reconciliation.

## Outcomes

- A failed run is retried within one minute

Rejected because 'status' is not one of draft|validated|approved|shipped|verified.

{
  "_reason": "'status' is not one of draft|validated|approved|shipped|verified.",
  "id": "invalid-002",
  "status": "in-progress",
  "objective": "Analysts re-filter the weekly export by hand every Monday.",
  "outcomes": ["The export respects the active filters"]
}