doclayer
/ meta-harnesses / planning
scenario 02: planning
A
V
PLAN chain · DOC_PLAN/v1 graph-delta /
  1. 01Bootstrap
  2. 02Plan
  3. 03Draft
  4. 04Review
  5. 05Publish
  6. 06Reader
architect: idle
planning board · evidence graph · decision log · full multiplayer surface lives in scenario 07 →
01Plan
02Draft
03Review
04Publish
decision outline holes · owners · order shared graph
  • 1 Harness claim
  • 2 Evidence
  • 3 Mechanism
  • 3.1 State-machine
  • 3.2 Renderer
  • 3.3 Eval hooks
  • 4 Proof example
  • 5 Open holes
V
Vishal builder · concrete-first layout · evidence rail + outline

Meta-harnesses

A series, target: AI engineers and builders.

3. Building meta-harnesses

The plan is still a map, not prose: define the harness claim, decide which sources are load-bearing, and mark the holes that cannot be hand-waved in draft.

Every row needs a next action before writing starts. RLMs stay only if they explain the control loop.

Vishal
+3 words
evidence
raw.works · vishal
Harness-as-controller notes
claim candidate · owner V
decision logged §3.2 ✓
x.com · trq212
Renderer constraint thread
source required · §3.2
youtube.com
Meta-harnesses talk
use only if mechanism stays fuzzy
+ akhil just added
x.com/paraschopra/1834…
scraping
Recursive feedback
+6 chunks · ready
akhil converted §3.2 objection → source requirement
shared outline · decision log · evidence graph
A
Akhil claim-first · evals advocate layout · objection rail + outline
planning objections
✓Resolving
"Does renderer-constraint belong before state-machine lineage?"
Akhil ←→ Vishal · decision logged
resolved by moving §3.2 above eval hooks
Open · evidence
Need one concrete trace that proves the Architect emits grammar atoms, not vibes.
Akhil & Vishal · 0 turns
Open · scope
Keep multiplayer as proof example here, or defer it to its own article?
Vishal · proposed
citation
cite "the harness is the controller; the planning question is which controller transitions the reader must see."
raw.works/posts/rlms ¶ 4 pinned · akhil
§3 density 2.8/3
reading §5 evals

Meta-harnesses

A series, target: AI engineers and builders.

3. Building meta-harnesses

Akhil is not line-editing yet. He is ranking unresolved claims: what must be proven, what can be deferred, and which section carries the technical burden.

The plan only advances when each open hole has an owner, a source, or a deliberate skip.

Akhil
scroll
2 authors live phase: plan chain: DOC_PLAN/v1 yjs: synced 12 events/min · 8ms RTT
← bootstrap all scenarios next: drafting →
next: drafting →