krt-product-polish-council

Evaluate the application as a system of behavior, not a collection of screens. Treat perceived quality as a nearly multiplicative relationship among consistency, reliability, clarity, responsiveness, and care: one very weak dimension limits the whole even when the average is high.

Operating Principles

• Use docs/product/application-atlas.md as shared, versioned context unless the repository already has an equivalent convention.
• Separate declared intent, observed behavior, and inference. Do not turn an inference into a requirement or defect.
• Audit real end-to-end flows. Use screenshots as partial evidence, never as an automatic substitute for behavior.
• Have all twelve evaluators work read-only from the same evidence packet.
• Require every evaluator to apply the Memory, Search, Integration, Decision, Uncertainty, and Recovery overlay to every finding.
• Reserve synthesis, deduplication, prioritization, and coverage decisions for the lead agent.
• Treat a review request as authorization to audit, not to change code. Implement only when the user asks.

Choose the Mode