Skip to content
Zeitlines

Plugins give each plan its own language

A plugin adds the fields, views, stored data and tools a planning domain needs. It is enabled per timeline, so the catalogue can grow without turning the core into one large planning suite.

Shipped plugins

Four plugins are included in the repository today. Each page names its current capabilities and limits.

Product and roadmaps

Projects and delivery

Lifecycle and obsolescence

What plugins can contribute

A versioned contract

Every plugin declares its identity, compatible host range and required capabilities. The host validates that manifest before loading the plugin. Unused built-in plugins stay in separate build chunks and load only for timelines that enable them.

Build on the platform

The authoring reference defines the external artifact and host API. The playbook covers domain research, implementation and publication. Current runtime limits are recorded in the repository with the contract.