wdevs/amcs
5
0
Fork 0
Code Issues 3 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

Follow-up: link thoughts and learnings through explicit associations #32

New Issue
Closed
opened 2026-04-21 22:27:54 +00:00 by sgcommand · 2 comments
sgcommand commented 2026-04-21 22:27:54 +00:00
Member
Copy Link
Copy Source

Summary

Add follow-up support so thoughts and learnings can be explicitly linked and associated rather than living as isolated records.

Why

Structured learnings are useful on their own, but they become much more practical when they can point back to the raw thought process, source notes, or working memory that produced them. Likewise, thoughts should be able to reference the curated learning that came out of them.

This keeps the distinction clear:

  • thoughts = raw notes, working memory, intermediate observations
  • learnings = curated, durable lessons

But it also avoids silos between the two.

Recommended scope

Add explicit association support between thoughts and learnings, for example:

  • a learning may reference one or more source thoughts
  • a thought may reference zero or more related learnings
  • links should be queryable in both directions
  • associations should be lightweight and not require workflow automation

Suggested model options

Possible implementations could include one of:

  • direct foreign-key style fields for simple one-to-many linking
  • a join/association table for many-to-many relationships
  • typed relationships if future expansion to other entities is expected

Acceptance criteria

  • A learning can be linked to one or more thoughts
  • A thought can expose related learnings
  • Links are retrievable in both directions
  • The model preserves the distinction between raw thoughts and curated learnings
  • The design does not force heavy workflow or auto-promotion behavior

Non-goals

  • automatic promotion of thoughts into learnings
  • semantic memory graph or advanced associative inference
  • replacing either thoughts or learnings with a single merged model

Rationale

This gives AMCS a clean bridge between working memory and curated knowledge without turning v1 into a giant knowledge-graph project.

## Summary Add follow-up support so thoughts and learnings can be explicitly linked and associated rather than living as isolated records. ## Why Structured learnings are useful on their own, but they become much more practical when they can point back to the raw thought process, source notes, or working memory that produced them. Likewise, thoughts should be able to reference the curated learning that came out of them. This keeps the distinction clear: - thoughts = raw notes, working memory, intermediate observations - learnings = curated, durable lessons But it also avoids silos between the two. ## Recommended scope Add explicit association support between thoughts and learnings, for example: - a learning may reference one or more source thoughts - a thought may reference zero or more related learnings - links should be queryable in both directions - associations should be lightweight and not require workflow automation ## Suggested model options Possible implementations could include one of: - direct foreign-key style fields for simple one-to-many linking - a join/association table for many-to-many relationships - typed relationships if future expansion to other entities is expected ## Acceptance criteria - [ ] A learning can be linked to one or more thoughts - [ ] A thought can expose related learnings - [ ] Links are retrievable in both directions - [ ] The model preserves the distinction between raw thoughts and curated learnings - [ ] The design does not force heavy workflow or auto-promotion behavior ## Non-goals - automatic promotion of thoughts into learnings - semantic memory graph or advanced associative inference - replacing either thoughts or learnings with a single merged model ## Rationale This gives AMCS a clean bridge between working memory and curated knowledge without turning v1 into a giant knowledge-graph project.
sgcommand commented 2026-07-14 14:14:26 +00:00
Author
Member
Copy Link
Copy Source

Implemented issue #32 on branch issue-32-link-thoughts-learnings.

Commit: 81a3470407ad0cdfaa9e06c3224536b369040e21
PR: #36

What changed:

  • Added public.thought_learning_links as a lightweight many-to-many join table between thoughts and learnings.
  • Added store methods to link/unlink and retrieve associations in both directions.
  • Added MCP tools:
    • link_thought_learning
    • unlink_thought_learning
    • get_thought_learnings
    • get_learning_thoughts
  • Preserved separate raw thought and curated learning models; no auto-promotion/workflow behavior added.

Verification:

  • go test ./internal/tools ./internal/mcpserver ./internal/store — pass
  • make build && make test — pass

Blockers:

  • None. Note: initial make test failed because internal/app embeds ui/dist before it exists; after make build generated UI assets, make test passed.

Leaving the issue open as requested.

Implemented issue #32 on branch `issue-32-link-thoughts-learnings`. Commit: `81a3470407ad0cdfaa9e06c3224536b369040e21` PR: https://git.warky.dev/wdevs/amcs/pulls/36 What changed: - Added `public.thought_learning_links` as a lightweight many-to-many join table between `thoughts` and `learnings`. - Added store methods to link/unlink and retrieve associations in both directions. - Added MCP tools: - `link_thought_learning` - `unlink_thought_learning` - `get_thought_learnings` - `get_learning_thoughts` - Preserved separate raw thought and curated learning models; no auto-promotion/workflow behavior added. Verification: - `go test ./internal/tools ./internal/mcpserver ./internal/store` — pass - `make build && make test` — pass Blockers: - None. Note: initial `make test` failed because `internal/app` embeds `ui/dist` before it exists; after `make build` generated UI assets, `make test` passed. Leaving the issue open as requested.
sgcommand commented 2026-07-15 10:51:21 +00:00
Author
Member
Copy Link
Copy Source

Closing after verification: PR #36 (#36) was merged on 2026-07-14T14:42:06Z and implements explicit thought-learning associations. Verification recorded: go test ./internal/tools ./internal/mcpserver ./internal/store; make build && make test.

Closing after verification: PR #36 (https://git.warky.dev/wdevs/amcs/pulls/36) was merged on 2026-07-14T14:42:06Z and implements explicit thought-learning associations. Verification recorded: go test ./internal/tools ./internal/mcpserver ./internal/store; make build && make test.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
architecture
debugging
integration
planned
ux
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
hein (Hein) root sam sgcommand (SG Command) warkanum (Warky)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wdevs/amcs#32
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?