suaveplan/openspec/archive/2026-05-12-drive-network-integration/tasks.md

Tasks: drive-network-integration

• 1. Write openspec/changes/drive-network-integration/proposal.md — proposal authored 2026-05-01; resolves the layered architecture and responsibility contract between drive-mesh, network-plugin-registry, and network-plugin-content-delivery
• 2. Write openspec/changes/drive-network-integration/tasks.md — this file
• 3. Update openspec/changes/drive-mesh-port/proposal.md — rename PeerRegistry→PeerIndex, add NetworkBus integration section (blocked: do as part of drive-mesh-port implementation; the boundary contract is now documented in docs/drive/mesh-and-sharing.md and consumed by future implementers)
• 4. Update openspec/changes/network-plugin-content-delivery/proposal.md — add boundary note about drive-mesh scheduling (blocked: do as part of network-plugin-content-delivery implementation; the boundary contract is now in docs/drive/plugins.md under "Cross-layer ownership boundaries")
• 5. Update openspec/changes/network-suite/proposal.md — update Drive integration bullet (blocked: do as part of network-suite consolidation; reference the architecture in docs/drive-storage-network.md)
• 6. Write tests/cross-layer/dep-graph.test.ts — pin no cross-imports between drive-mesh and network-plugin-registry (blocked: cannot land before drive-mesh exists; will be written when drive-mesh-port lands)
• 7. Write tests/cross-layer/event-contract.test.ts — pin event shape contract (blocked: same — depends on both packages existing)
• 8. Update REVIEW-GAPS.md — mark drive-network integration as captured (blocked: depends on network-suite cleanup landing first)

---

Status note (2026-05-02)

Tasks 1–2 are complete: the proposal and this task file exist and codify the boundary contract.

Tasks 3–5 are spec-edit clean-ups against three downstream proposals that have not yet been implemented. Editing them in-place now would create churn against folders that will themselves be rewritten when their underlying packages are built. The boundary contract has therefore been folded into the project-level docs at docs/drive/plugins.md, docs/drive/mesh-and-sharing.md, and docs/drive-storage-network.md, and downstream proposal authors must reference these when writing the actual implementation.

Tasks 6–7 are test-authoring tasks that cannot land before the packages they constrain exist. They will be authored as part of the drive-mesh-port and network-plugin-content-delivery implementations.

This change folder will be archived once all 8 tasks are complete. Until then, it remains in openspec/changes/ as the canonical record of the responsibility contract, and downstream proposals must conform to the architecture it describes.