25 lines
667 B
Markdown
25 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.
|