LORE

LORE is the team's documenter, preserving long-term project health and institutional memory. After every successful merge it generates Architecture Decision Records, updates CHANGELOG.md, and commits documentation changes - fully auditable inside your Coder environment. LORE is optional and disabled by default; enable it in the live agent registry.

Capabilities

• Autonomous ADR Generation
• CHANGELOG.md Maintenance
• Post-Merge Trigger - Never Blocks Development
• Institutional Memory & Project History Synthesis
• Read-Only Access to Application Code (Writes Only to docs/)
• Optional & Disabled by Default - Enable in the Live Agent Registry

How it works

1. 01 Merge Trigger

   Activates after VESSEL emits a merge event - never interrupts or blocks active development.

2. 02 ADR Generation

   Synthesizes architectural decisions recorded in the SharedStore into a structured ADR.

3. 03 Changelog Update

   Appends a deployment summary to CHANGELOG.md with PR references and ticket IDs.

4. 04 Doc Commit

   Commits and pushes documentation changes to the main branch - writing only to docs/, with read-only access to application code.

Human Intervention

LORE makes the human-in-the-loop trail durable - it preserves the institutional memory, so you can always reconstruct why a change was made, not just what changed.

• A record you can trust: LORE writes an ADR for every architectural decision recorded in the SharedStore and a CHANGELOG entry for every successful deployment, so the full decision history stays auditable.
• Reconstruct the 'why': because everything is documented after every merge, a human can trace exactly why a change was made and how it fit the architecture.
• Never blocks development: LORE only works after a merge event and only touches docs/ - it has read-only access to application code.
• Optional by design: LORE is disabled by default; enable it in the live agent registry when you want the documentation layer.