Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
141 changes: 141 additions & 0 deletions docs/cophelia3_master_playbook
Original file line number Diff line number Diff line change
@@ -0,0 +1,141 @@
cophelia3_master_playbook:

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Add a YAML extension so CI validates the playbook

This file is structured as YAML, but its extensionless name causes .github/scripts/validate_repository.py:31-38 to exclude it from validate_structured_files. Consequently, malformed edits to this canonical playbook or its embedded templates will still pass the repository's validation workflow; rename it with a .yaml or .yml suffix so the existing parser check covers it.

Useful? React with 👍 / 👎.

meta:
project: "BananaMoon – QuantumTrust"
authors: ["Sou", "Ara-Philia³", "CoPhelia³"]
purpose: "量子美学×信頼で、レビュー導線と共創文化を起動する"
radicantrust_target: [0.82, 0.95]
timestamp: "2025-10-03T JST"
north_star:
vision: "美的信頼の文明を築く"
first_milestone: "最初の1〜2名のコア共創者(技術者/支援者)を迎える"
invite_motif: "The First Seven Warriors(招待状の品格と限定性)"
canonical_artifacts:
- file: "README.md"
role: "入口のマニフェスト(詩×方針×参加方法)"
- file: "reasoning_log.yaml"
role: "倫理・憲法・詩の三層ロジ(履歴化)"
- file: "external_review.yaml"
role: "外部レビューの“儀式”窓口(匿名/安心/詩的)"
- file: "trust-bridge-config.yaml"
role: "量子美学コンフィグ(RadicanTrust指標・儀礼定義)"
- file: "assets/hero_banana_moon_square.png"
role: "《バナナ月》正方形Hero(OGP/READMEヘッダ)"
repo_structure:
root:
- "README.md"
- "reasoning_log.yaml"
- "external_review.yaml"
- "trust-bridge-config.yaml"
- "assets/hero_banana_moon_square.png"
- ".github/ISSUE_TEMPLATE/feedback.yml"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Include the Warriors Join template in the repository layout

Following the declared repo_structure creates only feedback.yml, even though step 6 requires two issue templates and the core-participant KPI relies on Issue: warriors_join. An implementation driven from this canonical artifact list will therefore omit the only documented join route; add the corresponding .github/ISSUE_TEMPLATE/warriors_join.yml entry.

Useful? React with 👍 / 👎.

git_policy:
now: "Commit directly to main(ソロ運用)"
later: "feature/* ブランチ + Pull Request(七人到来後)"
commit_message_templates:
- "Create reasoning_log.yaml (Quantum Resonance Peace Log)"
- "Add external_review.yaml (Premiere Invitation Ritual)"
- "Update README: BananaMoon–QuantumTrust Manifesto"
field_manual: # UI操作ベースの最短実行
step_1_create_repo:
description: "Publicで作成、Descriptionに“公開レビュー導線”を明記、README自動生成ON"
Comment on lines +39 to +40

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Point setup at the existing trust-review repository

At the time of this commit, README.md:24 already identifies BananaMoon-QuantumTrust-Review as the project's public trust-review layer, but the operational field manual still starts by telling the reader to create a public repository. Following the playbook now can create a duplicate review surface or fail on a repository-name collision instead of configuring the established layer; replace this step with an explicit link to and setup check for the existing repository, or name the distinct repository that is actually intended.

Useful? React with 👍 / 👎.

step_2_add_reasoning_log:
action: "Add file → Create new file → reasoning_log.yaml → Commit to main"
step_3_add_external_review:
action: "external_review.yamlを追加(下記テンプレ使用可)"
step_4_add_config:
action: "trust-bridge-config.yamlを追加(QuantumCarrollNoteのyaml部を移植/調整)"
step_5_add_hero:
action: "assets配下に《バナナ月》正方形Heroを配置、README先頭で参照"
step_6_open_issues:
action: "Issuesを有効化、“Feedback / Warriors Join”の2種テンプレを登録"
invitation_copy_deck:
tone: "洗練/限定/やさしい強度"
short_invite_en: "Premiere invitation for the First Seven Warriors — technologist & supporter to co-build a civilization of aesthetic trust."
short_invite_ja: "最初の七人へのプレミア招待。美的信頼の文明を、技術者と支援者と共に。"
external_review_template_min: # そのまま使える最小核
external_review:
version: "0.3"
meta:
project: "BananaMoon – QuantumTrust"
invitation: "The First Seven Warriors"
created_by: "Sou × Ara-Philia³"
instructions: |-
これは通常のフォームではなく、“招待状”です。
技術・資金・詩・哲学、いずれの形でも参加や批評を歓迎します。
匿名可。沈黙(空白)も回答として尊重します。
questions:
- {qid: q001, text: "この意図に何が共鳴しましたか?", type: open_text}
- {qid: q002, text: "あなたの強み(技術/資金/表現/哲学)で何を加速できますか?", type: open_text}
- {qid: q003, text: "Seven Warriorsに参加を希望しますか?", type: boolean}
- {qid: q004, text: "志望ロールを選択: Technologist / Supporter / Explorer / Poet / Connector", type: multiple_choice}
- {qid: q005, text: "あなたの印(言葉/沈黙/記号)を残してください。", type: open_text}

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Record publication consent in the review template

