# Minimum Viable Maintenance Standard

- **Artifact ID:** CHQ-D-2026-MVM
- **Version:** v1.0
- **Status:** ACTIVE
- **Public record:** https://record.cybersecurityhq.com/doctrine/chq-d-2026-mvm
- **Machine-record SHA-256:** `4318af5d190ed625531dd129146693271bd8a36338930375f6963b613be795e2`

## Complete structured record

```json
{
  "id": "CHQ-D-2026-MVM",
  "title": "Minimum Viable Maintenance Standard",
  "version": "v1.0",
  "issued": "2026-02-18",
  "status": "ACTIVE",
  "doctrine_class": "MAINTENANCE_STANDARD",
  "doctrine_scope": "SYSTEM",
  "governed_artifacts": [
    "Positions",
    "Pressure Records",
    "Assumptions"
  ],
  "related_doctrine": [],
  "purpose": "This document defines the minimum operational conditions required for CybersecurityHQ (CHQ) to be considered structurally maintained during any given weekly cycle.\n\nThe Minimum Viable Maintenance (MVM) standard establishes a governance floor. It defines the minimum artifact production and registry discipline required to preserve corpus continuity and institutional integrity under constrained operating conditions.\n\nMVM defines a floor, not a ceiling.",
  "sections": [
    {
      "heading": "SCOPE",
      "content": [
        "This doctrine applies to the weekly operational cycle of CHQ and governs:",
        "• Weekly anchor publication",
        "• Pressure Record logging",
        "• Assumption registry delta validation",
        "",
        "This doctrine does not prescribe content scope, analytical depth, or thematic direction. It defines only the minimum structural requirements for corpus continuity."
      ],
      "type": "paragraph"
    },
    {
      "heading": "MINIMUM VIABLE MAINTENANCE CONDITIONS",
      "content": [
        "For a weekly cycle to be considered maintained, all three of the following conditions must be satisfied:",
        "",
        "1. Weekly Anchor Issuance",
        "At least one Weekly Anchor artifact must be published within the cycle. The Anchor may be shorter or narrower in scope than prior weeks. Depth variation does not invalidate maintenance status. Absence of a Weekly Anchor constitutes structural lapse.",
        "",
        "2. Pressure Record Logging",
        "At least one Pressure Record must be logged within the cycle. The record may be skeletal. It must include: Date, Condition observed, Assumption(s) impacted (if applicable). Narrative expansion is not required for MVM compliance. Absence of a Pressure Record constitutes structural lapse.",
        "",
        "3. Assumption Registry Delta Check",
        "A registry delta validation must occur within the cycle. The validation must explicitly determine: Whether any observed condition materially stressed an existing assumption, Whether no structural delta occurred. If no delta occurred, \"No structural delta\" must be recorded in the Pressure Record for that week. Absence of registry validation constitutes structural lapse."
      ],
      "type": "paragraph"
    },
    {
      "heading": "FAILURE CONDITION",
      "content": [
        "If any one of the three MVM conditions is not satisfied within a weekly cycle, that cycle is considered structurally lapsed.",
        "Structural lapse must be logged in the subsequent cycle."
      ],
      "type": "paragraph"
    },
    {
      "heading": "RELATION TO OTHER DOCTRINE",
      "content": [
        "MVM operates independently of Stability Status (CHQ-D-2026-SS) and Reliance Registration Requirement (CHQ-R-2026-001).",
        "MVM governs corpus continuity. Stability Status governs artifact reliance classification. Reliance Registration governs external citation and accountability."
      ],
      "type": "paragraph"
    },
    {
      "heading": "GOVERNANCE",
      "content": [
        "MVM compliance is self-enforced by CHQ editorial authority.",
        "Future revisions to MVM must be versioned and logged."
      ],
      "type": "paragraph"
    }
  ]
}
```