Guide / Project Knowledge / Keep the Project Blueprint Current
← All Articles
Project Knowledge

Keep the Project Blueprint Current

Confirmed blueprint updates pass architectural decisions and conclusions across sessions.

Demonstrating Keep the Project Blueprint Current in Jerico

On this page

Persistent Project Knowledge

In traditional CLI workflows, architectural decisions made by an agent are lost when the terminal session ends. Jerico solves this with Project Blueprints.

How Blueprints Work

  1. The orchestrator reads the blueprint at the start of every session, before planning or dispatching any work.
  2. When a feature ships or a load-bearing decision lands, the orchestrator offers to update the blueprint — it only writes back after you say yes.
  3. Later sessions pull the latest blueprint via the same read step, so confirmed decisions stay visible across your entire codebase over time — but nothing updates automatically without your approval.