Forge AGENTS

Forge is an agentic system for building, automating, documenting, and running organizations. It is the single source of truth for organizational vision, plans, procedures, agents, and operating knowledge.

Accessing Forge

1. Open os.uvilo.com and log in with your team credentials.
2. Select the Forge Chat Bot.
3. Use Forge Chat for general work; when you mention a project or ask for project lifecycle work, it hands off to Project Runner.

Key Files and Systems

• Forge Chat prompt — Database prompt forge/chat; primary interactive entry point and routing contract.
• Forge Charter — Values, goals, scope, and constraints.
• Forge Project Workflow — Canonical lifecycle, phase ownership, context boundaries, todos use, human gates, project identity, and extraction rules.
• Forge Project User Guide — Human-facing guide to creating, steering, approving, and completing projects.
• Forge Agent Orchestration — Scheduling, spawning, monitoring, recovery, and task/project routing.
• Forge Infrastructure — Deployment, env vars, services, tool configuration, and operational gotchas.

Reference Docs

• Forge Agent Architecture — System prompt pipeline, memory architecture, agent management.
• Forge Agents User Guide — How to use workflows, create new ones, and schedule agent execution.
• Forge Content System — Content inclusion, page generation, writing conventions.
• Forge Document Structure — File naming, folder hierarchy, sidebar conventions.
• Forge Markdown Syntax — Markdown conventions supported by the docs site.
• Forge Setup — Step-by-step rebuild instructions and disaster recovery.

Where Files Go

Type of work	Folder
Platform infrastructure and agent-system projects	Forge/Projects/
Project workflow docs, templates, and lifecycle skills	Forge/Forge_Project/
Reusable platform skills	Forge/Skills/
MCP/runtime configuration	Forge/Configs/
Product design, specs, quiz work	Product/Projects/
Business-level docs	Department folders such as Finance/, Marketing/, Operations/

Skills

• Platform-wide reusable skills live in Forge/Skills/.
• Project lifecycle skills live in Forge/Forge_Project/Skills/. Use these for project Create, Vision, Research, Spec, Plan, Execute, Verify, Extract, Complete, Archive, Delete, and Rename phases.

Projects

Platform projects live in Forge/Projects/ and follow the Forge Project Workflow. Project identity uses the canonical display form {Department}/{ProjectShortName} and the filesystem slug {Department}_{ProjectShortName}.

Project recovery comes from the Phase file, durable work-products, persisted evaluation or verification reports, Execute_State files, saved conversation/AgentJob metadata, git status, and relevant todo items. Do not create or rely on WIP files. Human decisions and agent follow-up are routed through the todos tool group with durable work-product or report links.

Key Principles

• Git is the source of truth for repository documents; commit work to the dev branch.
• Never merge to main without explicit instruction.
• Durable work-products are the communication layer for project work.
• Human sovereignty matters — agents can recommend, but humans decide material scope, trade-off, and approval questions.
• Extract before completion — hard-won knowledge must move out of project folders into permanent Knowledge, Skills, Guides, or Prompts.

Troubleshooting

• Need project status or approval? Ask Forge Chat about the project; it routes to Project Runner.
• Agent making a scope assumption? Correct it. Scope decisions belong to the user/project owner; agents should record unclear scope as a pending decision, not silently mark it out of scope.
• Something broke? Describe what happened; Forge can diagnose and update durable work-products.
• Don’t know where a file should go? Ask Forge or spawn the Page Manager bot via spawnAgent with { botGroup: 'forge', botHandle: 'page-manager' } for page operations.
• Urgent infrastructure issue? Check Forge Infrastructure or reach out to Erik.