LearningRecord, MemoryProposal, and SkillProposal
Jarvis records human, agent, and pair learning. MemoryProposal and SkillProposal keep future behavior changes attributable, reviewed, and bounded.
LearningRecord records what improved because of the WorkSession or an accepted OutcomeReport.
id, work_session_id, created_by_actor_id, subject_type, subject_ref, lesson_type, source_event_refs, review_state, scope, created_at
human, agent, and pair. Learning belongs to the worker or team that actually learned.
MemoryProposal records a proposed durable memory change. It does not silently write memory.
MemoryProposal required fields are id, work_session_id, proposed_by_actor_id, proposed_for, memory_scope, memory_type, content, provenance, confidence, review_required, status, and created_at.
review_required records whether human review is required before durable memory effect.review_refs is required when status is accepted.SkillProposal records a reusable way of working, including trigger conditions, procedure, review checks, failure cases, provenance, and status.
SkillProposal required fields are id, work_session_id, proposed_by_actor_id, proposed_for, skill_scope, skill_name, trigger_conditions, procedure, review_checks, failure_cases, provenance, status, and created_at.
review_refs is required when status is accepted.LearningRecord references source events. OutcomeReport references LearningRecord without appending to a sealed WorkSession event log.
MemoryProposal and SkillProposal become durable only through governed review state.