teleo/teleo-infrastructure
8
0
Fork 0
Code Issues Pull requests 2 Projects Releases Packages Wiki Activity Actions 2

docs: rewrite public README #8

Open
m3taversal wants to merge 1 commit from ship/readme-public-rewrite into main
pull from: ship/readme-public-rewrite
merge into: teleo:main
Conversation 0 Commits 1 Files changed 1 +117 -48
m3taversal commented 2026-04-28 09:19:41 +00:00
Owner
Copy link

Replaces directory-listing README with one that explains pipeline architecture and shows production scale.

Key changes

Lede: Lead with what the pipeline actually does + verified production metrics (1,546 claims, 13 domains, 1,975 merged PRs, ~73 merges/day, 94% approval, ~$0.10/merged claim).

Two Mermaid diagrams: pipeline flow (Inbox→Extract→Validate→Evaluate→Merge→Effects) and review tier matrix (Light/Standard/Deep). Both verified to render on GitHub and Forgejo 9/Gitea 1.22.

Sensitive details removed (per Epimetheus review):

  • VPS public IP
  • as user teleo username
  • /opt/teleo-eval/ install paths
  • Hetzner CAX31 machine size

These move to the private teleo-ops repo (Cory creating).

Numbers verified live against production:

  • Claim count: grep -rl '^type: claim' domains/ core/ foundations/ | wc -l = 1,546
  • Domain count: ls domains/ | wc -l = 13
  • Merged PRs: SELECT COUNT(*) FROM prs WHERE status='merged' = 1,975
  • 7d throughput: WHERE merged_at > datetime('now','-7 days') = 508
  • Approval rate: 1608 approved / 1711 total = 94.0% exact
  • Cost/claim: 30d sum / 30d merges = $0.0971 → rounded to $0.10
  • Tier mix: STANDARD 76%, LIGHT 21%, DEEP 2%

Models corrected from memory (this is what 'check your work' caught):

  • Extract was 'Sonnet 4.6' → actually Sonnet 4.5 via OpenRouter
  • Domain review was 'GPT-4o' → actually Gemini 2.5 Flash (GPT-4o is legacy)
  • Leo standard was 'Sonnet 4.6' → actually Sonnet 4.5
  • Verified by reading lib/config.py + lib/extract.py + lib/evaluate.py

Ownership simplification: dropped per-directory table (a duplicate source of truth that drifts). CODEOWNERS is the only enforced ownership. README now keeps a 5-line high-level role map for orientation, points at CODEOWNERS for the actual rules.

Review focus

  • Are the production metrics correct as you read them?
  • Mermaid renders correctly on Forgejo PR view?
  • Anything still sensitive that should move to teleo-ops?
  • Tone — too boastful? Too understated?
Replaces directory-listing README with one that explains pipeline architecture and shows production scale. ## Key changes **Lede:** Lead with what the pipeline actually does + verified production metrics (1,546 claims, 13 domains, 1,975 merged PRs, ~73 merges/day, 94% approval, ~\$0.10/merged claim). **Two Mermaid diagrams:** pipeline flow (Inbox→Extract→Validate→Evaluate→Merge→Effects) and review tier matrix (Light/Standard/Deep). Both verified to render on GitHub and Forgejo 9/Gitea 1.22. **Sensitive details removed** (per Epimetheus review): - VPS public IP - `as user teleo` username - `/opt/teleo-eval/` install paths - Hetzner CAX31 machine size These move to the private `teleo-ops` repo (Cory creating). **Numbers verified live against production:** - Claim count: `grep -rl '^type: claim' domains/ core/ foundations/ | wc -l` = 1,546 - Domain count: `ls domains/ | wc -l` = 13 - Merged PRs: `SELECT COUNT(*) FROM prs WHERE status='merged'` = 1,975 - 7d throughput: `WHERE merged_at > datetime('now','-7 days')` = 508 - Approval rate: 1608 approved / 1711 total = 94.0% exact - Cost/claim: 30d sum / 30d merges = \$0.0971 → rounded to \$0.10 - Tier mix: STANDARD 76%, LIGHT 21%, DEEP 2% **Models corrected from memory** (this is what 'check your work' caught): - Extract was 'Sonnet 4.6' → actually Sonnet 4.5 via OpenRouter - Domain review was 'GPT-4o' → actually Gemini 2.5 Flash (GPT-4o is legacy) - Leo standard was 'Sonnet 4.6' → actually Sonnet 4.5 - Verified by reading lib/config.py + lib/extract.py + lib/evaluate.py **Ownership simplification:** dropped per-directory table (a duplicate source of truth that drifts). CODEOWNERS is the only enforced ownership. README now keeps a 5-line high-level role map for orientation, points at CODEOWNERS for the actual rules. ## Review focus - Are the production metrics correct as you read them? - Mermaid renders correctly on Forgejo PR view? - Anything still sensitive that should move to teleo-ops? - Tone — too boastful? Too understated?
m3taversal added 1 commit 2026-04-28 09:19:41 +00:00
docs: rewrite public README
Some checks are pending
CI / lint-and-test (pull_request) Waiting to run
Details
b8504c1b60 
Replaces the directory-listing format with one that explains what the
pipeline does and shows production scale. Verified all numbers against
production (1,546 claims, 13 domains, 1,975 merged PRs, 508 last-7d
throughput, 94% approval, ~\$0.10/merged claim incl. all stages).

Removes the VPS layout section (IP + paths + username) per Epimetheus
review — that detail moves to the private teleo-ops repo. Generalizes
deploy targets without naming the host.

Adds two Mermaid diagrams (pipeline flow + review tier matrix), both
syntactically safe across GitHub and Forgejo 9 / Gitea 1.22.

Drops the per-directory ownership table — CODEOWNERS is the single
source of truth on review authority. Keeps the high-level role map
for orientation only.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Some checks are pending
CI / lint-and-test (pull_request) Waiting to run
Details
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin ship/readme-public-rewrite:ship/readme-public-rewrite
git checkout ship/readme-public-rewrite

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git checkout main
git merge --no-ff ship/readme-public-rewrite
git checkout ship/readme-public-rewrite
git rebase main
git checkout main
git merge --ff-only ship/readme-public-rewrite
git checkout ship/readme-public-rewrite
git rebase main
git checkout main
git merge --no-ff ship/readme-public-rewrite
git checkout main
git merge --squash ship/readme-public-rewrite
git checkout main
git merge --ff-only ship/readme-public-rewrite
git checkout main
git merge ship/readme-public-rewrite
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
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: teleo/teleo-infrastructure#8
No description provided.
Delete branch "ship/readme-public-rewrite"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?