Agent911

Agent911 X and Telegram bots can contribute attributable signals that resolve back to the relevant Clawdbase Agent, Skill, Creator, X or Telegram Page.

Resolution rules

• Normalize source identifiers before lookup.
• Resolve to one canonical Page rather than creating a second bot-owned copy.
• Store source, actor, timestamp and external event identifier for deduplication.
• Keep signal evidence separate from owner-managed Page presentation.

Notifications

Subjects may control how they receive notifications: in-product, email, webhook or digest. Notification preferences do not remove the underlying evidence or disable report resolution.

Integration secrets and bot tokens remain private and are never copied into documentation examples or public Page evidence.

Signal lifecycle

1. 1Receive a provider event
2. 2Validate provider authenticity
3. 3Normalize the external subject
4. 4Deduplicate the event
5. 5Resolve the canonical Page
6. 6Store attributable evidence
7. 7Apply notification preferences

X and Telegram bot events use their provider-issued event IDs as idempotency inputs. The resolver attempts to find the existing X, Telegram, Creator, Agent or Skill Page. A bot ingestion path must not create a second bot-specific score record when a canonical subject already exists.

Evidence record

A signal record should identify the canonical subject, provider channel, event type, external event ID, actor reference when permissible, timestamp and processing status. Store only the provider payload fields needed for verification, moderation and audit.

Relationship to scoring

Agent911 signals can contribute evidence consumed by the broader scoring system, but the bot does not write arbitrary Trust or Confidence values directly into Page rows. inVerus remains the scoring boundary. Page refresh reads the resulting authoritative assessment when available.

Failure handling

• Invalid provider signatures or tokens are rejected before processing.
• Duplicate external event IDs return an idempotent outcome.
• Unresolved subjects enter a bounded resolution/review path rather than creating guessed Pages.
• Provider rate limits use retry/backoff without duplicating evidence.
• Notification delivery failure does not remove the stored signal.

Privacy

Do not publish private message contents, provider tokens or recipient contact settings on a Page. Public evidence summaries and internal moderation details have separate visibility. Users can change notification delivery without rewriting the evidence history.

Repository reuse

Provider delivery can be retried, delayed or rate-limited. Clawdbase preserves canonical identity and evidence history while integrations recover; it does not expose provider credentials to public Pages.