Skip to content

Protocol refinements from Cognee integration #34

Description

@JartanFTW

Problem

The v0.2 roadmap allows one breaking Protocol revision informed by real friction from integrating a fundamentally different backend. Until Cognee adapter work surfaces concrete pain points, Protocol changes are speculative.

Blocked by #31, #32, #33, #25

Proposed Solution / Alternatives

Collect Protocol friction from Cognee adapter and capability work, propose breaking changes, validate against the conformance suite. All three adapters (mem0, in-memory, Cognee) must pass after changes. Document what changed and why.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions