Show HN: Leo – a Markdown engineering process for AI coding agents
LEO Lead Engineering Orchestrator A written engineering process for coding agents. Markdown you load instead of a one-line personality. LEO is that missing process, written into the repository as rules the agent is loaded under: A router.
- ▪LEO Lead Engineering Orchestrator A written engineering process for coding agents.
- ▪Markdown you load instead of a one-line personality.
- ▪LEO is that missing process, written into the repository as rules the agent is loaded under: A router.
Hacker News (AI / LLM) files mainly under ai. We currently carry 5,016 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/alex-zaporozhan/leo |
| Publication time | Tue, 15 Sep 2026 15:38:37 +0000 |
| Retrieval time | 2026-09-15T15:46:52.561Z |
| Last seen | 2026-09-15T15:46:52.561Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | OwgE2qTwSLBR · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
LEO Lead Engineering Orchestrator A written engineering process for coding agents. Markdown you load instead of a one-line personality. Nothing installs. In brief · Sixty-second test · What it looks like · How it works · Proof at scale · Get started · Business case · Steering the frontend · Manifesto · License In brief Coding agents fail in four repeatable ways: they forget a decision made forty messages ago and re-make it differently; they skip the expensive 20% — the empty state, the error contract, the timeout on the outgoing call — because nothing made skipping it cost anything; they report "should work now" in the same tone as a verified fact; and nothing in a single-agent chat ever tells them no.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.
Discussion
0 commentsMore from GitHub
