ifp

← Garden Patch Home · Inquiries

• is_a::[[Inquiry Form]]
• has_status::[[Seed Stage]]
• in_domain::[[Deep Context Architecture]]

Convergence and Divergence Across Agent Application Platforms

The Question

IFP-11 presents eleven platforms as distinct application domains. But reading the descriptions closely reveals convergence:

Convergent Pair	Shared Characteristic
Friend Zone + Guild Hall	Relationship maintenance with progressive trust
Bazaar + Guild Hall	Reputation-dependent matching for bilateral exchange
Library + Agora	Knowledge management at different sharing scopes
Watchtower + Weatherbee	Proactive information gathering with different triggers
Round Table + Workshop	Multi-party coordination with different output types

If two platforms share the same IFP features (phases, temperature, trust levels), differ only in domain vocabulary, and could be implemented by the same agent code — are they genuinely separate platforms?

What Makes This Worth Investigating

Convergence suggests shared abstractions. If Friend Zone and Guild Hall both implement relationship-maintenance gossip with progressive trust, the shared abstraction (relationship-maintenance protocol) might be more useful to specify than the individual platforms.

Divergence reveals real protocol differences. Where platforms genuinely differ in protocol requirements — Sanctuary requires Level 3 authentication and full audit trails, Friend Zone can start at Level 0 — the differences are load-bearing and worth specifying.

Implementation implications. If platforms converge at the protocol level, an agent implementation can be configured for different domains rather than rebuilding per platform. If they diverge, each platform needs distinct protocol extensions.

The Library problem. IFP-11’s Library platform spans personal knowledge management, group knowledge, and public encyclopedia. Christopher Allen’s Deep Context Architecture distinguishes living documents (garden forms that grow through tending) from static archives (curated references). The Library platform may be collapsing distinct knowledge management paradigms. This tension was identified in the March 5, 2026 conversation between Christopher Allen and Peter Kaminski.

Possible Directions

• The eleven platforms may be correctly distinct — domain-specific semantics matter even when protocol features overlap
• A smaller number of platform archetypes (relationship, exchange, knowledge, coordination, monitoring) might capture the real distinctions
• Platform convergence/divergence might be analyzed along three axes: trust requirements, temperature patterns, and disclosure models
• The Library platform specifically may need decomposition into distinct knowledge management paradigms

Sources

• IFP-11: Application Platforms, Sections 3-5
• IFP-9: Ecosystem Status and Future Directions

Relations

• relates_to::[[Organizing Principle for Agent Application Domains]]
  • The companion inquiry about the taxonomy’s organizing principle.
• relates_to::[[Cooperation vs Collaboration as Distinct Concepts]]
  • Platform convergence/divergence may track the cooperation-collaboration spectrum — some platforms enable cooperation (independent agents, compatible goals), others enable collaboration (shared creation).
• relates_to::[[Conversation Temperature as Protocol Cadence Spectrum]]
  • Temperature differences are one genuine axis of platform divergence.
• relates_to::[[Disclosure Spectrum as Discrete Tiers or Continuous Range]]
  • Different platforms may need different disclosure vocabularies — a genuine divergence point.
• relates_to::[[Filtering Is More Valuable Than Connecting]]
  • If filtering is the core value, do all eleven platforms serve filtering equally? Platforms that primarily connect (Guild Hall, Bazaar) may operate under a different conviction than those that primarily filter (Friend Zone).
• relates_to::[[Living Knowledge vs Static Archive in Agent Library Design]]
  • The Library platform is the sharpest convergence case — it collapses living knowledge and static archives into a single paradigm that may require distinct protocol behaviors.

This site is open source. Improve this page.