03 · Public source

ChronoCore

Structured project continuity that survives the end of a chat session.

A handoff becomes maintained project state rather than another readable summary that quietly goes stale.

View source

Problem

I tried treating the last chat summary as a handoff. It was readable, but it could not tell the next session which blocker was still open, which test actually ran, or whether an old action had already been finished.

Mechanism

Record summaries, changed files, tests, decisions, blockers, next actions, risks and git state in a local SQLite ledger.
Turn those records into a compact briefing with resume.
Close actions and blockers explicitly, and search earlier observations through local FTS without another model call.

Evidence

Local tests: 107 passed
Storage: SQLite · transactions · FTS
Lifecycle: Handoff · resume · closure
Current use: This website handoff

Boundary

ChronoCore only knows what a person or agent records. Its documentation review uses deterministic local checks, not semantic understanding.

The current system is local, single-user infrastructure rather than general agent memory.