docs(whitepaper): product-first framing for tangle-cloud + open-source bridge#210
docs(whitepaper): product-first framing for tangle-cloud + open-source bridge#210drewstone wants to merge 1 commit into
Conversation
…e bridge
Lead with the product and the self-improving thesis, not decentralization and
tokenomics. The abstract and Vision opening now open on what ships today (sandbox
runtime + agentic workbench, every run traced and mined for improvement), frame
decentralization as the trajectory ('built to decentralize'), and add the
open-source bridge: the same open tooling runs on managed infra today and on the
operator network as it comes online, so there is no lock-in. Rebuilt PDF.
tangletools
left a comment
tangletools
left a comment
There was a problem hiding this comment.
✅ Auto-approved drewstone PR — 4bfcf1f8
This PR was opened by the trusted drewstone account.
The full PR reviewer audit still runs separately and will publish findings if it detects issues.
tangletools · auto-approval · reason: drewstone_author · 2026-07-22T17:09:53Z
tangletools
left a comment
tangletools
left a comment
There was a problem hiding this comment.
🟡 Value Audit — sound-with-nits
| Verdict | sound-with-nits |
| Concerns | 2 (2 weak-concern) |
| Heuristic | 0.0s |
| Duplication | 0.0s |
| Interrogation | 56.5s (2 bridge agents) |
| Total | 56.5s |
💰 Value — sound-with-nits
Reframes the tangle-cloud whitepaper's abstract + Vision opening to lead with the product and self-improving-AI thesis, sequencing decentralization as the trajectory; coherent, well-scoped, substantiated by the body, with one flagged title inconsistency.
- What it does: Rewrites three paragraphs of LaTeX copy (the abstract at whitepaper/tangle-cloud.tex:43 and the Vision opening at :55-59) plus a rebuilt PDF. The abstract now leads with 'infrastructure for AI systems that improve themselves,' names the two shipping products (sandbox runtime, agentic workbench), and states that traces are mined for improvement. The Vision opening sequences the product first, then
- Goals it achieves: Align the paper's highest-leverage opening copy with the actual GTM (product first, decentralize later) and with the website's 'infrastructure for self-improving AI' story, instead of leading with decentralization/tokenomics. The open-source bridge framing reconciles product-first messaging with a decentralized-future promise without locking the reader in. Better outcome: the paper's frame now mat
- Assessment: Good change on its merits. It is well-scoped (opening copy only, body untouched) and every new claim is substantiated by the existing body — traces-flywheel at tangle-cloud.tex:324,332; both products have their own sections (sandbox runtime §2, workbench §3); the managed-vs-decentralized model is already described at :203. The open-source bridge is a new narrative thread but does not contradict an
- Better / existing approach: none — this is the right approach. Searched whitepaper/*.tex (tangle-cloud, tangle-protocol, tangle-sdk); there is no duplicate product-framing block elsewhere to reuse, and prose framing is inherently local to each paper. The author correctly did NOT fold this into a mega-paper. Git log shows this path has had focused accuracy/voice passes before (9652412 'sharpen protocol voice', 0341d40 'accura
- Model: opencode/zai-coding-plan/glm-5.2
- Bridge attempts: 2
- Bridge warning: opencode/kimi-for-coding/k2p7: bridge stream ended without value-audit content
🎯 Usefulness — sound-with-nits
A well-scoped, internally-consistent messaging pass on the tangle-cloud whitepaper's highest-leverage copy; PDF kept in sync with the .tex.
- Integration: Standalone publishable doc artifact in whitepaper/ alongside the protocol and sdk papers; the three-paper split is preserved and the .tex/.pdf are in sync. Not wired into code, which is correct for a whitepaper — it is reached by external publication, not by an import. Not dead surface.
- Fit with existing patterns: Strong fit with the document's actual content. The new lede ('two products ship today; every run traced and mined') is corroborated by the unchanged body: sandbox runtime described at tangle-cloud.tex:149/151, workbench-to-sandbox flow at :342, and the closing 'operational today... unfinished' statement at :622. The abstract's promise to cover operator economics + roadmap matches the unchanged fee
- Real-world viability: Holds up: the new prose does not contradict any fact in the body, and the open-source-bridge claim ('same tooling runs two ways') is consistent with the body's managed-vs-operator-network framing throughout. Only soft spot is a frame mismatch between the new abstract ('infrastructure for AI systems that improve themselves') and the still-unchanged title/section header, both of which still lead on
- Model: opencode/zai-coding-plan/glm-5.2
- Bridge attempts: 1
💰 Value Audit
🟡 Title still says 'Decentralized Compute Layer for AI' while abstract now leads with the self-improving-AI frame [maintenance] ``
whitepaper/tangle-cloud.tex:34 keeps '\large The Decentralized Compute Layer for AI' as the subtitle, but the new abstract (line 43) leads with 'infrastructure for AI systems that improve themselves' and the Vision (line 57) closes on 'AI that gets better the more it runs.' The title and opening now tell slightly different stories. The PR author explicitly flagged this as a deferred founder-level call ('The Compute Layer for Self-Improving AI' would match the new frame + website). Not a blocker
🎯 Usefulness Audit
🟡 Title and Vision header still lead on 'Decentralized' after the abstract was reframed to 'self-improving AI' [ergonomics] ``
tangle-cloud.tex:34 title is 'The Decentralized Compute Layer for AI' and :52 section header is 'Vision: Decentralized AI Infrastructure', while the new abstract (:43) and Vision body (:57) now lead on 'AI that gets better the more it runs.' A reader hits 'Decentralized' on the cover, then a 'self-improving AI' abstract. The author already flagged this in the PR body as a founder-level call (left intentionally), and :59's 'built to decentralize' clause papers over it, so it does not gate shippin
What this audit checks
It judges the change on its merits — not whether it was tasked out in an issue. Unticketed, fast-moving work is fine; the question is whether the change is good and whether a better or existing approach should be used instead.
| Pass | What it asks |
|---|---|
| Heuristic | Vague title? Whitespace-only or cruft-bearing diff? (content signals only) |
| Duplication | Do added function/class names already exist elsewhere in the repo? |
| Value Audit | What does it do? What goal does it achieve? Is it good? Better architecture or already-exists? |
| Usefulness Audit | Does it integrate and fit? Will it hold up in real use and actually get used? |
Findings are concerns, not blocks — the human reviewer decides what to do with them.
✅ No Blockers —
|
tangletools
left a comment
tangletools
left a comment
There was a problem hiding this comment.
✅ Approved — 1 non-blocking finding — 4bfcf1f8
Full multi-shot audit completed 2/2 planned shots over 2 changed files. Global verifier still owns final merge decision.
Full immutable report for this review: trace
Summary comment for this run: full summary
tangletools · 2026-07-22T17:13:08Z · immutable trace
|
Closing: this reframe was built on a wrong read of the product architecture (it conflated the centralized cloud with the decentralized Blueprints layer, and used slop marketing copy). Reverting to reconsider with the correct model. |
2 participants
Opening-frame messaging pass on the
tangle-cloudpaper. Scope: the abstract and the Vision opening only — the highest-leverage copy, where the paper sets its frame. The rest of the paper (mechanics, economics, roadmap) is unchanged.Why
The paper led with decentralization and tokenomics, not the product. The abstract opened on "decentralized compute infrastructure," then the Vision dived straight into fee-split tables, genesis token buckets, and vesting — before a reader learned what Tangle Cloud does for them. That runs ahead of the actual go-to-market (product first, decentralize later) and diverges from the website's "infrastructure for self-improving AI systems" story.
What changed
Notes
latexmk) so.texand.pdfstay in sync.