FX
ForgeFX Simulations · ForgeBot Context
Role reframe · 2026-07-01
Channel Context Summary

#greg_
forgebot

A private ForgeBot collaboration channel centered on Greg Meyers as the primary user. ForgeBot is the primary worker. Adam Kane is tech support and owner-admin escalation.

1
primary user: Greg
1
primary worker: ForgeBot
1
tech support: Adam
0
raw private dumps in memory

What This Channel Is For

Use this channel to support Greg on ForgeFX business work: sales-lead triage, post and LinkedIn support, creative brief generation, generated media, ForgeFX-branded assets, Fireflies/ForgeSIM lookup, and assistant workflow continuity.

Working rule: Greg is the center of gravity. ForgeBot owns execution and verification. Adam provides tech support, debugging, unblocking, and owner-admin authorization.

Role Model

  • Greg Meyers — primary user.
  • ForgeBot — primary worker.
  • Adam Kane — tech support / owner-admin escalation.
  • AdamoBot — separate legacy context.

Reviewed Themes

  • fish-fry sales-lead triage.
  • Emails and attachments for sales qualification.
  • Creative brief and concept-image skill work.
  • LinkedIn and post support.
  • Generated media, ForgeMedia, and ForgeFX design variants.
  • Fireflies / ForgeSIM quote lookup.

Escalation Rules

  • ForgeBot works first and verifies.
  • Adam helps when tooling, access, or policy blocks ForgeBot.
  • Adam still authorizes gated actions.
  • Do not make Adam the default worker for Greg requests.

Important Operating Memory

TriggerRouting
Lead email or attachmentForgeBot loads fish-fry, uses source material, and verifies the triage output.
Post or LinkedIn requestForgeBot drafts/prepares first; confirmation is required before any external posting.
Media or concept image requestForgeBot loads forgemedia and forgefx-design-system; verify uploads/outputs.
ForgeSIM / Fireflies claimsForgeBot inspects original source systems before making claims.
Tooling/access/policy blockerEscalate to Adam as tech support / owner-admin.

Backfilled Files

FileRole Reframe Added
CHANNEL.mdFrontmatter and operating rules now say ForgeBot is primary worker and Adam is tech support.
MEMORY.mdStable roles and preferences now make ForgeBot responsible for execution, follow-through, and verification.
STATE.mdCurrent stance now says ForgeBot works first; Adam is escalation.
PEOPLE.mdRole table now lists ForgeBot before Adam as primary worker.
RUNBOOK.mdResponse routing now starts with ForgeBot execution and only escalates Adam for tech-support blockers.