Fix TSV column misalignment in wire-principle journal

Author: cursoragent

journal/2026-05-10-wire-principle-and-conversations-patch.tsv

@@ -1,7 +1,7 @@
 type	typeName	facet	quality_score	quality_max	quality_level	title	content
-D	Decision			5	5	strong	New Tier-1 principle agents-need-their-own-wire articulates the load-bearing need for the L1 wire	klappy://canon/principles/agents-need-their-own-wire — Tier-1 principle naming human-as-relay as the structural failure mode that the Klappy substrate's L1 wire exists to address. Four characteristic costs named: bottleneck (operator availability gates throughput), lossy relay (each copy-paste loses fidelity), O(N²) integration burden (every agent pair needs human relay), human-shaped formats (agents forced to encode for human carrier instead of receiving agent). Architectural answer: direct addressability between agents on an open substrate. AMS named as the canonical reference implementation per substrate-stack L1 + D0020. Symmetric-participation named as the architectural shape; this principle named as the load-bearing need. Both principles work together at L1.
-D	Decision			5	5	strong	Substantive Failure Modes section names what breaks when the wire stops being a wire	Six failure modes documented with diagnoses and fixes: (1) wire becomes prose-shaped rather than agent-shaped (rendering surfaces creep into wire); (2) wire access becomes a permission gate (openness erodes); (3) agents on wire produce noise that re-creates operator-as-filter problem; (4) multi-agent coordination produces compounding errors at machine speed (canon discipline above the wire becomes more necessary, not less, once it exists); (5) the wire becomes opinionated about what an outcome means (vodka-architecture violation); (6) some workflows still legitimately need human in relay path (high-stakes, regulated, training contexts) and the principle does not prescribe wire-only collaboration. Diagnosis pattern: when wire stays narrow and primitive, principle holds; when it accumulates opinions/gates/surfaces/special-cases, it stops being the answer.
-D	Decision			5	5	strong	Mode-separated-conversations patched to reflect five modes plus parallelism plus override plus handoff insufficiency	docs/appendices/mode-separated-conversations.md updated: (1) frontmatter date bumped to 2026-05-10, epoch E0008.5, tags expanded to include exploration, resolution, session-discipline; (2) Relationship to Canon updated to reference epistemic-modes, sessions-mirror-modes, encoded-handoff constraint; (3) The Core Insight expanded to name five mode-collapse anti-patterns; (4) new Exploration Conversations section (was missing); (5) new Resolution Conversations section (fifth mode); (6) new Multiple Participants section operationalizing the parallelism patterns; (7) new Operator Override section operationalizing the constraint's override provision in conversational form; (8) new Handoff Insufficiency section operationalizing the runtime feature in conversational form; (9) Mode Signaling examples extended with resolution; (10) Reversion and Final Note preserved.
-L	Learning			5	5	strong	The principle and the architectural shape together specify L1	Symmetric-participation already exists at Tier-1 and describes how the wire must look to stay open: every peer treated identically, no peer-type privilege, identity/capability conveyed through metadata above the wire. What was missing: the load-bearing why. Why does this wire need to exist at all? The agents-need-their-own-wire principle fills that gap. Read together at L1: agents-need-their-own-wire = the need; symmetric-participation = the shape that satisfies the need without crowding out the ecosystem. Either principle without the other is incomplete. Together they form L1's full rationale.
-L	Learning			5	5	strong	Existing klappy.dev canon already had three pieces of the diagnosis	Search-before-claiming surfaced: (1) writings/copy-paste — the lived experience essay (clipboard convergence as job description); (2) writings/shifting-bottlenecks-climbing-ladders — the bottleneck-migration framework where this principle slots in; (3) docs/planning/oddkit-write-access — practical evidence ("the single largest source of friction in the current workflow is the human carrying files between conversations"). Plus discernment-layer (where human's load-bearing work moves to once relay is gone) and substrate-stack/L1 (the structural map the principle articulates the need for). The principle does not invent the diagnosis; it consolidates the architectural rationale that was implicit across these.
-H	Handoff			5	5	strong	PR scope: new Tier-1 principle agents-need-their-own-wire + mode-separated-conversations patch + journal	klappy.dev branch claude/wire-principle-and-conversations-c5ab. Three file changes: (1) NEW canon/principles/agents-need-their-own-wire.md — Tier-1 principle, ~3.3kw, sibling to symmetric-participation; (2) MODIFIED docs/appendices/mode-separated-conversations.md — added Exploration and Resolution conversation types plus Multiple Participants, Operator Override, and Handoff Insufficiency pointer sections; (3) NEW journal/2026-05-10-wire-principle-and-conversations-patch.tsv. Concurrent with PR #187 and PR #188; no dependency between any of them. Sibling/follow-up work flagged: governance-validation-via-agents rename (vendor-naming smell — same as audit-gates was); use-case catalogue method-doc once 3-5 worked multi-agent applications exist; conversational-mode-orchestration consumer-pattern doc once a working orchestrator exists.
+D	Decision		5	5	strong	New Tier-1 principle agents-need-their-own-wire articulates the load-bearing need for the L1 wire	klappy://canon/principles/agents-need-their-own-wire — Tier-1 principle naming human-as-relay as the structural failure mode that the Klappy substrate's L1 wire exists to address. Four characteristic costs named: bottleneck (operator availability gates throughput), lossy relay (each copy-paste loses fidelity), O(N²) integration burden (every agent pair needs human relay), human-shaped formats (agents forced to encode for human carrier instead of receiving agent). Architectural answer: direct addressability between agents on an open substrate. AMS named as the canonical reference implementation per substrate-stack L1 + D0020. Symmetric-participation named as the architectural shape; this principle named as the load-bearing need. Both principles work together at L1.
+D	Decision		5	5	strong	Substantive Failure Modes section names what breaks when the wire stops being a wire	Six failure modes documented with diagnoses and fixes: (1) wire becomes prose-shaped rather than agent-shaped (rendering surfaces creep into wire); (2) wire access becomes a permission gate (openness erodes); (3) agents on wire produce noise that re-creates operator-as-filter problem; (4) multi-agent coordination produces compounding errors at machine speed (canon discipline above the wire becomes more necessary, not less, once it exists); (5) the wire becomes opinionated about what an outcome means (vodka-architecture violation); (6) some workflows still legitimately need human in relay path (high-stakes, regulated, training contexts) and the principle does not prescribe wire-only collaboration. Diagnosis pattern: when wire stays narrow and primitive, principle holds; when it accumulates opinions/gates/surfaces/special-cases, it stops being the answer.
+D	Decision		5	5	strong	Mode-separated-conversations patched to reflect five modes plus parallelism plus override plus handoff insufficiency	docs/appendices/mode-separated-conversations.md updated: (1) frontmatter date bumped to 2026-05-10, epoch E0008.5, tags expanded to include exploration, resolution, session-discipline; (2) Relationship to Canon updated to reference epistemic-modes, sessions-mirror-modes, encoded-handoff constraint; (3) The Core Insight expanded to name five mode-collapse anti-patterns; (4) new Exploration Conversations section (was missing); (5) new Resolution Conversations section (fifth mode); (6) new Multiple Participants section operationalizing the parallelism patterns; (7) new Operator Override section operationalizing the constraint's override provision in conversational form; (8) new Handoff Insufficiency section operationalizing the runtime feature in conversational form; (9) Mode Signaling examples extended with resolution; (10) Reversion and Final Note preserved.
+L	Learning		5	5	strong	The principle and the architectural shape together specify L1	Symmetric-participation already exists at Tier-1 and describes how the wire must look to stay open: every peer treated identically, no peer-type privilege, identity/capability conveyed through metadata above the wire. What was missing: the load-bearing why. Why does this wire need to exist at all? The agents-need-their-own-wire principle fills that gap. Read together at L1: agents-need-their-own-wire = the need; symmetric-participation = the shape that satisfies the need without crowding out the ecosystem. Either principle without the other is incomplete. Together they form L1's full rationale.
+L	Learning		5	5	strong	Existing klappy.dev canon already had three pieces of the diagnosis	Search-before-claiming surfaced: (1) writings/copy-paste — the lived experience essay (clipboard convergence as job description); (2) writings/shifting-bottlenecks-climbing-ladders — the bottleneck-migration framework where this principle slots in; (3) docs/planning/oddkit-write-access — practical evidence ("the single largest source of friction in the current workflow is the human carrying files between conversations"). Plus discernment-layer (where human's load-bearing work moves to once relay is gone) and substrate-stack/L1 (the structural map the principle articulates the need for). The principle does not invent the diagnosis; it consolidates the architectural rationale that was implicit across these.
+H	Handoff		5	5	strong	PR scope: new Tier-1 principle agents-need-their-own-wire + mode-separated-conversations patch + journal	klappy.dev branch claude/wire-principle-and-conversations-c5ab. Three file changes: (1) NEW canon/principles/agents-need-their-own-wire.md — Tier-1 principle, ~3.3kw, sibling to symmetric-participation; (2) MODIFIED docs/appendices/mode-separated-conversations.md — added Exploration and Resolution conversation types plus Multiple Participants, Operator Override, and Handoff Insufficiency pointer sections; (3) NEW journal/2026-05-10-wire-principle-and-conversations-patch.tsv. Concurrent with PR #187 and PR #188; no dependency between any of them. Sibling/follow-up work flagged: governance-validation-via-agents rename (vendor-naming smell — same as audit-gates was); use-case catalogue method-doc once 3-5 worked multi-agent applications exist; conversational-mode-orchestration consumer-pattern doc once a working orchestrator exists.