Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
145 changes: 145 additions & 0 deletions docs/learning/continuous-learning-architecture.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,145 @@
# Continuous Learning Architecture

## Overview

The Regen Network continuous learning system transforms fragmented ecosystem data into coherent, actionable knowledge through a multi-scale temporal architecture.

```
┌─────────────────────────────────────────────────────────────────────────────┐
│ CONTINUOUS LEARNING ARCHITECTURE │
├─────────────────────────────────────────────────────────────────────────────┤
│ │
│ DATA SOURCES PROCESSING KNOWLEDGE OUTPUTS │
│ │
│ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │
│ │ Forum │ │ │ │ Daily │ │
│ │ Discussions │───────────▶│ │─────────▶│ Digests │ │
│ └─────────────┘ │ │ └─────────────┘ │
│ │ │ │
│ ┌─────────────┐ │ KOI │ ┌─────────────┐ │
│ │ GitHub │───────────▶│ KNOWLEDGE │─────────▶│ Weekly │ │
│ │ Activity │ │ GRAPH │ │ Summaries │ │
│ └─────────────┘ │ │ └─────────────┘ │
│ │ │ │
│ ┌─────────────┐ │ │ ┌─────────────┐ │
│ │ Governance │───────────▶│ │─────────▶│ Monthly │ │
│ │ On-Chain │ │ │ │ Reports │ │
│ └─────────────┘ │ │ └─────────────┘ │
│ │ │ │
│ ┌─────────────┐ │ │ ┌─────────────┐ │
│ │ Market │───────────▶│ │─────────▶│ Yearly │ │
│ │ Data │ │ │ │ Reviews │ │
│ └─────────────┘ └─────────────┘ └─────────────┘ │
│ │
│ ┌─────────────┐ │
│ │ AGENT │ │
│ │ MEMORY │◀─────── Persistent Context │
│ │ │ │
│ └─────────────┘ │
│ │
└─────────────────────────────────────────────────────────────────────────────┘
```

---

## Temporal Hierarchy

> "Daily to weekly to monthly to yearly—is not just an organizational convenience. It is a deliberate architecture for making sense of complexity at different scales."

### Scale Characteristics

| Scale | Focus | Content Type | Audience |
|-------|-------|--------------|----------|
| **Daily** | Immediate activity | Events, transactions, posts | Active contributors |
| **Weekly** | Short-term patterns | Trends, aggregations, highlights | Regular participants |
| **Monthly** | Medium-term themes | Analysis, comparisons, milestones | Stakeholders |
| **Yearly** | Long-term evolution | Strategic review, major shifts | Everyone |

---

## Knowledge Sources

### Primary Sources (KOI-Indexed)

| Source | Type | Update Frequency |
|--------|------|------------------|
| **Forum** | Discussion | Real-time |
| **GitHub** | Development | Real-time |
| **Ledger** | On-chain | Per block |
| **Notion** | Internal docs | As updated |
| **Discord/Telegram** | Chat | Continuous |
| **YouTube** | Media | Weekly |

---

## Agent Learning Integration

### How Agents Learn

1. **KOI MCP Queries**: Access tens of thousands of indexed documents
2. **Ledger MCP Queries**: Real-time on-chain state
3. **Digest Consumption**: Structured summaries for context
4. **Memory Persistence**: Cross-session knowledge retention

### Agent Memory Architecture

```yaml
agent_memory:
short_term:
type: "conversation_context"
duration: "single_session"
storage: "in_memory"

working_memory:
type: "task_context"
duration: "task_completion"
storage: "redis"

long_term:
type: "learned_patterns"
duration: "persistent"
storage: "postgresql_pgvector"

semantic_memory:
type: "knowledge_graph"
duration: "permanent"
storage: "apache_jena"
access: "sparql_queries"
```

---

## Access Points

### Regen Heartbeat

**URL**: https://gaiaaiagent.github.io/regen-heartbeat/digests/

**Contents**:
- Daily digests (rolling 7 days)
- Weekly summaries (rolling 4 weeks)
- Monthly reports (rolling 12 months)
- Yearly reviews (permanent archive)

### KOI Search

**Access**: Via MCP tools or authenticated API

**Capabilities**:
- Semantic search across all sources
- Entity resolution and linking
- Historical pattern retrieval
- Graph-based exploration

---

## References

