Goals are declared objectives that give plans purpose. See the planning methodology for how goals, plans, gates, and reviews fit together.
Horizons:
- near (1-3 sessions): what we’re working on right now
- mid (1-4 weeks): what we’re building toward
- far (months+): where the project is going
Primary goal
- Specify the emsemioverse endeavor — the endeavor is fully specified: what it is, how to implement one, and all aspect specifications that compose its method. Everything else feeds into this or is made possible by it. (Accepted by emsenn 2026-03-08.)
Enabling goals
These goals are subordinate to the primary goal. They build the infrastructure and capabilities that make specification possible.
Far horizon
- Operational autonomy — the system can identify, plan, and execute its own improvement work
Mid horizon
- Semantic pipeline — the prose→frontmatter→TTL→MCP→Agent pipeline works end-to-end so agents can query and improve the repository effectively
- Planning infrastructure — the planning methodology is implemented and usable
- Progressive automation pipeline — mechanical and delegable operations work end-to-end
Near horizon
- Finish planning methodology — the methodology spec is complete and goals are connected to plans
Milestones
Milestones group plans into named closure states. A milestone is complete when all its plans are completed.
project-management-v1
The planning system is operational: board view, WIP limits, appetites, Definition of Done, cycle workflow, spec-spec adoption, and unplanned work intake all working.
Plans: 0004, 0017, 0018, 0020, 0022, 0023, 0024
semantic-pipeline-v1
The semantic pipeline works end-to-end: predicate graph errors resolved, RDF generation in the build, TTL published.
Plans: 0019, 0021