tegwick
1f218fa5ae
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014KmVxhJ35tCo7rE7UnLwWu Assistant: claude-code Assistant-Model: opus Assistant-Process: 1116572@bnt-lap001 Assistant-Session: 8ba9bb93-a72a-4883-b189-2499cce5c400
24 lines
667 B
Markdown
24 lines
667 B
Markdown
---
|
|
repo: fluid-telegram
|
|
updated: "2026-09-04"
|
|
---
|
|
|
|
# INTENT
|
|
|
|
## Why it exists
|
|
|
|
Fluid interface for telegram messaging and interaction platform.
|
|
|
|
Fluid interface for telegram messaging and interaction platform.
|
|
|
|
## Governing principle
|
|
|
|
This repository should stay focused on the purpose above. Work that changes its
|
|
authority, ownership boundaries, or operational promises should be captured in a
|
|
workplan before implementation.
|
|
|
|
## What it enables
|
|
|
|
- A coding agent can understand why the repository exists before changing it.
|
|
- State Hub can register and coordinate work for this repository.
|
|
- Future workplans can stay connected to the repository's intended role.
|