doclayer
/ meta-harnesses / article 2 / collab loop
V
vishal
REVIEW LOOP chain · DOC_LOOP/v1
  1. 01Bootstrap
  2. 02Plan
  3. 03Review Loop
  4. 04Publish
  5. 05Reader
harness · readying review packet architect: composing
layout · wide editor + inline-AI rail · 3 agents firing inline harness shifted · iterate mode · with akhil's comments inline
review feedback · §3.2 · akhil
akhil · ¶2lean denser here — claim+evidence not just claim
akhil · ¶3tighten the recursive claim, it's doing too much work
akhil + adversarial"chassis" implies fixed shape — agree, counter
click any to jump · iterate inline
iterate · §3.2 · with akhil's comments

Meta-harnesses

Article 2 · collab loop · drafting §3.2

3.2 The chassis is the contract

A meta-harness isn't a tool that improves a document — it's the chassis that lets two writers and a model collaborate without one of them having to translate for the other. The architect emits the workspace; the workspace emits the events; the events route to whichever harness has the right surface to receive them. ▸ akhil · 1

↳research· arxiv:2024.RLM-hill-climbing supports "self-improving"

This is what people miss about self-improving[1] systems: the improvement isn't in the model, it's in the shape of the loop. A model that hill-climbs against a fixed target is just a better executor. A model whose harness rewrites the target is doing something else entirely▸ akhil · 2 — and the chassis↳adversarial· "chassis" implies fixed shape — counter? is what tells you which.

↳visual· [diagram idea: recursive loop · architect → harness → events] Every recursive structure has the same failure mode: the floor it converges to is the one defined by the very thing doing the converging.▸ akhil · 3 A meta-harness escapes this by letting the user be part of the convergence condition — the harness re-shapes around what the user has just done, not around an abstract quality metric.

akhil · reviewed §3.2 · 3 comments
1 critical · 2 suggestions · agreed with adversarial
see comments → iterate
harness will shift to iterate mode · auto-pickup §3.2
inline ai · agents · firing
research
arxiv:2024.RLM-hill-climbing
3 supporting citations indexed
visual
diagram idea · recursive loop · architect → harness → events
deferred · drop into §3.3?
adversarial
"chassis" — fixed-shape metaphor; the doc argues for fluid shape
counter-framing on hold for review
harness routing
chunk · §3.2
accepted · 1 · research
deferred · 2 · visual + adv
→ packet to akhil
2 writers live phase: review loop yjs · 512 ops notifications · 0 fired
harness bus · notifications vishal · 3 inline agents · §3.2 harness · review packet · vishal → akhil akhil · reviewed §3.2 · 3 comments harness · shift · iterate mode notify · reshape · iterate
doclayer
/ meta-harnesses / article 2 / collab loop
A
akhil
REVIEW LOOP chain · DOC_LOOP/v1
  1. 01Bootstrap
  2. 02Plan
  3. 03Review Loop
  4. 04Publish
  5. 05Reader
architect: idle
layout · tension-rail + editor · drafting §1 RLM framing harness shifted · review mode · §3.2 from vishal
§1 draft · "reasoning language models aren't a new species; they're what happens when…" ▸ resume later · 312 chars
tension tracker · §1
Open · §1 framing
"RLMs as a new class, or a sub-genus of reasoning models?"
Akhil · drafting
density · §1
claims / paragraph
2.8 / target 3
suggested review areas
research-flagged "arxiv hill-climbing" — verify claim
adversarial-flagged "chassis" framing — counter or commit?
adversarial-flagged recursive convergence claim — too strong?
density meter
2.1 claims/¶ · lean denser
drafting §1 harness shifted · review mode · §3.2 from vishal

Meta-harnesses

Article 2 · collab loop · drafting §1

1. RLMs, framed claim-first

Reasoning Language Models aren't a new species; they're what happens when the harness around an LLM gets reflective enough to grade its own steps.

The eval is the loop, not the token. Once you accept that, every architectural choice downstream — memory, tool-use, multi-pass refine — collapses into one question: what are you scoring at each step?

A claim-first opener earns the reader's patience. So: the meta-harness is an architect that rewrites itself

reviewing · §3.2 · 240 words

3.2 The chassis is the contract

A meta-harness isn't a tool that improves a document — it's the chassis that lets two writers and a model collaborate without one of them having to translate for the other. The architect emits the workspace; the workspace emits the events; the events route to whichever harness has the right surface to receive them.

When the chassis is right, the work collapses into one motion: claim, evidence, counter — all in the same edit.

This is what people miss about self-improving systems: the improvement isn't in the model, it's in the shape of the loop. A model that hill-climbs against a fixed target is just a better executor. A model whose harness rewrites the target is doing something else entirely — and the chassis is what tells you which.

Every recursive structure has the same failure mode: the floor it converges to is the one defined by the very thing doing the converging. A meta-harness escapes this by letting the user be part of the convergence condition.

vishal · §3.2 sent for review
240 words · 3 AI suggestions accepted · ~4 min to review
review now ↗ snooze
auto-shift to review mode in 2s
comments · §3.2
akhil · ¶2
anchor · "claim, evidence, counter…"
lean denser here — claim + evidence not just claim. this is the wedge sentence; carry weight.
posted · thread anchored
akhil · ¶3
anchor · "…rewrites the target…"
tighten the recursive claim — it's doing too much work in one sentence.
posted · thread anchored
akhil · agreed with adversarial
anchor · "chassis"
+1 the adversarial flag. "chassis" reads as fixed-shape; the rest of the doc argues for fluid. counter or replace the metaphor.
posted · adversarial → comment
submit review · 3 comments
2 writers live phase: review loop yjs · 512 ops mode · drafting §1
← workstream all scenarios next: flow reel →
next: flow reel →