tegwick
3431a6eb91
Domain infotech, workplan prefix PRHOH-WP-. Adds the generated integration files; the bootstrap workplan is dropped for the same reason as elsewhere. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0172sgCZEEDJcnQmr4SGDvKa Assistant: claude-code Assistant-Model: opus Assistant-Process: 1361245@bnt-lap001 Assistant-Session: b3b428ef-f3e6-4688-b091-01f71461d66a
24 lines
820 B
Markdown
24 lines
820 B
Markdown
---
|
|
repo: pr-hall-of-helix
|
|
updated: "2026-09-04"
|
|
---
|
|
|
|
# INTENT
|
|
|
|
## Why it exists
|
|
|
|
Public-relations campaign that composes and publishes posts about hall-of-helix work through the fluid-telegram interface.
|
|
|
|
The public-relations campaign that turns `hall-of-helix` work into published posts. The `pr-` prefix marks it as a campaign repository rather than a service.
|
|
|
|
## 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.
|