{
  "@context": {
    "@language": "es-ES",
    "CIP100": "https://github.com/cardano-foundation/CIPs/blob/master/CIP-0100/README.md#",
    "CIP119": "https://github.com/cardano-foundation/CIPs/blob/master/CIP-0119/README.md#",
    "hashAlgorithm": "CIP100:hashAlgorithm",
    "body": {
      "@id": "CIP119:body",
      "@context": {
        "summary": "CIP119:summary",
        "rationale": "CIP119:rationale",
        "references": "CIP119:references"
      }
    }
  },
  "hashAlgorithm": "blake2b-256",
  "body": {
    "summary": "IO & Ensurable Systems: Cardano Maintenance Initiative",
    "rationale": "Vote: Yes\nCore node maintenance is non-negotiable infrastructure. The nine functional areas covered — bugfixing, DevOps, monitoring, documentation, open source support, performance, QA, release management, and component maintenance — represent the full support envelope without which no other ecosystem initiative can safely deliver. The Cardano Blueprint deliverable adds strategic long-term value by enabling alternative node implementations.\nThe treasury governance structure is well-designed: milestone-based smart contract disbursement through Intersect, multi-sig oversight with five independent entities, and unspent funds returning to treasury. The collaboration with Ensurable Systems to distribute infrastructure stewardship is a welcome step toward reducing single-entity dependency.\nHowever, this approval comes with noted concerns:\nThe KPI framework is insufficiently concrete. \"Monthly Uptime\" is listed as the primary KPI but no target threshold is defined. Most Cardano 2030 KPI alignments are marked \"Yes: Partially\" without specifying what partial means in measurable terms. For a ₳62M ask, the community deserves quantifiable success criteria.\nThe budget breakdown lacks granularity. 74% allocated to \"Development\" covers the entire engineering team across all nine areas, but no FTE counts, team size estimates, or per-area cost breakdowns are provided. This makes it difficult to assess whether the pricing is proportionate.\nThe prior execution record warrants attention. The IOE workstream from the current cycle shows ₳47.1M received against its allocation, described as 49% disbursed. The proposal does not explain whether this reflects pacing (on track with remaining milestones) or underdelivery. This context matters when evaluating a new ask of similar magnitude.\nThe risk assessment for increased maintenance burden from concurrent initiatives (Leios, Peras) is classified as Medium likelihood / Medium severity. Given that these represent fundamental protocol changes, t",
    "references": []
  },
  "authors": [
    {
      "name": "drep15jspgw8ea9pw3w0fwyqam2lw58ulw7z6qhr8qyuah7j0yj962w7",
      "witness": {
        "witnessAlgorithm": "ed25519",
        "publicKey": "078c04a088ee52fe58d3257993ea6ec90f0b1dd59e4456a6b0e97e81f09525df"
      }
    }
  ]
}