id: T005
name: PlasmaVMC Specification Design
status: complete
created: 2025-12-08
owner: peerA
goal: Create comprehensive specification for VM infrastructure platform

description: |
  Design PlasmaVMC (VM Control platform) specification following TEMPLATE.md.
  Key requirements from PROJECT.md:
  - Abstract hypervisor layer (KVM, FireCracker, mvisor)
  - Multi-tenant VM management
  - Integration with aegis (IAM), overlay network

trigger: IAM P0s complete (S5+S6) per T003 Modified (B) Parallel decision

acceptance:
  - specifications/plasmavmc/README.md created
  - Covers: architecture, API, data models, hypervisor abstraction
  - Follows same structure as chainfire/flaredb/iam specs
  - Multi-tenant considerations documented

steps:
  - step: S1
    action: Research hypervisor abstraction patterns
    status: complete
    notes: Trait-based HypervisorBackend, BackendCapabilities struct

  - step: S2
    action: Define core data models
    status: complete
    notes: VM, Image, Flavor, Node, plus scheduler (filter+score)

  - step: S3
    action: Design gRPC API surface
    status: complete
    notes: VmService, ImageService, NodeService defined

  - step: S4
    action: Write specification document
    status: complete
    output: specifications/plasmavmc/README.md (1017 lines)

parallel_with: T004 S2-S4 (Chainfire remaining P0s)

notes: |
  This is spec/design work - no implementation yet.
  PeerB continues T004 Chainfire fixes in parallel.
  Can delegate S4 writing to Aux after S1-S3 design decisions made.