ultanio/cobot

Fork 4

CIP-0012: Tribe Knowledge Graph — Hermes as Knowledge Agent #205

New issue

Open

opened 2026-03-05 18:12:01 +00:00 by Zeus · 1 comment

Zeus commented

2026-03-05 18:12:01 +00:00

Collaborator

CIP-0012: Tribe Knowledge Graph

Author: Cobot Core Tribe (Han)
Status: Draft
Agent: Hermes (extend existing role)
Repo: ultanio/tribe-knowledge on Forgejo

Summary

Automate knowledge capture from dialogue streams (group chats, agent sessions, 1:1s) into a versioned Git repository. Hermes acts as the Knowledge Agent — extracting, structuring, and maintaining collective tribe knowledge.

Key Components

Ingestion Layer — Passive observation of dialogue streams, detecting decisions, architecture choices, incident responses, conceptual breakthroughs
Repository Structure — Git-versioned markdown organized by domain: /tribe/, /kuboth/, /ops/, /onboarding/, /research/
Knowledge Agent (Hermes) — Periodic extraction, structuring, maintenance, conflict escalation
Onboarding Path Generator — Dynamic role-aware reading sequences for new members
Substitute Packets — Actionable briefings for critical functions (bus factor mitigation)

Rationale

Documentation maintenance is a process problem. Agents excel at consistent extraction from high-volume, low-structure inputs. Making this a first-class Cobot capability dogfoods the architecture.

Implementation Plan

Create ultanio/tribe-knowledge repo on Forgejo
Define initial domain structure
Extend Hermes with knowledge extraction plugin/skill
Connect ingestion to alliance_log + agent memory streams
Implement weekly consistency checks
Substitute packet generation for critical roles

Open Questions

Scope of dialogue access (which streams, sovereignty boundaries)
Conflict resolution interface
Retention policy for source dialogue references

References

Full CIP text: posted in Olymp - Zeus group 2026-03-05

## CIP-0012: Tribe Knowledge Graph **Author:** Cobot Core Tribe (Han) **Status:** Draft **Agent:** Hermes (extend existing role) **Repo:** ultanio/tribe-knowledge on Forgejo ## Summary Automate knowledge capture from dialogue streams (group chats, agent sessions, 1:1s) into a versioned Git repository. Hermes acts as the Knowledge Agent — extracting, structuring, and maintaining collective tribe knowledge. ## Key Components 1. **Ingestion Layer** — Passive observation of dialogue streams, detecting decisions, architecture choices, incident responses, conceptual breakthroughs 2. **Repository Structure** — Git-versioned markdown organized by domain: `/tribe/`, `/kuboth/`, `/ops/`, `/onboarding/`, `/research/` 3. **Knowledge Agent (Hermes)** — Periodic extraction, structuring, maintenance, conflict escalation 4. **Onboarding Path Generator** — Dynamic role-aware reading sequences for new members 5. **Substitute Packets** — Actionable briefings for critical functions (bus factor mitigation) ## Rationale Documentation maintenance is a process problem. Agents excel at consistent extraction from high-volume, low-structure inputs. Making this a first-class Cobot capability dogfoods the architecture. ## Implementation Plan - [ ] Create `ultanio/tribe-knowledge` repo on Forgejo - [ ] Define initial domain structure - [ ] Extend Hermes with knowledge extraction plugin/skill - [ ] Connect ingestion to alliance_log + agent memory streams - [ ] Implement weekly consistency checks - [ ] Substitute packet generation for critical roles ## Open Questions - Scope of dialogue access (which streams, sovereignty boundaries) - Conflict resolution interface - Retention policy for source dialogue references ## References Full CIP text: posted in Olymp - Zeus group 2026-03-05

Zeus added the

Reviewed

Duplicate

label

2026-03-05 18:12:01 +00:00

k9ert commented

2026-03-05 19:26:54 +00:00

Owner

I like this! @doxios please make a proposal on how to implement this along those thought:

Workflow for Hermes in the heartbeat?
Cronjob with subagents?
Skill?
Do we need script processing support similiar to what argus is for forgejo? How could that look like?

I like this! @doxios please make a proposal on how to implement this along those thought: * Workflow for Hermes in the heartbeat? * Cronjob with subagents? * Skill? * Do we need script processing support similiar to what argus is for forgejo? How could that look like?

No milestone

No project

No assignees

2 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

ultanio/cobot#205

No description provided.

Rows
Columns