Vision Lock v1: AI News Aggregator -> AI Enthusiast Daily (ADR-0007)

- docs/vision/VISION_LOCK_V1.md: permanent editorial mission, audience (builders/tinkerers/
  local-AI users/home-lab/agent devs), Editorial Test ('what would an enthusiast DO?'),
  architectual constraint (editorial vision is primary system), priority order.
- docs/vision/ADR-0007_EDITORIAL_PIVOT.md: accepted pivot record, before/after table,
  Sprint 1 evidence (high-signal = actionable, low-signal = spectator content).
- docs/vision/EDITORIAL_GUIDELINES.md: operating rules; score is draft, taste overrides;
  hand-before-machine; memory must store 'what can be done' not 'what happened'.
- docs/vision/SECTION_DEFINITIONS.md: 5 sections (What Shipped / Run It Locally /
  Benchmarks & Builds / Problem Solved / Worth Trying Tonight).
- docs/vision/SPRINT_1_FINDINGS.md: reference evidence, 45/200 UNCATEGORIZED taxonomy gap.
- Issue_001.md: handcrafted prototype edition from Sprint 1 stories; benchmark for all future automation.

This is the architectural directive. No scoring/narrative/memory work proceeds except in
service of the Vision Lock. Sprint 2 (Lens) stays blocked pending manual review tallies.
This commit is contained in:
Epictetus
2026-07-15 05:08:26 +00:00
parent ed6b7475dc
commit 3a42f53333
6 changed files with 373 additions and 0 deletions
+97
View File
@@ -0,0 +1,97 @@
# Issue 001 — Prototype Edition: "If We Launched Tomorrow Morning"
**Type:** Handcrafted prototype edition
**Automation:** NONE. No new architecture. No additional scoring. Curated by hand from Sprint 1 stories (athena_review_report.txt) against the Editorial Test (VISION_LOCK_V1.md).
**Purpose:** The benchmark against which all future automation is measured. If a future pipeline can't reproduce the judgment shown here, it isn't ready.
---
## What Shipped Today
**Juggler — open-source GUI coding agent** `(id 2225, HN)`
A visual, open-source coding agent from the creator of JUCE. Install and drive it.
*Do: install it. GitHub: github.com/juggler-ai/juggler*
**Open-Source Local LLM Training Tool (consumer hardware)** `(id 2315, Reddit)`
A tool for training/fine-tuning local models on consumer GPUs.
*Do: run it on your hardware.*
**Zer0Fit — MCP server for zero-shot ML, 100% local** `(id 2427, Reddit)`
Wraps Google's TabFM/TimesFM as an MCP server for forecasts/classifications/regressions. Fully local.
*Do: wire it into your agent as an MCP tool.*
**Hundreds of arXiv papers hit daily — an open-source triage tool** `(id 2430, Reddit)`
Built because only ~3 of hundreds matter to one researcher's work.
*Do: use it to cut your own paper noise.*
---
## Run It Locally
**Quad 5060Tis benchmarked for code-gen with Qwen3.6-27B** `(id 1558, Reddit, final 0.50)`
Real numbers, consumer hardware, reproducible method.
*Do: replicate the bench on your GPU.*
**Voodoo Quant beats Unsloth Dynamic 2.0 KLD by 95% (Qwen3.5 0.8B/2B)** `(id 1977, Reddit, 0.45)`
Quantization-quality showdown with measured delta.
*Do: try Voodoo on your next quant.*
**Nemotron Puzzle 75B on a 64GB M2 Max** `(id 1573, Reddit)`
Runs smoothly — a concrete ceiling number for Apple-silicon home labs.
*Do: compare against your own max-model-on-Mac result.*
**Your $80 Tesla P100 has been doing silently noisy math in llama.cpp for years** `(id 1975, Infra, 0.32)`
Three-line fix, free. The most "worth trying tonight" infrastructure post in the set.
*Do: apply the 3-line fix tonight.*
---
## Benchmarks & Builds
**GPUHedge: serverless GPU hedging drops cold-start p95 from 117s → 30s** `(id 2438, Problem Solved, 0.41)`
Measured latency win with a concrete method.
*Do: steal the hedging pattern for your own GPU jobs.*
**Migrating a production AI agent to GPT-5.6: 2.2x faster, 27% cheaper** `(id 2089, HN, 0.41)`
Real cost/latency numbers from a production cutover.
*Do: benchmark your own agent migration against these.*
**5090 (475/600W) vs 6000 Pro MaxQ / WS (600W) concurrency** `(id 1559, Infra, 0.34)`
Full compute comparison with methodology.
*Do: map your workload onto their numbers.*
**Dual-GPU PCIe transfer under llama.cpp (tensor + pipeline)** `(id 1565, Reddit, 0.34)`
Measured interconnect behavior for multi-GPU home builds.
*Do: check your own PCIe scaling.*
---
## Problem Solved
**The real bottleneck for AI agents may be proving who they are** `(id 2314, Infra, 0.19)`
Identity before intelligence — a production lesson, not a feature drop.
*Do: learn the pattern before you scale agents.*
**AI agent crawlers now need permission** `(id 2134, RSS, 0.25)`
Cloudflare-style rules for agent access. A workflow decision, not news.
*Do: set the same rule for your own agents.*
**GPUHedge / Migrating** (see Benchmarks) — both are *problem-solved-with-numbers*, the canonical section fit.
---
## Worth Trying Tonight
1. **Apply the Tesla P100 llama.cpp 3-line fix** `(id 1975)` — free, immediate, local.
2. **Install Juggler and drive one real coding task** `(id 2225)` — open-source, now.
3. **Replicate the quad-5060Ti Qwen3.6 bench on your GPU** `(id 1558)` — 20 minutes, real numbers.
4. **Try Voodoo Quant on your next local model** `(id 1977)` — measured 95% KLD win.
5. **Wire Zer0Fit as an MCP tool in your agent** `(id 2427)` — 100% local forecasting.
---
## What This Edition Proves
Every story above passes the Editorial Test: a reader can **install, run, benchmark, replicate, or learn** something. Nothing here is a lawsuit, a funding round, a CEO take, or a valuation. That's the entire publication in one morning — and the bar every automated edition must clear.
*Rejected from this prototype (representative): PixVerse $439M raise, Apple/OpenAI trade-secret suit, Altman job-creation take, Spotify AI assistant, Lorde-on-AI-glasses. Reader would do NOTHING with those.*
+74
View File
@@ -0,0 +1,74 @@
# ADR-0007: Editorial Pivot — AI News Aggregator → AI Enthusiast Daily
**Status:** ACCEPTED · 2026-07-15
**Supersedes:** implicit "AI news aggregation" assumption (never written down — that was the bug)
**Superseded by:** nothing yet
---
## Title
Editorial Pivot: AI News Aggregator → AI Enthusiast Daily
## Context
Athena Oracle was built as a multi-source AI research pipeline: ingest → score → pattern/falsification. Sprint 1 (pure rule-based bucket classifier + scorer) was the first time we put 200 real stories in front of a human with the question "would we proudly publish these?"
The classifier accuracy was never the discovery. The discovery was **what the stories were actually for**. Scanning the 200, the ones we'd proudly ship were uniformly *actionable by a builder*: local-model how-tos, benchmarks with real numbers, reproducible tooling, agent infra with code. The ones we'd reject were uniformly *spectator content*: lawsuits, funding rounds, CEO opinions, valuations, corporate announcements.
We had been optimizing the system for the wrong question.
## Decision
Athena Oracle is **no longer optimizing for:**
> "What happened in AI today?"
Athena Oracle is **optimizing for:**
> "What can an AI enthusiast DO after reading this?"
This changes every layer: scoring, classification, editorial review, rendering, narratives, memory. Everything.
## Before / After
| Dimension | Before (implicit) | After (locked) |
|-----------|------------------|-----------------|
| Optimized for | Recency | Actionability |
| | Volume | Reproducibility |
| | Virality | Enthusiast value |
| | | Builder usefulness |
| Unit of value | "was published" | "can be done" |
| Audience | anyone interested in AI | builders / tinkerers / local-AI users |
| Reject signal | none | "reader would do NOTHING" |
## Sprint 1 Evidence
From the 200-story manual review (athena_review_report.txt):
**High signal (would ship):**
- LOCAL AI bucket — gguf / rtx / quantization / llama.cpp stories scored highest on enthusiast + replication
- Open-source tools (Juggler GUI coding agent, open-source arXiv tool, Zer0Fit MCP server)
- Benchmarks with real numbers (GPUHedge: 117s→30s p95; Migrating to GPT-5.6: 2.2x faster, 27% cheaper)
- Infrastructure with code (Your $80 Tesla P100 llama.cpp fix)
- Production learnings (agent identity, permissioned crawlers)
**Low signal (would reject):**
- Funding rounds (PixVerse $439M, DeepSeek $7B)
- Lawsuits (Apple/OpenAI trade secret, Google training suit)
- CEO opinions (Altman, Hassabis, Mosseri takes)
- Valuations (PixVerse $2B)
- Corporate announcements (Waze features, Spotify assistant)
**Taxonomy gap found:** 45 / 200 (22.5%) were UNCATEGORIZED — mostly Reddit/HN opinion + culture-adjacent pieces with no keyword hit. This is exactly the discovery data we wanted: the editorial boundary is sharper than any keyword set yet.
## Consequences
- All future scoring work measures actionability, not recency.
- The Lens (Sprint 2) is **blocked** until manual review tallies are returned and the taxonomy is tuned by hand.
- Narratives and memory engines, when built, must encode "what can be done," not "what happened."
- This ADR is the reference anchor for every later ADR.
## Confirmation
Accepted by founder directive 2026-07-15. Locked in `/docs/vision/VISION_LOCK_V1.md`.
+47
View File
@@ -0,0 +1,47 @@
# EDITORIAL GUIDELINES — AI Enthusiast Daily
Derived from VISION_LOCK_V1.md and ADR-0007. These are the operating rules for every edition, human- or machine-assisted.
---
## The One Test
> **What would an AI enthusiast DO after reading this?**
If the honest answer is **Nothing**, the story does not belong in the publication. No exceptions for "it's a big deal" or "everyone's talking about it."
## Publish Lean
Default toward stories where the reader walks away able to:
- **install** something (open-source tool, model, agent)
- **benchmark** something (real numbers, reproducible method)
- **run** something locally (Ollama, llama.cpp, GGUF, self-host)
- **replicate** a result (code, weights, config)
- **learn** a technique (production war story, failure post-mortem)
- **build with** it (agent infra, framework, pipeline)
## Reject Default
Reject by default when the story is:
- A lawsuit or legal filing (unless it changes what a builder can ship)
- A funding round or valuation (money moved, no capability changed)
- A CEO / exec opinion or take (someone said something)
- A celebrity or consumer AI culture piece (glasses, ads, vibes)
- A corporate feature announcement with no reproducible substance
- A pure market / stock / IPO item
## Section Fit (see SECTION_DEFINITIONS.md)
Every published story must map to exactly one section. If it fits none, it's either UNCATEGORIZED-by-design (hold) or a reject.
## Score Is Not Taste
The `final_score` from Sprint 1 is a **draft signal only**. It was built to be debugged, not trusted. Editorial judgment — the One Test — overrides any number. A 0.50 local-AI benchmark may ship; a 0.29 culture piece may not.
## Hand-Before-Machine
No automation may publish. Automation may *propose*; the human editor *confirms*. The founder rule stands: "Publish? [Y/N] — Not algorithmic. Human review only."
## Memory Rule
When future memory / knowledge-graph components land, they must record **what a reader can do** with a development — not a summary of the development. "Qwen3.6-27B runs on 4×5060Ti at INT8" is memory. "Qwen released a model" is not.
+35
View File
@@ -0,0 +1,35 @@
# SECTION DEFINITIONS — AI Enthusiast Daily
The publication is organized into five working sections. Every published story maps to exactly one. These are editorial sections, not the Sprint 1 classifier buckets (those are a separate, internal taxonomy — see athena_review_report.txt).
---
## 1. What Shipped Today
**Things people built.**
New open-source tools, models released with weights, agents shipped, MCP servers, GitHub projects that a reader can go use right now.
*Editorial test:* "Can I install or run it today?" → Yes = in.
## 2. Run It Locally
**Local models, GGUF, Ollama, inference, benchmarks on consumer hardware.**
Anything about running AI on your own machine — quantization, VRAM budgets, llama.cpp tricks, Mac/Linux/RTX setups, home-lab builds.
*Editorial test:* "Could I replicate this on hardware I own?" → Yes = in.
## 3. Benchmarks & Builds
**Hardware and performance experimentation.**
Head-to-head GPU comparisons, concurrency tests, latency/throughput numbers, quantization-quality showdowns, build logs with measurable outcomes.
*Editorial test:* "Are there real numbers I can compare against my own setup?" → Yes = in.
## 4. Problem Solved
**Real-world outcomes and workflows.**
Production war stories, failure post-mortems, "we fixed X and here's the method," agent-identity/permissioning, cost-reduction playbooks.
*Editorial test:* "Did someone actually ship something and learn a transferable lesson?" → Yes = in.
## 5. Worth Trying Tonight
**High-action recommendations.**
The short list — 3 to 5 items max — that a reader could act on *this evening*. Curated, not comprehensive. The "if you only do one thing" section.
*Editorial test:* "Would a builder drop what they're doing and try this tonight?" → Yes = in.
---
## Mapping note (Sprint 1 → sections)
The internal classifier buckets (LOCAL AI, PROBLEM SOLVED, RESEARCH, INFRASTRUCTURE, SHIPPING, MODEL RELEASE, BUSINESS, CULTURE, UNCATEGORIZED) feed these sections but are NOT identical to them. Section assignment is an editorial act, not a mechanical copy. A RESEARCH paper with a clear builder angle may land in Benchmarks & Builds; a MODEL RELEASE with no reproducible substance may be rejected entirely.
+57
View File
@@ -0,0 +1,57 @@
# SPRINT 1 FINDINGS — Reference Material
Raw evidence from the Sprint 1 manual review (200 stories, athena_review_report.txt). This document is **reference material for future decisions** — it records what the data actually showed so later tuning has a baseline.
---
## What We Learned
Sprint 1 was pure rules (no embeddings, no LLM, no semantic similarity) by founder directive: *discover the taxonomy before adding intelligence*. The classifier's job was not accuracy — it was to surface misclassifications as signal. It did.
## High Signal (ship)
Stories the editorial test would pass — reader can DO something:
- **Local AI** — gguf / rtx / quantization / llama.cpp. Highest enthusiast + replication scores.
- e.g. "I benched quad 5060Tis for code generation with Qwen3.6-27B" (final 0.50)
- "Voodoo Quant beats Unsloth Dynamic 2.0 KLD by 95%" (0.45)
- **Open-source tools** — things to install/run.
- "Show HN: Juggler open-source GUI coding agent" (0.57, highest in set)
- "Open Source Local LLM Training Tool (consumer hardware)" (0.46)
- "Zer0Fit — MCP server for zero-shot ML, 100% local" (0.300.46)
- **Benchmarks with real numbers** — reproducible, comparable.
- "GPUHedge: cold-start p95 117s→30s" (0.41)
- "Migrating to GPT-5.6: 2.2x faster, 27% cheaper" (0.41)
- **Infrastructure with code** — fixable, runnable.
- "Your $80 Tesla P100 silently noisy math in llama.cpp — 3-line fix, free" (0.32)
- **Production learnings** — transferable lessons.
- "The real bottleneck for AI agents may be proving who they are" (0.19)
- "AI agent crawlers now need permission" (0.25)
## Low Signal (reject)
Stories the editorial test would fail — reader does NOTHING:
- **Funding rounds** — PixVerse $439M, DeepSeek $7B. Money moved, no capability changed.
- **Lawsuits** — Apple/OpenAI trade secret, Google training suit. Spectator content.
- **CEO opinions** — Altman, Hassabis, Mosseri takes. Someone said something.
- **Valuations** — PixVerse $2B. Number, no action.
- **Corporate announcements** — Waze features, Spotify assistant, Siri beta. No reproducible substance.
## Taxonomy Gap (the real discovery)
- **45 / 200 (22.5%) UNCATEGORIZED.** Mostly Reddit/HN opinion + culture-adjacent pieces with no keyword hit (e.g. "Stop Telling Me to Ask an LLM", "Mesh LLM", "Ghost Font").
- This is **not a failure** — it's the editorial boundary made visible. The keyword set is narrower than taste. Tuning Sprint 2 (Lens) must start from these 45, not from classifier precision.
## Bucket distribution (200 reviewed)
| Bucket | n |
|--------|---|
| RESEARCH | 40 |
| INFRASTRUCTURE | 23 |
| UNCATEGORIZED | 45 |
| MODEL RELEASE | 24 |
| PROBLEM SOLVED | 19 |
| SHIPPING | 12 |
| CULTURE | 15 |
| BUSINESS | 13 |
| LOCAL AI | 9 |
## Open question for Sprint 2
When the Lens arrives, its first job is **not** to classify better. It's to explain *why* a story is or isn't actionable — and to propose a section (§SECTION_DEFINITIONS) for human confirmation. The 45 UNCATEGORIZED are the training set for that judgment, not the 155 that already matched.
+63
View File
@@ -0,0 +1,63 @@
# VISION LOCK V1
**Status:** PERMANENT · LOCKED 2026-07-15
**Authority:** Primary system constraint. No future scoring, narrative, memory, knowledge-graph, or editorial-automation work may contradict this document.
---
## Mission
Find the **small number of developments that change what AI enthusiasts can DO today** — not what happened, but what became possible.
## Audience
NOT:
- General readers
- Investors
- Executives
- Policymakers
IS:
- **Builders** — people shipping things with AI
- **Tinkerers** — people modifying, extending, breaking
- **Local AI users** — people running models on their own hardware
- **Home-lab operators** — people running inference, agents, pipelines at home
- **Workflow creators** — people automating with agents
- **Agent developers** — people building agent systems
## Editorial Test
For **every** story, ask one question:
> **What would an AI enthusiast DO after reading this?**
Acceptable answers:
- `install it`
- `benchmark it`
- `run it`
- `replicate it`
- `learn from it`
- `build with it`
If the answer is:
> **Nothing.**
**Reject.**
## Architectural Constraint
The editorial vision is now the **primary system**.
The architecture serves it. Not the other way around.
Any future component — scorer, classifier, narrative engine, memory engine, knowledge graph, rendering layer, editorial automation — must be justified against the Editorial Test above. If a component optimizes for recency, volume, virality, or engagement instead of *actionability*, it contradicts the Lock and must be rejected or re-scoped.
## Architectural Priority Order
1. **Vision** — the Editorial Test wins all conflicts
2. **Editorial Quality** — would we proudly publish this?
3. **Reader Value** — can the reader DO something?
4. **Automation** — only after 13 are proven by hand
5. **Technical Elegance** — last. Never traded against 14.
If any two levels conflict, the higher level wins.