ForgeBot Channel Context / #forgelab

ForgeLab Channel Context

A durable working map for the Slack channel that supports ForgeLab: ForgeFX's microprojects sandbox, live lab URLs, prototype navigation, proof-of-concept links, and quick app/version/deploy checks.

Readable by ForgeBot Public Slack Channel Last Reviewed 2026-06-30
6

Top-Level Messages

Full visible channel history was sampled at the initial context build.

3

Replied Threads

Threads cover app identity, current source version, POC navigation, and this context build.

4105

Local Dev Port

ForgeLab runs locally on port 4105 through the app's Vite dev server.

Executive Summary

What This Channel Knows

#forgelab is the Slack context channel for ForgeLab, ForgeFX's microprojects sandbox app under /Users/forgebot/forgeapps/apps/forgelab.

The channel began with Adam asking ForgeBot to identify the lab site, check the ForgeLab app version, move the POC navigation item, and build durable context.

Current stance: use this context to answer ForgeLab questions quickly, but still verify live/source state before claiming deployment, version, or UI changes are complete.
Verified Working Facts

Source, Live URLs, And Nav State

App Purpose

Microprojects sandbox and experimentation workspace for one-off demos and proof-of-concept apps.

POC Navigation

The POC link is now second in the primary navigation, immediately after Home.

Recent Timeline

How The Context Was Built

2026-06-30
ForgeLab identity: Adam asked what the lab URL is. ForgeBot identified it as the ForgeFX prototype and microproject sandbox.
2026-06-30
Version check: source metadata showed 2026.06.28.6. A prior live header observation showed an older visible value, so live/source version display should be rechecked when accuracy matters.
2026-06-30
Navigation request: Adam asked to place POC second after Home. Source now reflects that order.
2026-06-30
Durable context: the full channel folder was created and registered for future ForgeBot sessions.
Runbook

How ForgeBot Should Use This Channel

Before Answering

Load the local channel folder first, then read app-local context when the question touches source, build, route, version, or deployment state.

Version Questions

Read package metadata first. If live accuracy matters, inspect both public URLs and report source and live versions separately.

Deploy Questions

Push-to-GitHub is the only deploy path. Never use Vercel CLI, Vercel API, or direct deployment commands.

Files Written

Durable Context Folder

  • CHANNEL.md — identity, app link, bot policy.
  • MEMORY.md — stable facts.
  • STATE.md — current working context.
  • PEOPLE.md — participant map.
  • DECISIONS.md — durable decisions.
  • TASKS.md — open checks and verified work.
  • THREADS.md — important thread index.
  • SOURCES.md — links and source paths.
  • RUNBOOK.md — repeatable workflow.
  • SUMMARY.md — readable digest.