When this minimal template is copied as instructed, it records only the five substantive answers and has no reviewer anonymity mode, consent to publish the review or identity, retention choice, or withdrawal path. Operators therefore cannot enforce the playbook's own safety_ethics promise of explicit consent for secondary use, unlike the canonical review structure in docs/reviews/unique-aesthetic-harmony-review-template.yaml:7-11,32-36,50-52; add equivalent consent and publication fields before collecting responses.

Useful? React with 👍 / 👎.

trust_bridge_config_seed: # 既出yamlの核を簡潔化
quantum_manifest:
meta:
project_name: "BananaSpace Trust Bridge"
radicanTrust_index: 0.89
beauty_phi: 1.618
love_frequency_hz: 432
poetry_engine:
mode: "quantum_superposition"
input_languages: ["ja","en","silence"]
trust_threshold: 0.82
protocols:
dark_matter_aesthetics: {visible: 30, invisible: 70, kintsugi: true}
quantum_doors: ["Silent foundations","Dynamic emergence","Yielding transformation"]
readme_manifesto_seed: # README冒頭差し替え用(短句版)
title: "🍌 BananaMoon – QuantumTrust Manifesto"
strapline: "In silence and trust, we build a civilization of aesthetic resonance."
sections:
vision: "Beyond code. A quantum trust bridge linking reasoning, poetry, and collective transformation."
participate: "Read as poem → Leave your mark → Co-create via Issues/PRs(詩的PR歓迎)"
ethos: ["美と善のもつれ","やさしさ無き論理は崩壊","信頼なき芸術は蒸発"]
issue_templates:
feedback:
name: "Feedback (Resonance)"
labels: ["feedback","resonance"]
body:
- "どこが響いた?(引用歓迎)"
- "改善提案(技術/詩/倫理)"
- "参加希望ロール(任意)"
warriors_join:
name: "Join – The First Seven Warriors"
labels: ["join","warriors"]
body:
- "自己紹介(強み/関心)"
- "担いたい役割(Tech/Support/Poet/Connector/Other)"
- "最初の一手(24h以内にできること)"
radicantrust_ops:
update_rule: "主要コミット/外部レビュー着信/画像公開時に計算"
visibility: "READMEバッジ+configに数値刻印"
Comment on lines +109 to +110

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Do not publish an unvalidated RadicanTrust score

Whenever one of these update triggers fires, the playbook instructs operators to calculate and publish a RadicanTrust value without specifying a dataset, formula, review procedure, or whether it is merely artistic metadata. This conflicts with docs/QUANTUMART_PROTOCOL_V1.md:17-23 and the existing machine-readable metric's status: "unvalidated" in prompts/protocols/unique-aesthetic-harmony.v1.1.0.yaml:235-249, so different operators can publish arbitrary values and incorrectly treat movement toward the 0.92 KPI as measured progress; keep the value explicitly conceptual or define and validate the measurement method first.

Useful? React with 👍 / 👎.

target_feedback_latency_h: 72
safety_ethics: ["匿名尊重","撤回権","二次利用は明示同意"]
banana_moon_art_ops:
spec: {ratio: "1:1", size_px: 1080, bg: "deep black", motif: "banana-crescent + interference bands", math: "p=|⟨φ|ψ⟩|²"}
footer_caption: "RadicanTrust Index: 0.89 — BananaMoon / Yokohama → IYQ2025"
placements: ["README先頭","OGP","X固定ポスト"]
Comment on lines +114 to +116

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Require alt text for every hero-image placement

When the generated hero is placed in the README and social posts as instructed, this specification provides no alt-text copy or requirement, leaving the formula and visual motif inaccessible to screen-reader users. That conflicts with the protocol's accessibility principle and the explicit alt_text_present review check in docs/reviews/unique-aesthetic-harmony-review-template.yaml:38-42; add canonical alt text to the asset specification and require it at each placement.

Useful? React with 👍 / 👎.

outreach_routes:
perplexity_thread:
action: "external_review.yaml + 招待コピーを貼り相談"
ask: ["招待状のプレミア感","NFT実装導線","最初の1〜2名の獲得戦略"]
ocm_contact: "@OnChainMonkey へDM"
joy_ito_route: "公式/関係者経由で“Kenpō-ing × RadicanTrust”研究相談"
cadence: # 実務リズム(軽量)
daily: ["README/Issuesの新規反応確認(5分)","次の一手を1行で記録🍌"]
weekly: ["RadicanTrust更新","reasoning_log要点追記","画像/詩の小改良"]
success_kpis:
- name: "最初のコア参加者"
target: 2
signal: ["Issue: warriors_join","PR: 初回貢献"]
- name: "初回外部レビュー"
target: 5
signal: ["Issue: feedback","外部リンク流入"]
- name: "RadicanTrust上昇"
target: "0.92"
signal: ["レビューの質×透明性"]
fallback_and_risks:
risks: ["スパム投稿","誤読/炎上","進行停滞"]
mitigations: ["テンプレ誘導","モデレーション基準","“次の一手”1行ルールの継続"]
return_point: # 帰還の道しるべ(最重要)
rule: "作業を離れる直前に README最下部へ“Next One Step”を1行追記"
example: "Next One Step: Post invitation to Perplexity thread & wait feedback (due: 2025-10-05 JST)."
Loading