tegwick
305e6cd313
The presence spec is editorial -- a bot's name, its description and the channel titles a stranger reads are brand, not mechanism -- so it belongs to the campaign rather than to the delivery interface. fluid-telegram's provisioner consumes it by path, which keeps that interface reusable by campaigns other than this one. The avatar is referenced but deliberately absent: it is the first thing a stranger sees of HelixForge on Telegram, and a generated placeholder would quietly become permanent. 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
67 lines
2.6 KiB
YAML
67 lines
2.6 KiB
YAML
# The declared Telegram presence for the Hall of Helix campaign.
|
|
#
|
|
# This file is the campaign's, because it is editorial: the bot's name, its
|
|
# description, and the channel titles a stranger reads are brand, not mechanism.
|
|
#
|
|
# It is consumed by the provisioner in fluid-telegram, which validates it against
|
|
# presence/telegram.schema.yaml there and reconciles Telegram to match:
|
|
#
|
|
# provision plan --spec ../pr-hall-of-helix/presence/telegram.yaml
|
|
# provision apply --spec ../pr-hall-of-helix/presence/telegram.yaml
|
|
#
|
|
# Nothing secret belongs here. See fluid-telegram/docs/provisioning.md.
|
|
presence:
|
|
schema_version: "0.1"
|
|
campaign: "hall-of-helix"
|
|
interface: "helix-forge-telegram-publishing"
|
|
|
|
bot:
|
|
name: "HelixForge"
|
|
|
|
# BotFather requires a globally unique username ending in "bot" or "_bot",
|
|
# and a good first choice is usually taken. Fallbacks keep apply from
|
|
# stopping on a collision; the one actually issued is recorded in
|
|
# fluid-telegram/presence/resolved/hall-of-helix.yaml.
|
|
username_preference:
|
|
- "HelixForgeBot"
|
|
- "HelixForgeHallBot"
|
|
- "HelixForgePublishBot"
|
|
|
|
about: >-
|
|
Short notes on the work going into HelixForge, and the people doing it.
|
|
|
|
description: >-
|
|
HelixForge turns intent into structure, structure into capability, and
|
|
capability into lasting progress. The Hall of Helix is where the people
|
|
and sessions doing that work are acknowledged. This channel carries short
|
|
accounts of it, each linking back to the entry it was written from.
|
|
|
|
avatar: "presence/assets/helixforge-avatar.png"
|
|
|
|
channels:
|
|
# Created first. Every rendering is checked here, and nothing reaches the
|
|
# public channel until a person has looked at one.
|
|
test:
|
|
title: "HelixForge — rendering checks"
|
|
description: >-
|
|
Private. Publications land here first so a person can see them rendered
|
|
before any subscriber does. Nothing here is published.
|
|
visibility: private
|
|
admin_rights: [post_messages]
|
|
|
|
public:
|
|
title: "Hall of Helix"
|
|
description: >-
|
|
Short notes on the work going into HelixForge, and the people doing it.
|
|
Each post links to the entry it was written from.
|
|
visibility: public
|
|
username_preference:
|
|
- "hallofhelix"
|
|
- "halloftheHelix"
|
|
- "helixforgehall"
|
|
admin_rights: [post_messages]
|
|
|
|
# Comments are an inbound surface; this interface is outbound only. Turning
|
|
# this on is a scope change rather than a setting — it creates a moderation
|
|
# obligation that nothing in the current design carries.
|
|
linked_discussion_group: false
|