TEN-framework / TEN-framework/ten-framework
[FEATURE] [OceanDeveloperChallenge] Write Docs: Understanding Memory-Enabled Voice AI with TEN + PowerMem
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11.1k
- Forks
- 1.4k
- Avg merge
- 2d 15m
- Merged PRs (30d)
- 22
Description
Description
We’re looking for documentation-focused PRs to help developers better understand how to build voice AI with memory using TEN Framework + PowerMem.
The goal is not API reference docs, but explanatory, developer-friendly documentation that breaks down the ideas, structure, and logic behind memory-enabled voice agents.
Reference:
What to contribute
Documentation that helps answer questions like:
- Why do voice agents need memory?
- How does PowerMem fit into the TEN Framework workflow?
- What data is stored, retrieved, and updated?
- How memory changes the behavior of a voice agent over time
Suggested formats:
- Architecture overview
- Step-by-step walkthrough
- Conceptual explanation with diagrams
- Annotated code explanations
You can help developers with
- Clear, well-structured Markdown documentation
- Diagrams, examples, or pseudo-code are welcome
- Content should help developers quickly grasp the full picture
Severity
Critical
Additional Information
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the referenced example at ai_agents/agents/examples/voice-assistant-with-PowerMem and trace how memory fits into the TEN Framework workflow. Produce developer-friendly Markdown explaining the architecture, stored and retrieved data, and how memory changes voice-agent behavior; diagrams, examples, or pseudocode can support the explanation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ai, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100