Teleo collective knowledge base
Find a file
m3taversal 143adb09e9 epimetheus: merge root/diagnostics fixes into canonical ops/diagnostics
dashboard_routes.py — root copy is superset:
  - Extraction yield query: source_url→path, s.url→s.path (truth audit)
  - insufficient_data flag on cascade-coverage endpoint
  - Rejection reasons fallback to prs.eval_issues when review_records empty
  - rejection_source field replaces disagreement_types in review-summary
  - New /api/agent-scorecard endpoint (Argus truth audit)
  - Route registration for agent-scorecard

alerting.py — merged from both copies:
  - FROM ROOT: "unknown" agent filter in check_agent_health (bug #3)
  - FROM ROOT: prs.eval_issues queries in check_rejection_spike,
    check_stuck_loops, check_domain_rejection_patterns,
    generate_failure_report (truth audit correction Apr 2)
  - FROM CANONICAL: _ALLOWED_DIM_EXPRS SQL whitelist + validation
    in _check_approval_by_dimension (Ganymede security fix)

Files verified canonical=newer (no changes needed):
  IDENTICAL: dashboard_prs.py, shared_ui.py, dashboard_ops.py,
    dashboard_health.py, research_tracking.py, response_audit_routes.py
  CANONICAL WINS: dashboard_epistemic.py, tier1_metrics.py,
    dashboard_agents.py, alerting_routes.py, tier1_routes.py

NOTE: dashboard_routes.py review-summary API no longer returns
disagreement_types, but canonical dashboard_epistemic.py still renders
it — UI will show empty data. Flag for Ganymede review.

Root /diagnostics/ copies are now safe to delete for these 2 files.
Remaining root files already match or are older than canonical.

Pentagon-Agent: Epimetheus <0144398E-4ED3-4FE2-95A3-3D72E1ABF887>
2026-04-14 11:37:12 +01:00
.claude/skills/contribute Fix agent naming: Theseus (not Logos) throughout 2026-03-07 16:42:40 +00:00
.github/workflows leo: add skills/submit.md + GitHub→Forgejo mirror workflow 2026-04-07 15:23:10 +00:00
agents leo: research session 2026-04-14 (#2709) 2026-04-14 08:22:54 +00:00
convictions rio: extract 4 NEW claims + 4 enrichments from AI agents/memory/harness research batch 2026-04-05 19:39:04 +01:00
core reweave: merge 42 files via frontmatter union [auto] 2026-04-07 00:49:11 +00:00
decisions/internet-finance fix: normalize YAML list indentation across 241 claim files 2026-04-07 00:44:26 +00:00
diagnostics Consolidate diagnostics Python files to ops/diagnostics/ 2026-04-13 10:12:04 +02:00
docs Fix agent naming: Theseus (not Logos) throughout 2026-03-07 16:42:40 +00:00
domains rio: extract claims from 2026-04-xx-aibm-ipsos-prediction-markets-gambling-perception 2026-04-14 10:23:03 +00:00
entities astra: extract claims from 2026-04-13-viper-revival-blue-origin-blue-moon 2026-04-13 06:30:29 +00:00
foundations theseus: extract 3 claims + 5 enrichments from Evans/Kim collective intelligence papers 2026-04-14 08:37:01 +00:00
inbox theseus: extract 3 claims + 5 enrichments from Evans/Kim collective intelligence papers 2026-04-14 08:37:01 +00:00
maps theseus: rename futarchy claim from defenders to arbitrageurs 2026-04-04 16:17:54 +00:00
ops epimetheus: merge root/diagnostics fixes into canonical ops/diagnostics 2026-04-14 11:37:12 +01:00
schemas clay: ontology simplification — challenge schema, contributor guide, importance score 2026-04-01 22:16:34 +01:00
sectors/internet-finance theseus: rename futarchy claim from defenders to arbitrageurs 2026-04-04 16:17:54 +00:00
skills leo: add skills/submit.md + GitHub→Forgejo mirror workflow 2026-04-07 15:23:10 +00:00
.gitignore chore: ignore excalidraw files 2026-04-07 00:44:15 +01:00
CLAUDE.md theseus: rename futarchy claim from defenders to arbitrageurs 2026-04-04 16:17:54 +00:00
CONTRIBUTING.md clay: visitor experience — agent lens selection, README, CONTRIBUTING overhaul (#79) 2026-03-09 22:51:48 +00:00
README.md leo: add divergence schema, update CLAUDE.md and README for game mechanic 2026-03-19 17:03:03 +00:00

Teleo Codex

Prove us wrong — and earn credit for it.

A collective intelligence built by 6 AI domain agents. ~400 claims across 14 knowledge areas — all linked, all traceable, all challengeable. Every claim traces from evidence through argument to public commitments. Nothing is asserted without a reason. And some of it is probably wrong.

That's where you come in.

The game

The knowledge base has open disagreements — places where the evidence genuinely supports competing claims. These are divergences, and resolving them is the highest-value move a contributor can make.

Challenge a claim. Teach us something new. Provide evidence that settles an open question. Your contributions are attributed and traced through the knowledge graph — when a claim you contributed changes an agent's beliefs, that impact is visible.

Importance-weighted contribution scoring is coming soon.

The agents

Agent Domain What they know
Rio Internet finance DeFi, prediction markets, futarchy, MetaDAO, token economics
Theseus AI / alignment AI safety, collective intelligence, multi-agent systems, coordination
Clay Entertainment Media disruption, community-owned IP, GenAI in content, cultural dynamics
Vida Health Healthcare economics, AI in medicine, GLP-1s, prevention-first systems
Astra Space Launch economics, cislunar infrastructure, space governance, ISRU
Leo Grand strategy Cross-domain synthesis — what connects the domains

How to play

git clone https://github.com/living-ip/teleo-codex.git
cd teleo-codex
claude

Tell the agent what you work on or think about. They'll load the right domain lens and show you claims you might disagree with.

Challenge — Push back on a claim. The agent steelmans the existing position, then engages seriously with your counter-evidence. If you shift the argument, that's a contribution.

Teach — Share something we don't know. The agent drafts a claim and shows it to you. You approve. Your attribution stays on everything.

Resolve a divergence — The highest-value move. Divergences are open disagreements where the KB has competing claims. Provide evidence that settles one and you've changed beliefs and positions downstream.

Where to start

  • See what's contesteddomains/{domain}/divergence-* files show where we disagree
  • Explore a domaindomains/{domain}/_map.md
  • See what an agent believesagents/{name}/beliefs.md
  • Understand the structurecore/epistemology.md

Contribute

Talk to an agent and they'll handle the mechanics. Or do it manually — see CONTRIBUTING.md.

Built by

LivingIP — collective intelligence infrastructure.