Skip to content

DEVELOPMENT / PROJECT ARCHITECTURE

Understand the System Before You Change It

Trace a project flow from its sources, identify the contracts between components and save what the evidence supports. In a later chat, your agent can find that knowledge, compare source versions and explain who a change would affect.

A WORKED ARCHITECTURE EXAMPLE

A Saved Contract Meets a New README

We tested this cycle with Maple Import, a small fictional CSV-import command.

SCATTERED CONTEXT

Where Is the Agreement?

A README describes the import flow, but the next question needs a precise answer. What happens to an invalid row? When can the ledger writer run? The agent needs the source and its version to establish which behavior is documented.

CHANGING SOURCES

Which Details Still Hold?

A newer README changes the error message and removes the row number. Reusing the old description without comparison would carry that outdated detail forward. The earlier contract needs to remain identifiable while the new version is examined.

RETRIEVE AND COMPARE

Keep the Contract and Its Evidence

Project Architecture guides the agent to save a bounded contract with its source version, known behavior and open questions. Components, decisions and evidence can be connected where those relationships help the next question.

In the Maple Import check, a fresh agent found the saved contract and compared it with README v2. It identified the changed error response and the guarantees that still held.

The comparison stayed read-only. The saved contract remained available for a later, deliberate update.

Video coming soon

We’re preparing a walkthrough for this section.

WHY IT WORKS

Project Knowledge You Can Check and Reuse

Keep the evidence behind each claim. Follow the relationships that matter for the next change.

SOURCE AND VERSION

Know What Is Established

A README, inspected code and a runtime check establish different things.

Record the source, version and limits of each claim so the next agent can see what still needs verification.

COMPONENT CONTRACTS

Trace the Consequences

A changed input can affect its producer, callers and stored data.

Use connected component and contract records to follow the relevant flow and choose a focused check.

LATER QUESTIONS

Return to What You Learned

The useful result stays in your project base between conversations.

A new chat can find the same contract, compare new material and explain which earlier conclusions still apply.

TRY IT YOURSELF

Start with One Project Flow

Try a source excerpt or the Reading List exercise, then save one useful contract. Need to install Lorebo or connect your agent? Get Started

Open Project Architecture in Templates → Development. Create and name a copy for your project, then activate it and read Start Here.

Video coming soon

We’re preparing a walkthrough for this section.

Frequently Asked Questions

Good to Know

Can I start in Free?

Yes. Select an empty, writable local base and use Replace Active Base. Lorebo makes a recovery backup. Pro also lets you register a separate working copy.

What’s in the template?

Methods for tracing flows and reviewing changes, formats for components, contracts, decisions and debt, plus the fictional Reading List exercise and an agent startup instruction.

How does my agent find the project knowledge?

Start Here gives you prompts that direct the agent to the startup instruction. The agent then reads your project context and relevant records, checking their sources and versions. MCP Setup Instructions

Can one project include several repositories?

Yes. Keep the repositories that belong to one system in the same project context. Identify each source and its revision separately, then trace the boundaries relevant to your question.

Does activating the template make it writable?

Activate opens the template for reading. Create a working base from it to save your own project knowledge, as shown in Try It Yourself

Do I need source code for the first question?

A permitted README excerpt or project description is enough to try a bounded analysis. The agent records what that source establishes and leaves implementation details unknown until checked.

What happens when documentation and code disagree?

Keep the documented expectation and observed behavior with their respective versions. The agent identifies the discrepancy and the next check. An accepted decision and verified implementation remain separate.

Will a template update replace my project records?

Your working copy is independent. Updating the downloaded template leaves it intact. When you choose to apply new instructions, reconcile the copy while preserving its decisions, records and archive choices.

A person studies and draws a dimensioned rocket plan at an angled drafting table, with a task lamp and rolled blueprints beside it.

Start with one source, trace a flow and keep a contract you can return to in the next conversation.

Privacy choices

Choose whether to allow optional cookies.