IX (9)

janus-worklog

janus

Use at the end of any meaningful work session to update the project's continuity log — what changed, what was learned, what is next. Also use when resuming work and the prior WORKLOG must be read.

Janus Worklog

IPurpose

Keep project continuity short and durable. The worklog is the bridge between sessions.

IIWhen To Use

  • At the end of a meaningful work session.
  • When resuming a project — read it first.
  • After a checkpoint (/checkpoint).

IIIFile Location

Each janus-managed project has its own log at:

<project-root>/.janus/WORKLOG.md

If the project does not yet have a .janus/ folder, bootstrap one with scripts/new_project.py <project-root>.

IVWhat To Write

Keep it concise. The template is templates/WORKLOG.md. Fill only the sections that changed this session.

  • Current State: one line.
  • Completed Work: a few bullets.
  • Decisions Made: only durable ones, not tactical ones.
  • Problems / Risks: only open ones.
  • Verification Results: commands run and outcome.
  • Lessons Learned: only reusable ones.
  • Next Recommended Action: one line.

VDiscipline

  • Worklog is short-term continuity.
  • Long-term durable facts belong in PROJECT_CONTEXT.md.
  • Reusable patterns belong in a new skill, not the worklog.

Do not let the worklog grow into a journal.

← back to the stoa