Decision: /record Command For Knowledge Capture

Decision

Arijit's agent ecosystem should have one consistent knowledge capture workflow invoked as /record or an equivalent "record this" instruction.

The command should work across Codex, Claude, Hermes/Athena, MyOS role agents, and future coding agents. It should preserve raw session evidence when useful, but its real job is to distill and promote durable knowledge into the right project or vault layer: decisions, wiki updates, project state, process notes, links, and follow-up questions.

Hermes should expose this same method as a skill slash command, not a quick command. Codex and Claude should use the same reusable method through their own skill or command mechanisms.

Rationale

Arijit does not want to write lengthy instructions every time a conversation produces durable knowledge. The capture system should understand the current project, infer the target workspace or repo, and write the appropriate durable artifacts.

Quick commands are too shallow for the Hermes invocation because they run shell commands directly and do not invoke the LLM. /record needs judgment, classification, synthesis, and careful edits. Hermes skills are already exposed as slash commands and can load reusable workflow instructions.

Rejected Alternatives

• Treating Telegram or Codex chat history as the source of truth.
• Saving only raw transcripts.
• Requiring Arijit to specify the exact files to update every time.
• Building a complex knowledge graph before a reliable v1 exists.
• Making the method MyOS-only or Chowmes-only.
• Creating a separate MyOS flavor of /record.
• Using a Hermes quick command as the main Hermes invocation.

Initial Scope

V1 should:

• Infer the workspace when possible.
• Write a session log.
• Create decision records only when decisions were made.
• Update canonical notes or indexes when the operating model changes.
• Preserve raw evidence without flooding the wiki.
• Return a compact receipt.

Follow-Up

• Build a portable agent-knowledge-capture skill for Codex/Claude/Hermes-style usage.
• Install or wrap that same method as the Hermes /record skill command.
• Add a local helper script only if the skill needs deterministic file routing.
• Decide whether /record should also create memory proposals for Athena and future ELT profiles.
• Add a small verification checklist before syncing vault changes to Hermes.