Status Report: ICN — March 2026

Author: Matt Faherty | Date: March 16, 2026 Period: March 1–16, 2026

Executive Summary

ICN had a strong first half of March. The feat/demo-federation-system branch merged to main on March 13, completing Phase 0 and Phase 1 and bringing the project to roughly 75% overall. The ops layer was significantly consolidated — icn-ops is deprecated and its v2 schema is now canonical in icn/ops/mcp. Infrastructure blockers (K3s connectivity, icn-dev disk pressure) are resolved. The next focus is scoping Phase 2 and stabilizing the build pipeline.

Overall Status: 🟡 On Track with Watch Items

Key Milestones

Accomplishments This Period

• Merged feat/demo-federation-system → main (Mar 13)
• Completed Phase 0 + Phase 1; project at ~75% across 38 crates
• Shipped @icn/ops-mcp v0.1.0 with 8 tool sets: sessions, tasks, repos, health, decisions, comms, events, watchers — plus process poller and zombie prevention
• Deprecated icn-ops; v2 schema now live in icn/ops/mcp as canonical source of truth
• Resolved K3s ↔ icn-dev connectivity (Mar 12) — both now on VLAN 30
• Cleared 143GB of Rust build artifacts from icn-dev (Mar 4)

In Progress / Watch Items

Risks and Issues

Next Period Priorities

1. Define Phase 2 scope
2. Complete WireGuard/elitebook VPN setup
3. Evaluate Sovereign Tech Fund grant application timing relative to Phase 2 milestone

ICN Phase 2 Plan: Demo-Ready

Goal: A polished guided walkthrough (video or live) demonstrating ICN's federation capabilities to an audience of cooperative organizers, funders, and technologists. Timeline: March 17 – April 17, 2026 Exit criteria: A recorded or scriptable demo + enough supporting documentation to submit an ICN workshop proposal for the NY Coop Summit call for presenters in May.

Week 1 (Mar 17–23): Assess & Scope

The honest answer on weakest area is "not sure yet," so this week is about finding out.

• Audit the current state. Walk through the merged federation demo end-to-end. Catalog what works, what's fragile, and what's missing for a convincing story.
• Define the demo scenario. Pick a concrete cooperative use case (e.g., two cooperatives federating to share resources or coordinate a decision). Write a 1-page script: what the audience sees, what's happening underneath.
• Identify blockers. List anything that would panic, fail, or look unfinished during the walkthrough. Prioritize ruthlessly — only fix what the demo touches.

Deliverable: Demo script (1 page) + blocker list with severity ratings.

Week 2 (Mar 24–30): Stabilize & Build

Fix the things that would embarrass you during the walkthrough.

• Fix demo-path bugs. Work through the blocker list from Week 1, focusing only on the demo's critical path.
• Fill narrow gaps. If the demo scenario needs a feature that's 80% there, finish it. If it needs something that's 0% there, simplify the scenario instead.
• Stand up the demo environment. Get a clean K3s deployment or local setup that reliably runs the walkthrough scenario without manual workarounds.

Deliverable: A repeatable demo environment that runs the scenario clean.

Week 3 (Mar 31–Apr 6): Document & Narrate

This is where the grant-readiness comes in. The code is only half the story.

• Write the narrative layer. A plain-language overview of what ICN does, who it's for, and why it matters — aimed at cooperative organizers, not developers. This becomes the backbone for both the summit proposal and any grant applications.
• Document the architecture (briefly). A one-page diagram + caption showing the federation model. Not a deep spec — just enough for a technical reviewer to see it's real.
• Draft the summit workshop proposal. Title, description, learning outcomes, format. Ready to submit when the call for presenters opens in May.

Deliverable: Narrative overview + architecture summary + draft workshop proposal.

Week 4 (Apr 7–17): Record & Package

• Record the walkthrough. Screen recording with narration walking through the demo scenario. Aim for 5–10 minutes. Can double as a grant application artifact.
• Package supporting materials. README refresh, a landing section on GitHub, links to the narrative doc and architecture diagram.
• Phase 2 retro. What's solid, what's still rough, what Phase 3 should tackle.

Deliverable: Recorded demo + public-facing README + workshop proposal ready to submit.

Risks