status

You can check FIRE project status by scanning state.yaml and on-disk artifacts to compute a live status snapshot. This validates the status cascade across work items, intents, and runs to detect any drift or gaps in your project.

A FIRE project status cascade enforces status consistency from work items to intents to the project level. You should validate it when you suspect drift between your state.yaml file and actual artifacts on disk.

You detect drift by reading state.yaml and scanning on-disk artifacts like intents, work items, and runs. This comparison surfaces inconsistencies in frontmatter and project state, providing a structured report of any issues.

Yes, you can remediate state.yaml inconsistencies interactively. The process guides you through resolving issues, logging maintenance activities, and updating state to ensure your FIRE project status remains accurate.

Yes, FIRE project status validation applies to both development and production environments. It surfaces drift in intents, work items, and runs regardless of the environment to guide necessary remediation.

Your FIRE project status shows frontmatter consistency issues when on-disk artifacts do not match the expected metadata defined in state.yaml. The validation process verifies frontmatter and reports these issues with suggested fixes.