working note: a text-first checklist for using Kimi K3 on a long project packet. this is a preparation and review routine, not a benchmark.

• name the decision first
  • write one question the packet must answer
  • remove pages that cannot change that decision
• build an approved evidence packet
  • include checked notes, policy excerpts, and prior decisions
  • leave out private messages, credentials, unrelated customer data, and personal journals
• redact before upload
  • replace names, emails, account numbers, internal urls, and tokens with stable labels
• label every excerpt
  • add source title, section, and date so each claim can be checked later
• set the evidence rule
  • ask for a source after every factual conclusion
  • require NOT IN PACKET when the supplied text does not support a claim
• separate the output
  • verified facts
  • decisions already recorded
  • open questions
  • draft actions that still need approval
• review against the source
  • reject invented owners, dates, commitments, or missing events
• keep the last action human
  • no email, approval, policy change, or task assignment until a person checks the cited passage

reference: official Kimi model guide

working note: for Kimi K3 at work, the useful constraint is the boundary around the packet, not simply how much text fits.