create - #29
Open
grandchildrice wants to merge 14 commits into
Open
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
presentation-agent | 642c729 | Commit Preview URL Branch Preview URL |
May 23 2026, 04:09 PM |
…lems 勉強会 framing — avoid self-promotion. Remove SL21 (成熟度ギャップ chart) and rewrite SL21b from a Nyx-pitch (共同研究 / パイロット監視 / アドバイザリー) into three domain-neutral論点 the DeFi field has yet to address. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The new slide-import-guard in @slidev/cli 52.15 (Rolldown-based build) rejects static `src="/images/..."` attributes because Vue's compiler rewrites them as ESM imports, which then resolve outside Vite's server.fs.allow and fail the build on Cloudflare Pages. Switching to `:src="'/...'"` keeps the path as a runtime expression so it's left as a plain public-asset URL. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- SL01: drop poetic 「コードは正しかった」 subtitle and KelpDAO date line
so the title slide is just client/title/speaker
- SL09: introduce DVN with explicit `≒ クロスチェーン送金のマルチシグ`
analogy on first mention so a banking audience can anchor it
- SL21b: rebuild the `次の数年` three-card layout
- 論点 2 (運用構成の継続監視) absorbs the formal-verification +
Proof-of-Reserve-for-operations theme as `運用の正しさの継続的保証`
- 論点 3 swaps from cross-industry reports to
`バグバウンティを置き換える発見モデル` (AI動的監視 + 形式検証付き報告)
- Body text drops DVN/RPC/PoR jargon in favor of マルチシグ/ノード/残高証明
- Tightened paddings, font sizes and bottom-summary margins so the
cards no longer overflow the slide
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
max-h-[Nvh] / style="height:Npx" let chart boxes overflow the slide canvas on PDF export. Pin width/height to each chart's natural aspect so the export preview shows the full image. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…tion Default slidev export rendered SL11's <img>+caption blank below the title (a Slidev 52.15 quirk with this particular slide's bind+layout combo). --per-slide isolates each slide and the chart renders. NixOS-bundled playwright-chromium can't link libgbm.so.1; auto-detect google-chrome-stable / chromium / chrome on PATH and pass it via --executable-path. Falls through to playwright's bundle on platforms where one isn't found. SL11 image dropped to 607x380 (was 700x438) so the CWE/OWASP caption fits in the slide canvas, matching SL18/SL19's sizing pattern. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
SL14 redesigned: 3-panel code (market.move:575 register / :580 buggy exec guard / :686 stop condition) side-by-side with the Group A vs Group B reserve aggregation diagram. Makes the global-vs-per-group mismatch visible at a glance. New SL14b preserves the ¥27 reward + 2-bug summary cards (Med EMA-vs- Spot + High ADL) as the punchline. Bug 1 stays as summary text; Bug 2 is cross-referenced back to SL14 for the code-level detail. Deck grows from 22 to 23 pages. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
タイトルを「顧客Aを見るべき場所で、銀行全体を見ていた」に変更し、 バグ箇所に「1/3 だけ違う」バッジ、顧客Aに「30M < 閾値50M → 健全」 の緑カラウト、出力箱を ❌コードが返した答え/✓本来あるべき答え に 再ラベル。皆様の言葉で (ITGC-CC04 / FISC 統83) バナーも追加。 SL14b の Bug 2 カードも揃えて「顧客Aを見るべき場所で、銀行全体を見ていた」に統一。 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…g deep-dive 5ステップのユーザフロー (handle_new_obligation → handle_mint → handle_borrow → handle_debt_auto_deleverage ← 問題関数 → try_stop_borrow_deleverage) を 左列に並べ、右列でステップ4の中身 (575/580/686 の3管理ポイント) と 攻撃経路を同じ番号で対応させる。SL14 の3管理ポイント詳細に入る前の オリエンテーション。 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
5ステップを横パイプラインで並べ、問題関数 (Step 4) を赤枠で強調。 拡大鏡 ▼ で下段の「ステップ4 の中身」(3管理ポイントの色分けバー) と 「攻撃データフロー」(顧客カード → reserve 合算 → 比較器 → 結果) の 2列に視線を誘導。テキスト中心だった旧版から、図中心に作り変え。 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
コード関数のパイプラインから、ユーザの動きそのもののフロー図に作り直し。 顧客A (LST eMode で stSUI 50M を担保に USDC 30M 借入、健全) と 顧客B (ETH eMode で wETH 100M を担保に USDC 80M 借入、別グループ) の 2シナリオを並列に描き、「二人とも USDC を借りた」で同じ reserve に 合算される様子を SVG で可視化。reserve 110M を最大級にハイライトし、 :580 の誤判定 → 顧客A の stSUI 強制清算という縦フローで「何を担保にして 何をしたら清算されたか」が一目で読めるようにした。 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…ghtning) CSSボックスから、SVG イラストレーションへ全面改修。顧客A/Bを人型シルエット、 担保を宝箱(chest)で描き、両者がUSDCを同じ「USDC reserve」金庫に投げ込む様子を コインアイコン付きの破線矢印で可視化。中央の黒い大型金庫に「30M + 80M = 110M」、 下段に :580 の誤判定 (110M > 50M)、その先に雷 → 顧客Aの stSUI 金庫が破壊 される結末を描いた。Slidev のmarkdownパーサがインライン SVG の text要素を HTMLに昇格させて壊す問題を、public/images/diagrams/sl13b_scenario.svg の 外部ファイル化で回避。 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
SL13b: 中央reserve金庫のコイン/ロック/ラベル配置を修正。コインを金庫の外に 出し、「USDC reserve」ラベルを蓋部分に、ロックを蓋のエッジへ縮小配置。 「30M + 80M」と「= 110M」を2行に分けて視認性向上、文字かぶり解消。 SL14: 同じシナリオシーンを左半分に再掲しつつ、reserve金庫を赤い破線で 囲って「:580 が読んだ場所」、顧客A→reserve矢印を緑破線で囲って「本来 :686 のように ここだけを見るべき」と注釈。右半分に handle_debt_auto_deleverage の 3 管理ポイント (:575 ✓ 登録 / :580 ❌ 実行 / :686 ✓ 停止) のコードを スタックし、赤と緑の破線で図と対応づけ。verdictと「皆様の言葉で (ITGC/FISC)」 バナーも併載。 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.