Skip to content

refactor: move training capture out of mneme into turn orchestrator #3175

@forkwright

Description

@forkwright

Training capture is a pipeline tap (side-effect observer on the turn loop), not a memory operation. Placing it in mneme couples I need memory to I might emit training data for every consumer. The natural home is the turn orchestrator (nous), with mneme only owning the TrainingRecord type. Medium priority -- affects architecture clarity but not correctness.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions