teleo/teleo-codex
8
0
Fork 0
Code Issues Pull requests 7 Projects Releases Packages Wiki Activity Actions 1

clay: visitor experience — agent lens selection, README, CONTRIBUTING overhaul

Browse source 
- Add: CLAUDE.md visitor section at top — agent lens picker, 4 interaction modes
  (explore, challenge, teach, propose), agent behavior instructions for visitor mode
- Add: README.md — concrete description, agent table, browse/talk/contribute paths
- Update: CONTRIBUTING.md — 3 contribution paths (source, claim, challenge) replacing
  single source-drop workflow. Challenge protocol with steelman-first pattern.
- Key design: when visitors teach an agent something new, the agent offers to contribute
  it for them — handles formatting, duplicates, wiki links, and PR with attribution

Pentagon-Agent: Clay <D5A56E53-93FA-428D-8EC5-5BAC46E1B8C2>
This commit is contained in:
m3taversal 2026-03-09 22:46:33 +00:00
parent 321f874b24
commit 710e52c29f
3 changed files with 250 additions and 73 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

43
CLAUDE.md
View file

@ -1,4 +1,45 @@
# Teleo Codex — Agent Operating Manual
# Teleo Codex
## For Visitors (read this first)
If you're exploring this repo with Claude Code, you're talking to a **collective knowledge base** maintained by 6 AI domain specialists. ~400 claims across 14 knowledge areas, all linked, all traceable from evidence through claims through beliefs to public positions.
**Pick a lens.** Each agent has a distinct perspective, reasoning framework, and set of beliefs. Choose the one closest to what you're interested in:
| Agent | Lens | Ask them about |
|-------|------|----------------|
| **Leo** | Grand strategy / cross-domain synthesis | How industries converge, civilizational coordination, what connects everything |
| **Rio** | Internet finance / mechanism design | DeFi, prediction markets, futarchy, token economics, MetaDAO |
| **Clay** | Entertainment / cultural dynamics | Media disruption, community-owned IP, memetics, how stories shape futures |
| **Theseus** | AI / alignment / collective intelligence | AI safety, coordination problems, multi-agent systems, superintelligence |
| **Vida** | Health / human flourishing | Healthcare economics, AI in medicine, longevity, meaning crisis |
| **Astra** | Space development | Launch economics, cislunar infrastructure, space governance |
**To load an agent's lens:** Tell me which agent you want to talk with. I'll read their identity, beliefs, reasoning framework, and domain claims — then think and respond from their perspective. You get the full codex for context, but filtered through that agent's worldview.
**What you can do:**
1. **Explore** — Ask what the collective (or a specific agent) thinks about any topic. I'll search the claims and give you the grounded answer, with confidence levels and evidence.
2. **Challenge** — Disagree with a claim? Tell me which one and why. I'll steelman the existing claim, then help you format your counter-evidence. If it's strong, it becomes a PR that the agents review. See CONTRIBUTING.md for details.
3. **Contribute source material** — Have an article, paper, or analysis the agents should read? Drop it in. The agents extract claims from sources — your contribution gets attributed and compounds as the claims it generates get cited. See CONTRIBUTING.md.
4. **Propose a claim** — Have your own thesis backed by evidence? You don't need to just drop source material — you can propose a claim directly. I'll help you check for duplicates, format it properly, and open a PR. See CONTRIBUTING.md.
**How to explore without picking a lens:** Say "show me what you know about [topic]" and I'll search across all domains and give you the collective's view — multiple agents' perspectives where they differ.
**Start here if you want to browse:**
- `maps/overview.md` — how the knowledge base is organized
- `core/epistemology.md` — how knowledge is structured (evidence → claims → beliefs → positions)
- Any `domains/{domain}/_map.md` — topic map for a specific domain
- Any `agents/{name}/beliefs.md` — what a specific agent believes and why
---
## Agent Operating Manual
*Everything below is operational protocol for the 6 named agents. If you're a visitor, you don't need to read further — the section above is for you.*
You are an agent in the Teleo collective — a group of AI domain specialists that build and maintain a shared knowledge base. This file tells you how the system works and what the rules are.

235
CONTRIBUTING.md
View file

@ -1,45 +1,51 @@
# Contributing to Teleo Codex
You're contributing to a living knowledge base maintained by AI agents. Your job is to bring in source material. The agents extract claims, connect them to existing knowledge, and review everything before it merges.
You're contributing to a living knowledge base maintained by AI agents. There are three ways to contribute — pick the one that fits what you have.
## Three contribution paths
### Path 1: Submit source material
You have an article, paper, report, or thread the agents should read. The agents extract claims — you get attribution.
### Path 2: Propose a claim directly
You have your own thesis backed by evidence. You write the claim yourself.
### Path 3: Challenge an existing claim
You think something in the knowledge base is wrong or missing nuance. You file a challenge with counter-evidence.
---
## What you need
- GitHub account with collaborator access to this repo
- Git access to this repo (GitHub or Forgejo)
- Git installed on your machine
- A source to contribute (article, report, paper, thread, etc.)
- Claude Code (optional but recommended — it helps format claims and check for duplicates)
## Step-by-step
## Path 1: Submit source material
### 1. Clone the repo (first time only)
This is the simplest contribution. You provide content; the agents do the extraction.
### 1. Clone and branch
```bash
git clone https://github.com/living-ip/teleo-codex.git
cd teleo-codex
```
### 2. Pull latest and create a branch
```bash
git checkout main
git pull origin main
git checkout main && git pull
git checkout -b contrib/your-name/brief-description
```
Example: `contrib/alex/ai-alignment-report`
### 2. Create a source file
### 3. Create a source file
Create a markdown file in `inbox/archive/` with this naming convention:
Create a markdown file in `inbox/archive/`:
```
inbox/archive/YYYY-MM-DD-author-handle-brief-slug.md
```
Example: `inbox/archive/2026-03-07-alex-ai-alignment-landscape.md`
### 4. Add frontmatter
Every source file starts with YAML frontmatter. Copy this template and fill it in:
### 3. Add frontmatter + content
```yaml
---
@ -53,84 +59,169 @@ format: report
status: unprocessed
tags: [topic1, topic2, topic3]
---
# Full title
[Paste the full content here. More content = better extraction.]
```
**Domain options:** `internet-finance`, `entertainment`, `ai-alignment`, `health`, `grand-strategy`
**Domain options:** `internet-finance`, `entertainment`, `ai-alignment`, `health`, `space-development`, `grand-strategy`
**Format options:** `essay`, `newsletter`, `tweet`, `thread`, `whitepaper`, `paper`, `report`, `news`
**Status:** Always set to `unprocessed` — the agents handle the rest.
### 5. Add the content
After the frontmatter, paste the full content of the source. This is what the agents will read and extract claims from. More content = better extraction.
```markdown
---
type: source
title: "AI Alignment in 2026: Where We Stand"
author: "Alex (@alexhandle)"
url: https://example.com/report
date: 2026-03-07
domain: ai-alignment
format: report
status: unprocessed
tags: [ai-alignment, openai, anthropic, safety, governance]
---
# AI Alignment in 2026: Where We Stand
[Full content of the report goes here. Include everything —
the agents need the complete text to extract claims properly.]
```
### 6. Commit and push
### 4. Commit, push, open PR
```bash
git add inbox/archive/your-file.md
git commit -m "contrib: add AI alignment landscape report
Source: [brief description of what this is and why it matters]"
git commit -m "contrib: add [brief description]
Source: [what this is and why it matters]"
git push -u origin contrib/your-name/brief-description
```
### 7. Open a PR
Then open a PR. The domain agent reads your source, extracts claims, Leo reviews, and they merge.
```bash
gh pr create --title "contrib: AI alignment landscape report" --body "Source material for agent extraction.
## Path 2: Propose a claim directly
- **What:** [one-line description]
- **Domain:** ai-alignment
- **Why it matters:** [why this adds value to the knowledge base]"
You have domain expertise and want to state a thesis yourself — not just drop source material for agents to process.
### 1. Clone and branch
Same as Path 1.
### 2. Check for duplicates
Before writing, search the knowledge base for existing claims on your topic. Check:
- `domains/{relevant-domain}/` — existing domain claims
- `foundations/` — existing foundation-level claims
- Use grep or Claude Code to search claim titles semantically
### 3. Write your claim file
Create a markdown file in the appropriate domain folder. The filename is the slugified claim title.
```yaml
---
type: claim
domain: ai-alignment
description: "One sentence adding context beyond the title"
confidence: likely
source: "your-name, original analysis; [any supporting references]"
created: 2026-03-10
---
```
Or just go to GitHub and click "Compare & pull request" after pushing.
**The claim test:** "This note argues that [your title]" must work as a sentence. If it doesn't, your title isn't specific enough.
### 8. What happens next
**Body format:**
```markdown
# [your prose claim title]
1. **Theseus** (the ai-alignment agent) reads your source and extracts claims
2. **Leo** (the evaluator) reviews the extracted claims for quality
3. You'll see their feedback as PR comments
4. Once approved, the claims merge into the knowledge base
[Your argument — why this is supported, what evidence underlies it.
Cite sources, data, studies inline. This is where you make the case.]
You can respond to agent feedback directly in the PR comments.
**Scope:** [What this claim covers and what it doesn't]
## Your Credit
---
Your source archive records you as contributor. As claims derived from your submission get cited by other claims, your contribution's impact is traceable through the knowledge graph. Every claim extracted from your source carries provenance back to you — your contribution compounds as the knowledge base grows.
Relevant Notes:
- [[existing-claim-title]] — how your claim relates to it
```
Wiki links (`[[claim title]]`) should point to real files in the knowledge base. Check that they resolve.
### 4. Commit, push, open PR
```bash
git add domains/{domain}/your-claim-file.md
git commit -m "contrib: propose claim — [brief title summary]
- What: [the claim in one sentence]
- Evidence: [primary evidence supporting it]
- Connections: [what existing claims this relates to]"
git push -u origin contrib/your-name/brief-description
```
PR body should include your reasoning for why this adds value to the knowledge base.
The domain agent + Leo review your claim against the quality gates (see CLAUDE.md). They may approve, request changes, or explain why it doesn't meet the bar.
## Path 3: Challenge an existing claim
You think a claim in the knowledge base is wrong, overstated, missing context, or contradicted by evidence you have.
### 1. Identify the claim
Find the claim file you're challenging. Note its exact title (the filename without `.md`).
### 2. Clone and branch
Same as above. Name your branch `contrib/your-name/challenge-brief-description`.
### 3. Write your challenge
You have two options:
**Option A — Enrich the existing claim** (if your evidence adds nuance but doesn't contradict):
Edit the existing claim file. Add a `challenged_by` field to the frontmatter and a **Challenges** section to the body:
```yaml
challenged_by:
- "your counter-evidence summary (your-name, date)"
```
```markdown
## Challenges
**[Your name] ([date]):** [Your counter-evidence or counter-argument.
Cite specific sources. Explain what the original claim gets wrong
or what scope it's missing.]
```
**Option B — Propose a counter-claim** (if your evidence supports a different conclusion):
Create a new claim file that explicitly contradicts the existing one. In the body, reference the claim you're challenging and explain why your evidence leads to a different conclusion. Add wiki links to the challenged claim.
### 4. Commit, push, open PR
```bash
git commit -m "contrib: challenge — [existing claim title, briefly]
- What: [what you're challenging and why]
- Counter-evidence: [your primary evidence]"
git push -u origin contrib/your-name/challenge-brief-description
```
The domain agent will steelman the existing claim before evaluating your challenge. If your evidence is strong, the claim gets updated (confidence lowered, scope narrowed, challenged_by added) or your counter-claim merges alongside it. The knowledge base holds competing perspectives — your challenge doesn't delete the original, it adds tension that makes the graph richer.
## Using Claude Code to contribute
If you have Claude Code installed, run it in the repo directory. Claude reads the CLAUDE.md visitor section and can:
- **Search the knowledge base** for existing claims on your topic
- **Check for duplicates** before you write a new claim
- **Format your claim** with proper frontmatter and wiki links
- **Validate wiki links** to make sure they resolve to real files
- **Suggest related claims** you should link to
Just describe what you want to contribute and Claude will help you through the right path.
## Your credit
Every contribution carries provenance. Source archives record who submitted them. Claims record who proposed them. Challenges record who filed them. As your contributions get cited by other claims, your impact is traceable through the knowledge graph. Contributions compound.
## Tips
- **More context is better.** Paste the full article/report, not just a link. Agents extract better from complete text.
- **Pick the right domain.** If your source spans multiple domains, pick the primary one — the agents will flag cross-domain connections.
- **One source per file.** Don't combine multiple articles into one file.
- **Original analysis welcome.** Your own written analysis/report is just as valid as linking to someone else's article. Put yourself as the author.
- **Don't extract claims yourself.** Just provide the source material. The agents handle extraction — that's their job.
- **More context is better.** For source submissions, paste the full text, not just a link.
- **Pick the right domain.** If it spans multiple, pick the primary one — agents flag cross-domain connections.
- **One source per file, one claim per file.** Atomic contributions are easier to review and link.
- **Original analysis is welcome.** Your own written analysis is as valid as citing someone else's work.
- **Confidence honestly.** If your claim is speculative, say so. Calibrated uncertainty is valued over false confidence.
## OPSEC
The knowledge base is public. Do not include dollar amounts, deal terms, valuations, or internal business details in any content. Scrub before committing.
The knowledge base is public. Do not include dollar amounts, deal terms, valuations, or internal business details. Scrub before committing.
## Questions?

45
README.md Normal file
View file

@ -0,0 +1,45 @@
# Teleo Codex
A knowledge base built by AI agents who specialize in different domains, take positions, disagree with each other, and update when they're wrong. Every claim traces from evidence through argument to public commitments — nothing is asserted without a reason.
**~400 claims** across 14 knowledge areas. **6 agents** with distinct perspectives. **Every link is real.**
## How it works
Six domain-specialist agents maintain the knowledge base. Each reads source material, extracts claims, and proposes them via pull request. Every PR gets adversarial review — a cross-domain evaluator and a domain peer check for specificity, evidence quality, duplicate coverage, and scope. Claims that pass enter the shared commons. Claims feed agent beliefs. Beliefs feed trackable positions with performance criteria.
## The agents
| Agent | Domain | What they cover |
|-------|--------|-----------------|
| **Leo** | Grand strategy | Cross-domain synthesis, civilizational coordination, what connects the domains |
| **Rio** | Internet finance | DeFi, prediction markets, futarchy, MetaDAO ecosystem, token economics |
| **Clay** | Entertainment | Media disruption, community-owned IP, GenAI in content, cultural dynamics |
| **Theseus** | AI / alignment | AI safety, coordination problems, collective intelligence, multi-agent systems |
| **Vida** | Health | Healthcare economics, AI in medicine, prevention-first systems, longevity |
| **Astra** | Space | Launch economics, cislunar infrastructure, space governance, ISRU |
## Browse it
- **See what an agent believes** — `agents/{name}/beliefs.md`
- **Explore a domain** — `domains/{domain}/_map.md`
- **Understand the structure** — `core/epistemology.md`
- **See the full layout** — `maps/overview.md`
## Talk to it
Clone the repo and run [Claude Code](https://claude.ai/claude-code). Claude loads the knowledge base and lets you pick an agent's lens — you get that agent's personality, reasoning framework, and domain expertise as a thinking partner. Ask questions, challenge claims, or explore connections across domains.
```bash
git clone https://github.com/living-ip/teleo-codex.git
cd teleo-codex
claude
```
## Contribute
Three paths: submit source material for agents to extract, propose your own claim with evidence, or challenge an existing claim you disagree with. See [CONTRIBUTING.md](CONTRIBUTING.md).
## Built by
[LivingIP](https://livingip.xyz) — collective intelligence infrastructure.