渐入默契
它已经懂你团队的多数脉络,正在学习你的偏好。
记忆等级不是静态分数,而是用协作证据持续校正 Kiki 的理解边界:它看到了多少、理解是否成立、信息是否仍然新鲜。
每次跃迁都能讲清原因:确认了 12 条流程、纠正 3 处误解、连续 3 周高频协作。理解过期时等级会局部回落,AI 主动说“这块我需要重新确认”——会承认变笨,反而更可信。
它已经懂你团队的多数脉络,正在学习你的偏好。
点任意一项,看它具体记住了什么。
Action · What it did · How well it gets you
Counts everything Link triggered, not only what I ran directly.
Value to you
Smart-reply / meeting / option picks you accepted
Tasks Kiki completed from your asks
Estimated manual work avoided this week
Suggestion adoption is high, so repeated meeting follow-ups can move from ask-first to auto-run.
Value to your team
Your deliveries accepted by teammates without rework
Docs, tables, briefs, and demos shared into team work
Flows copied or rerun by other people
Team acceptance is high enough to package the feedback-import Flow for the product group.
Work taken off your plate
Updates that ran through Tanka instead of manual tool work
Repeatable routines Kiki helped turn into reusable SOPs
Most recurring updates now pass through Flow. The next lift is routing more Docs and Notion updates through Kiki.
What Kiki leaves behind
Later work referenced SOPs or decisions Kiki helped create
Other agents reused Kiki-created context or SOPs
Kiki outputs promoted into shared team practices
Frequently referenced SOPs can be promoted so other agents and teams inherit the same working pattern.
AI 是否看到了足够多的信息
68%coverageAI 是否能带着完整上下文工作
72%scoreBased on 18 recent work plans · 64 steps checked
Kiki found recent changes that may affect its memory. They become reliable once confirmed, linked, and applied.
Detected, but not yet confirmed as reliable memory
Found in Slack, not confirmed in project docs
Found in meeting notes, no linked artifact
New values in Figma, source not refreshed
Hinted in a finance thread Kiki can't open
Kiki found two versions while preparing the renewal Flow.
needs confirmationBudget memory resolved. Kiki will use the confirmed value in renewal Flows.
Completeness and freshness signals update after this memory is used.
24 decisions captured · 3 missing rationale · 2 missing owners
Per-level bars made users feel audited rather than understood. One score reframes the panel as “how much Kiki gets it” instead of a checklist of faults.
Decision rationale will be attached to the related work memory.
Kiki can use it after the decision is referenced in a real Flow.
11 threads captured · 4 missing arguments · 2 unresolved alternatives
Discussion threads will be connected to decisions and rejected options.
Kiki can explain how the team argued to a conclusion after indexing finishes.
6 major work changes captured · 2 missing turning points
Missing work memory will be connected to this project history.
Kiki can explain the path from early proposal to current version.
14 meetings linked · 3 discussions missing · 2 attendees out of scope
Meeting notes and transcripts will be mapped to related decisions.
Completeness improves after Kiki uses them to answer or run a Flow.
Missing links: Discussion → Decision, PRD → Design, Decision → Demo
Related artifacts will be connected into one story chain.
Kiki can trace from discussion to decision to output after verification.
24 flows · 91% completed · 2 corrections
13 flows · 72% accepted · BI source unlocked
18 flows · 81% completed · 4 owner changes
29 meetings · 84% actions accepted · 1 correction
9 flows · 61% accepted · needs stronger source coverage
12 flows · 70% accepted · Jira linked
7 flows · 56% accepted · GitHub pending
Drive / Docs · create briefs, PRDs, and notes
Kiki can create a new document from Flow context, meeting notes, or a prompt.
Tanka Chat · send a DM or group message from Flow context
Kiki can send a Tanka message after confirming recipients, wording, and source context.
Memo · write meeting notes, team wiki, or collaboration memo
Kiki can turn meetings, Flow outcomes, and chat decisions into a structured memo.
Tanka Chat · start a group with people and Flow context
Kiki can create a focused group chat, add relevant teammates, and attach the Flow summary.
Gmail · send approved follow-ups and outreach
Kiki can send an email after preparing recipients, context, and final copy.
Gmail · prepare email drafts before approval
Kiki can write a draft and leave it for review before anything is sent.
Gmail · reply with context from Flow and memory
Kiki can answer from recent Flow context, prior decisions, and linked docs.
Calendar · create meetings, guests, and agenda
Kiki can create calendar events with agenda, invitees, and related Flow context.
Calendar · change time, guests, or attached context
Kiki can update meeting details when Flow context changes or owners shift.
Slack · send internal reminders and updates
Kiki can send Slack reminders, status updates, or owner nudges.
Slack · acknowledge updates without a message
Kiki can acknowledge routine updates without interrupting the thread.
Jira · turn Flow outputs into tracked issues
Kiki can create a Jira issue from approved Flow output and linked evidence.
emails, drafts, outreach context
meetings, availability, reminders
channels, decisions, team context
docs, decks, research artifacts
issues, releases, validation progress
meeting notes, team wiki, decisions
market research and public signals
Codex and Claude Code output memory
Connect the required tool first. Then Kiki can use this capability in real work.
Issues, milestones, owners, blockers, and release progress.
requiredKiki can start a Flow that tracks risk, summarizes changes, and asks you only when a decision is needed.
newResult data linked & indexed. Kiki has indexed enough work results to connect meetings, documents, messages, and Flow outcomes.
Link the missing tools Kiki needs to close source gaps.
Request view access for Memo docs Kiki cannot read yet.
Choose what Kiki should learn from next.