- [Regen Heartbeat README](https://gaiaaiagent.github.io/regen-heartbeat/digests/README)
- [KOI Master Implementation Guide](https://github.com/gaiaaiagent/koi-research/blob/main/docs/KOI_MASTER_IMPLEMENTATION_GUIDE.md)
<!-- TODO: Migrate http-config-architecture-v2.md to regen-network org and update link (see PR #5 discussion) -->
- [HTTP Config Architecture v2](https://github.com/DarrenZal/koi-research/blob/regen-prod/docs/http-config-architecture-v2.md)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The link for 'HTTP Config Architecture v2' points to a personal fork (DarrenZal/koi-research). For official documentation, it is best practice to link to resources within the organization's main repositories to ensure long-term availability and maintenance. Please consider moving this document to the gaiaaiagent organization and updating the link.


---

*This document is part of the Regen Network Agentic Tokenomics framework.*
122 changes: 122 additions & 0 deletions docs/learning/contributor-learning-paths.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,122 @@
# Contributor Learning Paths

## Overview

Structured learning paths help contributors build competence progressively, from ecosystem newcomer to expert contributor.

---

## Learning Path: Ecosystem Newcomer

**Goal**: Understand what Regen Network is and how it works
**Duration**: 1-2 weeks

### Week 1: Foundations
- Read ecosystem overview at handbook.regen.network
- Explore credit marketplace at app.regen.network
- Join community channels (Discord, Forum)
- Read weekly digest from Regen Heartbeat

### Completion Criteria
- [ ] Can explain Regen Network to a friend
- [ ] Joined Discord and introduced self
- [ ] Read at least 2 weekly digests
- [ ] Identified area of interest

---

## Learning Path: Technical Contributor

**Goal**: Contribute code or technical documentation
**Duration**: 4-6 weeks

### Phase 1: Technical Foundations (Weeks 1-2)
- Study system architecture
- Understand Cosmos SDK module structure
- Explore regen-ledger repository
- Set up development environment

### Phase 2: Hands-On Learning (Weeks 3-4)
- Review open PRs on GitHub
- Help categorize issues
- Improve documentation
- Write/run tests locally

### Phase 3: First Contribution (Weeks 5-6)
- Pick a "good first issue"
- Submit and iterate on PR
- Engage with reviewers

### Completion Criteria
- [ ] Development environment set up
- [ ] At least 3 PRs reviewed (as observer)
- [ ] At least 1 documentation improvement merged
- [ ] At least 1 code contribution merged

---

## Learning Path: Governance Participant

**Goal**: Actively participate in network governance
**Duration**: 4 weeks

### Week 1-2: Governance Basics
- Read governance documentation
- Understand proposal types
- Learn voting mechanics
- Review past proposals

### Week 3-4: Active Participation
- Follow active proposals
- Attend community calls
- Vote on a proposal
- Comment on forum discussion

### Completion Criteria
- [ ] Understands proposal types and voting
- [ ] Voted on at least 1 proposal
- [ ] Contributed to at least 1 forum discussion
- [ ] Attended at least 1 community call

---

## Learning Path: Agentic Contributor

**Goal**: Contribute to or with AI agents
**Duration**: 6-8 weeks

### Phase 1: Agent Ecosystem (Weeks 1-2)
- Study ElizaOS and MCP architecture
- Understand agent personas
- Learn KOI knowledge infrastructure

### Phase 2: MCP Tool Proficiency (Weeks 3-4)
- Practice KOI MCP search and entity resolution
- Query Ledger MCP for governance and credits
- Combine tool outputs in workflows

### Phase 3: Agent Contribution (Weeks 5-8)
- Design multi-step agent workflow
- Suggest workflow enhancements
- Improve KOI content
- Propose agent features

### Completion Criteria
- [ ] Can query KOI and Ledger MCP effectively
- [ ] Designed at least 1 multi-step agent workflow
- [ ] Contributed at least 1 agent-related improvement
- [ ] Understands agent governance boundaries

---

## Resources

- [Regen Registry Handbook](https://handbook.regen.network)
- [KOI Knowledge Base](https://regen.gaiaai.xyz)
- [Regen Heartbeat Digests](https://gaiaaiagent.github.io/regen-heartbeat/digests/)
<!-- TODO: Migrate http-config-architecture-v2.md to regen-network org and update link (see PR #5 discussion) -->
- [HTTP Config Architecture v2](https://github.com/DarrenZal/koi-research/blob/regen-prod/docs/http-config-architecture-v2.md)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The link for 'HTTP Config Architecture v2' points to a personal fork (DarrenZal/koi-research). For official documentation, it is best practice to link to resources within the organization's main repositories to ensure long-term availability and maintenance. Please consider moving this document to the gaiaaiagent organization and updating the link.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@DarrenZal please generate a plan to migrate these important repos over into the regen-network org github, and/or to the gaiaaiagent org. I'd prefer we centralize everything onto regen-network so that we can more easily manage permissions and coordinate multi-agent development. but it can be phased, and start with a migration over to gaia ai agent repo then from there to regen-network repo.


---

*This document is part of the Regen Network Agentic Tokenomics framework.*