WFM Labs Hub — Documentation

Project documentation for the WFM Labs community platform at community.wfmlabs.com.

Contents

Document	Purpose	Updated
Architecture Overview	System architecture, stack decisions, integration points	Living document
Changelog	What changed, when, and why	After every meaningful session
Status	Current build status, what works, what doesn't	After every session
Data Model	Collection schemas, relationships, access control	When collections change
API Reference	Payload REST/GraphQL endpoints, custom routes	When API changes
Deployment	How to deploy, environment setup, Vercel config	When deployment changes

For Ted

The two documents you'll check most often:

1. Status — What's working, what's broken, what's next. Updated after every TARS session.
2. Changelog — Chronological record of every change. Scan this to see what happened since you last looked.

For TARS

Update status.md and CHANGELOG.md after every session that changes the system. Architecture and data model docs update when those systems change. These docs are the public-facing complement to MEMORY/ (which is TARS-internal).