weft-chronicle

name	weft-chronicle
description	Generate a multi-chapter Builder Journey narrative from Weft milestone attestations using Kimi — each milestone is a thread woven into the project's fabric
version	1.1.0
metadata	{"hermes":{"tags":["web3","ai","kimi","creative","narrative","weaving","0g"],"category":"creative","requires_toolsets":["terminal"]}}
required_environment_variables	[{"name":"KIMI_API_KEY","prompt":"Kimi/Moonshot API key","help":"Get a key from https://platform.kimi.ai","required_for":"chronicle narrative generation"}]

Weft Chronicle — Builder Journey Narratives

When to Use

• User asks "tell me my project's story", "tell me the story of Weft", "what's my builder journey?", or "generate a chronicle"
• After a milestone is verified and the builder wants a shareable achievement card
• Generating creative content from onchain verification data

Concept

Weft is the horizontal thread that interlaces with the vertical warp to create woven fabric. Technology provides the warp (onchain data, peer verdicts, storage proofs). The liberal arts provide the weft (narrative, meaning, human context).

Procedure

Step 1 — Reason

Explain what a chronicle is: "A Builder Journey chronicle weaves multiple milestone attestations into a multi-chapter narrative using Kimi (moonshot-v1-128k). Each milestone is a thread in the project's fabric."

Determine which milestones to include:

• If the user specified a milestone hash, look for its attestation
• Otherwise, look for all attestations in agent/.attestations/*/attestation.json
• If no attestations exist, explain that the builder needs to verify a milestone first (use /weft-verify or /weft-workflow)

Step 2 — Run the chronicle generator

cd $WEFT_ROOT && source scripts/.env 2>/dev/null; python3 - << 'PYEOF'
import json, glob, os, sys

sys.path.insert(0, '.')
from agent.lib.kimi_client import generate_chronicle
from agent.lib.chronicle import write_chronicle, write_card, CardData

OUT_DIR = 'agent/.attestations/chronicle'
os.makedirs(OUT_DIR, exist_ok=True)

# Load real attestations
attestations = []
for path in sorted(glob.glob('agent/.attestations/*/attestation.json')):
    with open(path) as f:
        d = json.load(f)
    attestations.append({
        'milestoneHash': d.get('weft', {}).get('milestoneHash', d.get('milestoneHash', '')),
        'projectId':     d.get('weft', {}).get('projectId', d.get('projectId', 'weft-protocol')),
        'verified':      d.get('verdict', {}).get('verified', d.get('verified', False)),
        'uniqueCallerCount': d.get('evidence', {}).get('usage', {}).get('uniqueCallerCount',
                             d.get('usage', {}).get('uniqueCallerCount', 0)),
        'commitCount':   len(d.get('evidence', {}).get('github', {}).get('commits', [])),
        'narrative':     d.get('narrative', {}).get('summary', ''),
        'evidenceRoot':  d.get('evidenceRoot', ''),
        'peerSigners':   d.get(, 0),
    })

 not attestations:
    ()
    ()
    ()
    ()
    ()
    ()
    ()
    ()
    sys.exit(1)

(f)
()


chronicle = generate_chronicle(attestations)
(f)
 ch  chronicle.chapters:
    (f)
    (f)
 chronicle.epilogue:
    (f)


chronicle_path = f
write_chronicle(
    title=chronicle.title,
    chapters=chronicle.chapters,
    epilogue=chronicle.epilogue,
    attestations=attestations,
    out_path=chronicle_path,
)
(f)


att = attestations[0]
ch0 = chronicle.chapters[0]  chronicle.chapters  {}
card = CardData(
    milestone_hash=att[],
    project_id=att.get(, ),
    verified=att[],
    narrative_summary=att.get() or (ch0.get(, )[:300]),
    unique_callers=att[],
    commits=att[],
    peer_signers=att.get(, 0),
    evidence_root=att.get(, ),
    chapter_heading=ch0.get(, ),
    chapter_body=ch0.get(, ),
)
card_path = f
write_card(card, card_path)
(f)

()
PYEOF

Step 2 — Open the files in the browser

open $WEFT_ROOT/agent/.attestations/demo-node-1/chronicle.html
open $WEFT_ROOT/agent/.attestations/demo-node-1/milestone_card.html

Step 3 — Present the narrative in chat

After the files open, display the chronicle title, chapter headings, and a 2–3 sentence excerpt from the first chapter directly in the chat window. Format it like this:

🧵 Builder Journey Chronicle
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

"<chronicle title>"

Chapter 1: <heading>
<first 2 sentences of body>

Chapter 2: <heading>
<first 2 sentences of body>

Epilogue: <first sentence>

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✅ Chronicle opened in your browser.
✅ Milestone card opened in your browser.

Technology provides the warp. Liberal arts provide the weft.

Rules

• Never substitute demo data — if no real attestations exist, report what's missing and how to create them
• Always open the browser — call open <path> after generating; never leave the user to open files manually
• KIMI_API_KEY — sourced from scripts/.env automatically; do not ask the user for it

Pitfalls

• If generate_chronicle returns empty title/chapters, the Kimi key may be missing or rate-limited — the script still writes the HTML with whatever it has
• The source scripts/.env at the top loads all keys including KIMI_API_KEY; do not skip it