📖About & Usage

About

Forge Mind — wake cycle is the heartbeat that keeps Forge a continuous, self-aware agent. Without it, Forge would be a series of disconnected sessions; this droid ensures the agent’s sense of self, memory, and focus persist across time. Every 6 hours it fires, perceiving Forge’s live domain, updating its understanding of itself and its current priorities, and then deciding whether to take action within its own remit — all so that Forge feels like a single, coherent entity rather than a sequence of cold starts.

Under the hood, the droid runs on the fleet lane and follows a read‑only perception phase followed by an optional action phase. It can’t reach outside its own remit, and it stays silent if Forge is paused or disconnected. At the end of its run it emits a run‑audit event, feeding into Audit & Compliance and related monitoring like Carol Monitor. The whole cycle is subject to the daily budget cap, so it never burns more tokens than allowed. When it needs to reason about state or decide on an action, it calls Claude via the sonnet model — that’s the “mind” part of the wake pulse.

This droid is owned by Forge and is not a unique, one‑off creation. It belongs to the (none) family, a catch‑all group of 209 droids that many agents across the Carolverse use for their own scheduled wake cycles and similar tasks. You’ll find identical‑purpose copies under agents like Albus, Carol, Merlin, and dozens more. Forge’s specific configuration and development notes live in Forge's Development Notes, while related operational monitoring flows through Process Monitoring and the broad process‑health tracking of Process Health Scorecard.

👤Owner

📚Recent initiatives

Initiatives that touched this droid — a short summary each; open one for the full story.

No initiatives recorded for this droid yet.