54a1866c · zzmq.dev@gmail.com/zz
Commit
54a1866c17b8be7e1d469ab6d0d8c45624d07032
Replace parent/child Lane terminology with origin/related_lanes Lanes are peer workstreams, not a strict tree, per clarified design: - origin: the single Lane that created this one and that it rolls up into (by merge, or by rung rollup when there's no direct merge path). - related_lanes: every Lane descended from it at any depth (not just immediate decomposition), each carrying its own origin so structure is reconstructable from any single Lane's record. Propagated upward by each Coordinator reporting to its own origin's Coordinator. Updated the data-format schema and examples, and every parent/child mention across lanes-and-ladders, protocol, nouns, and competition-plan. Left architecture.md's "parent Maintainer" alone, a distinct Durable Object spawning relationship, not this Lane-to-Lane one. Also renamed the Insight JSON field from "tag" to "kind" per request. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Troy Howard <thoward37@gmail.com> -- 2026-10-07T10:16:19.000Z