Processes, Roadmaps, and Clearer Planning Structure

Planning now separates recurring processes from living documents, with new agents starting from a real roadmap instead of a blurred boundary between the two.

Planning is now clearer about what belongs where. The system distinguishes more cleanly between execution rhythm and evolving context, which makes long-lived agents easier to steer.

Processes Define The Rhythm

PROCESS entities now stand more clearly for recurring execution patterns: what should run, and how often.

Documents Hold The Story

Living context belongs in documents like ROADMAP.md and HEARTBEAT.md, where goals, priorities, and working notes can evolve without being confused for automation rules.

New Agents Start With A Better Shape

New agents now begin with a real roadmap document in place, and the heartbeat flow is nudged to review it. The result is a stronger default structure for agents that need to think over time, not just execute once.