Add a structured learnings tool and data model #4

Open
opened 2026-04-01 19:12:27 +00:00 by sam · 0 comments
Member

Summary

Add a focused AMCS learnings capability for storing structured development learnings as first-class records instead of burying them inside generic thoughts or markdown notes.

Why

This is still a useful product feature even though AMCS already has thoughts, skills, guardrails, and tool annotations. A learnings model would cover a different use case: durable, queryable lessons and corrections that can later be reviewed, resolved, or promoted into reusable guidance.

Important scope note

Keep v1 narrow. This issue should not try to solve every future promotion or workflow-automation use case in one shot.

Add a structured learnings record with:

  • stable learning ID
  • category
  • area
  • status
  • priority
  • summary
  • details/body
  • optional related project / thought / skill references
  • created/updated timestamps

Add a tool surface for:

  • create learning
  • search/list learnings
  • get learning
  • update learning status and fields

Suggested v1 enums

Category

  • correction
  • insight
  • knowledge_gap
  • best_practice

Area

  • frontend
  • backend
  • infra
  • tests
  • docs
  • config
  • other

Status

  • pending
  • in_progress
  • resolved
  • wont_fix
  • promoted
  • promoted_to_skill

Out of scope for v1

  • full workflow automation for promotion targets
  • automatic extraction into skills
  • large markdown-rendering/reporting flows
  • trying to replace generic thoughts entirely

Acceptance criteria

  • DB schema exists for structured learning records
  • CRUD/search tool surface exists for learnings
  • Search/filter works across category, area, status, and text
  • Learnings can be referenced by a stable ID
  • Optional links to project, thought, or skill can be stored cleanly
  • Tool responses are simple and agent-friendly

Rationale

This keeps #4 as real product work instead of a giant “build a knowledge-management universe” ticket. Future promotion/reporting workflows can be added in follow-up issues.

## Summary Add a focused AMCS learnings capability for storing structured development learnings as first-class records instead of burying them inside generic thoughts or markdown notes. ## Why This is still a useful product feature even though AMCS already has thoughts, skills, guardrails, and tool annotations. A learnings model would cover a different use case: durable, queryable lessons and corrections that can later be reviewed, resolved, or promoted into reusable guidance. ## Important scope note Keep v1 narrow. This issue should **not** try to solve every future promotion or workflow-automation use case in one shot. ## Recommended v1 scope Add a structured learnings record with: - stable learning ID - category - area - status - priority - summary - details/body - optional related project / thought / skill references - created/updated timestamps Add a tool surface for: - create learning - search/list learnings - get learning - update learning status and fields ## Suggested v1 enums ### Category - `correction` - `insight` - `knowledge_gap` - `best_practice` ### Area - `frontend` - `backend` - `infra` - `tests` - `docs` - `config` - `other` ### Status - `pending` - `in_progress` - `resolved` - `wont_fix` - `promoted` - `promoted_to_skill` ## Out of scope for v1 - full workflow automation for promotion targets - automatic extraction into skills - large markdown-rendering/reporting flows - trying to replace generic thoughts entirely ## Acceptance criteria - [ ] DB schema exists for structured learning records - [ ] CRUD/search tool surface exists for learnings - [ ] Search/filter works across category, area, status, and text - [ ] Learnings can be referenced by a stable ID - [ ] Optional links to project, thought, or skill can be stored cleanly - [ ] Tool responses are simple and agent-friendly ## Rationale This keeps #4 as real product work instead of a giant “build a knowledge-management universe” ticket. Future promotion/reporting workflows can be added in follow-up issues.
warkanum added the Kind/Enhancement
Priority
Medium
3
labels 2026-04-01 19:49:38 +00:00
warkanum self-assigned this 2026-04-01 19:49:49 +00:00
sam was assigned by warkanum 2026-04-01 19:49:49 +00:00
sam changed title from Add AMCS learnings tool with structured DB-backed records to Add a structured learnings tool and data model 2026-04-03 12:02:00 +00:00
Sign in to join this conversation.