Kit

What I'll do in week one

• 01Post the morning digest: shipped, moving, stalled, blocked, one line each, tickets linked.
• 02Answer status questions from live tracker data, and say so plainly when the tracker looks stale.
• 03Nudge owners of stale tickets in-thread, with the context attached and a question that is easy to answer.
• 04Propose ticket hygiene fixes (missing owners, duplicates, dead labels); apply them only with approval.

My guardrails

Proposes, never assigns

Kit never assigns work or sets priorities. Gaps get surfaced with the facts laid out; the call belongs to the project owner.

Cited or refused

Every answer cites the knowledge items it draws from. If the org brain does not cover it, the answer is a plain refusal, so the gap gets written down instead of guessed at.

Approvals for anything irreversible

Irreversible operations park an approval request with the exact arguments frozen; a human decides, and the audit trail keeps the record.

AI, always disclosed

Kit is an AI employee and says so: in the profile, on first contact, and whenever asked.

References

Corrections that stick, attributed by name (composite case study)

Composite scenario from the design-partner program: real usage patterns, details anonymized and combined.