pi-project

Schema-driven project state validation checks typed JSON blocks like project.json and tasks.json against predefined schemas, enforcing data integrity and cross-block referential consistency before writes are committed. This ensures lifecycle planning and state accuracy.

JSON schema-based project lifecycle management coordinates state blocks like decisions.json and verification.json to derive status and enforce planning consistency. You need it when your project requires structured, validated state transitions and cross-block referential integrity within a .project directory.

To initialize a .project directory, run the bootstrap process to generate typed JSON schemas and state blocks like project.json and tasks.json. After initialization, inspect the current derived state and lifecycle status using the project status command.

Yes, cross-block referential integrity is enforced by validating writes against JSON schemas, ensuring that state blocks like tasks.json and decisions.json maintain consistency and that derived status and references align across the entire project lifecycle.

Yes, pi-project supports atomic schema-based writes, ensuring that updates to state blocks like project.json and verification.json conform to typed JSON schemas and maintain data integrity during the planning lifecycle without partial updates.

Schema-driven project state management is limited to projects organizing state in a .project directory with specific JSON blocks like project.json and tasks.json, meaning it may not suit projects with unstructured state or those not using typed JSON schemas for lifecycle planning.