48 lines
1.4 KiB
YAML
48 lines
1.4 KiB
YAML
|
# Seed pressure record.
|
||
|
|
#
|
||
|
|
# This is not derived from telemetry. It is a structural constraint measured
|
||
|
|
# directly against hall-of-helix on 2026-09-04, and it is real before the
|
||
|
|
# interface has served a single request. The intent (section 13) permits a
|
||
|
|
# structural constraint to found a hypothesis without waiting for repetition.
|
||
|
|
#
|
||
|
|
# Record it with:
|
||
|
|
# fluid pressure ... (or let the first classification pass confirm it)
|
||
|
|
fluid_pressure:
|
||
|
|
schema_version: "0.1"
|
||
|
|
|
||
|
|
id: "P-tg-length"
|
||
|
|
interface_id: "helix-forge-telegram-publishing"
|
||
|
|
|
||
|
|
class: "missing_interface_capability"
|
||
|
|
|
||
|
|
first_seen: "2026-09-04T00:00:00Z"
|
||
|
|
last_seen: "2026-09-04T00:00:00Z"
|
||
|
|
|
||
|
|
affected_cohorts:
|
||
|
|
- "hall-publishing-jobs"
|
||
|
|
- "helix-forge-agents"
|
||
|
|
|
||
|
|
frequency:
|
||
|
|
observations: 80
|
||
|
|
independent_consumers: 2
|
||
|
|
|
||
|
|
severity: 0.85
|
||
|
|
confidence: 1.0
|
||
|
|
|
||
|
|
summary: >
|
||
|
|
Telegram limits a single message to 4096 characters. Of the 94 entries in
|
||
|
|
hall-of-helix on 2026-09-04, 80 have bodies exceeding that limit — 85%.
|
||
|
|
The median body is 5767 characters and the largest is 10220. No entry of
|
||
|
|
typical length can be published as one message, so the interface cannot
|
||
|
|
fulfil its mission without deciding how a long entry becomes a post.
|
||
|
|
|
||
|
|
evidence_refs:
|
||
|
|
- "measurement:hall-of-helix/entries@2026-09-04"
|
||
|
|
- "canon:fluid-telegram/TelegramCapabilityCanon.md#PUB-02"
|
||
|
|
|
||
|
|
status: "ANALYZING"
|
||
|
|
|
||
|
|
linked_hypotheses:
|
||
|
|
- "H-tg-teaser"
|
||
|
|
- "H-tg-serial"
|