Org knowledge: subtree-scoped policies and linked knowledge folders (Obsidian or Markdown) with citations

Open
#159 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
electron, markdown, typescript
Domain
ai, backend, databases

Research direction

Start by reading the related issues #117, #133, #126 and #38, then locate the org-node policy, knowledge indexing, and Hindsight recall entry points. The issue specifies no file paths or tests, so first map those areas before estimating the work. Done means policies inherit to agents below a node, recall cites folder paths and headings, edits re-index within one minute, and access is scoped per role bank.

Written by the indexing model from the issue text.

Description

area:memory area:projects needs-triage p1 type:feature

Part of #117 · beat-Paperclip spec id E9

  • Priority: p1
  • Labels: type:feature, area:memory, area:projects
  • Relates to: #117 (#133, #126), #38
  • Scope: Paperclip's #2 most-requested feature (#1858, #7545, #2789; PRs #1978 and #461 closed) is still ⚪ on its roadmap. Muster adds:
    • policies attached to an org node, which apply to every agent below it
    • knowledge folders (a local Obsidian vault or a repo docs/), indexed into Hindsight with citations
    • "Who knows this?" answers that cite folder paths
  • Acceptance:
    • A policy set on the CTO applies to 5 engineers with no duplication.
    • Recall cites file path and heading.
    • Folder edits re-index within 1 minute.
    • Access is scoped per role bank.

Source: Paperclip issue/discussion research (docs, GitHub issues, live instance).

Dominant language
TypeScript
Stars
3
Forks
0
Avg merge
17h 33m
Merged PRs (30d)
163

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from musterhq/muster-code

All issues in musterhq/muster-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.