Omega3 end

omega3-end

Curate what mattered this session into omega3 (__OMEGA3_HOME__). You are the primary capture point. Be judicious: capture long-term value, skip noise.

1. Gather material

• This conversation: what was done, decided, learned; results and their drivers.
• The work (git): git -C "$PWD" log --oneline -20 and git -C "$PWD" diff --stat (and git diff if useful) to ground what actually changed this session.
• Supplement (optional): if you use a per-repo session buffer (e.g. .remember/), glance at it for anything the conversation missed. It's a safety net, not the source of truth.

2. Apply the redaction rule (hard)

Never write credentials, tokens, keys, connection strings, or customer PII. Reference where secrets live instead (Vault/1Password/env). Treat this repo as if it could leak, even if it's private.

3. Decide what's worth keeping

Keep: durable facts, architecture/behavior learned, gotchas, decisions + rationale, shipped work + measurable results, initiative progress. Skip: transient debugging steps, trivia, anything already captured, speculation with no lasting value. If nothing qualifies, say so and do not create empty files or an empty commit.

4. Write outputs

a) Journal entry — write DIRECTLY (if you did work worth logging)

Copy templates/journal-entry.md → journal/YYYY-MM-DD-<slug>.md and fill it: date, initiatives: [<slug>] (pick/reuse a stable initiative slug — this is what the distill rolls up), systems: [...], role, drivers, impact (quantify if known; "TBD" ok), and the What / Why / Result body. Reference PRs/dashboards/incidents by link, not by pasting secrets. Then add a one-line entry to journal/INDEX.md under its marker comment.

b) Knowledge / system candidates — write to inbox (do NOT dedup)

For durable knowledge or system understanding, write raw notes to inbox/YYYY-MM-DD-<slug>.md with frontmatter (type: knowledge or type: system, systems: [...], description:). Don't merge into systems//knowledge/ yourself and don't hand-edit their INDEXes — the nightly distill dedups, merges, links, and indexes. One concept per inbox file.

5. Commit + push (auto)

cd __OMEGA3_HOME__
git add -A
git commit -m "session capture <YYYY-MM-DD>: <short summary>"
git push

Then show the user a concise summary: which journal entry + inbox items you created, and the commit hash. Do not block on confirmation (capture is auto), but the summary makes it auditable and easy to amend.

Guardrails

• Journal → direct; knowledge/systems → inbox. Never write to insights/ (that's review-gated).
• Prefer updating an existing journal initiative slug over inventing new ones.
• If git push fails (offline), leave the commit and tell the user to push later.