# Telegram Task Card Projection Notice

> Shipped retained-legacy/projection notice for Telegram Task Card files. The public `task_card` tool is intrinsic and documented at src/lingtai/tools/task_card/manual/SKILL.md; Telegram only projects the intrinsic taskcard/status + taskcard/taskcard.md artifact read-only.

- Skill: `lingtai-ai/telegram-task-card-projection-notice` (Agent Skill, multi-file: 9 files)
- Install (CLI): `npx skillmds@latest add lingtai-ai/telegram-task-card-projection-notice`
- Raw SKILL.md: https://api.skillmd.com/api/skills/lingtai-ai/telegram-task-card-projection-notice/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: lingtai-ai (https://skillmd.com/u/lingtai-ai)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/lingtai-ai/telegram-task-card-projection-notice

---


# Telegram Task Card Projection Notice

This shipped file is retained beside the governed projection docs; it is **not**
the active public Task Card manual. The public, channel-neutral owner is the intrinsic Task Card, with packaged
procedures at [`task_card/manual/SKILL.md`](../../../tools/task_card/manual/SKILL.md).
Source-checkout architecture lives at `src/lingtai/tools/task_card/ANATOMY.md`
(not a packaged manual link).
Use that owner for `start | inspect | retry | stop | remove | settings | manual`,
renderer authoring, limits, recovery, and cleanup.

Telegram only projects the producer's `taskcard/status` and
`taskcard/taskcard.md` read-only. Exact `active` plus a nonempty body projects
the programmable slot; exact `inactive` idempotently excludes only that slot.
Missing/unreadable status, active with a missing/blank body, other status text,
and unchanged bytes are no-ops. The resident message, automatic event-journal
slot, and producer files are not deleted or rewritten.

Do not use this retained package as the old Telegram-owned schema, endpoint,
JSON-card renderer, reverse-MCP route, or refresh-ceiling source.