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

Abierto
#159 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
electron, markdown, typescript
Área
ai, backend, databases

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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).

Lenguaje dominante
TypeScript
Estrellas
3
Forks
0
Merge medio
17 h 33 min
PR fusionados (30 d)
163

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de musterhq/muster-code

Todos los issues de musterhq/muster-code

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.