Files
rutster/docs/reviews
opencode controller 274d0ebff5 docs(reviews): strategic reviews + post-pivot re-score
File three docsReviewed under the strategic-relevance track:

- 2026-06-28-vision-sanity-check.md (Claude Opus 4.8): the idea-level
  review. Six findings S1-S6 (wedge emphasis, differentiation valley,
  compliance paradox, turn-taking ownership at the tap, solo scope
  vs. category timing, reframe to boundary+data loop as moat).
- 2026-06-28-gtm-path.md (Claude Opus 4.8): the GTM/positioning/
  pivots review. Seven findings G1-G6 + R1 (revenue-vector sequence,
  CLA before contributor #2 — the time-sensitive irreversible one,
  services as early engine, hosted = BYO-cloud, open-core seam,
  funding fork; plus pressure-test R1 gating the outbound beachhead).
- 2026-06-29-strategic-reviews-post-pivot-rescore.md (GLM-5.2):
  re-scores every vision + GTM finding against ADR-0007 (rent the
  trunk) + ADR-0008 (FOB / green-zone doctrine). Most findings
  strengthened or ratified by the pivot. One finding flagged as
  needing active user decision rather than doc-only action: G2
  (CLA posture), because ADR-0008 explicitly states multiple coding
  agents now work this repo and every commit without a CLA in place
  erodes the dual-license / AGPL / paid-embedding options.

Per AGENTS.md, ratifying strategy/ADR changes warrants the user's
signoff — this commit files the reviews and re-score as input to
that decision, not the decision itself. The user's pivot changes
(ADR-0007, ADR-0008, AGENTS, README, ARCHITECTURE, PORT_PLAN,
Cargo.toml, ADR-0003 status flip) are unstaged in the working tree
on this branch and remain the user's to commit.
2026-06-29 19:55:11 -04:00
..