Skip to content

[MAJOR] §14: KeystoneMessage struct carries orchestration concerns in transport layer #515

@mvillmow

Description

@mvillmow

Finding

Severity: MAJOR
Section: 14
Evidence: include/core/message.hpp:134 (task_id), :127 (session_id), :51 (CANCEL_TASK ActionType)
Principle: SOLID

KeystoneMessage contains task_id (for task tracking/cancellation), session_id (for context isolation), CANCEL_TASK and TASK_FAILED action types, and a metadata map. These are orchestration concerns. For a library documented as a 'pure transport layer', the message protocol is contaminated with application-level semantics that belong in ProjectAgamemnon.


Part of #504

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions