---
mw_bundle: 1
type: hub_digest
slug: b0bpar81
author: "bconklin66"
url: https://memory.wiki/hub/b0bpar81
concept_count: 40
updated: 2026-09-20T19:02:18.457Z
source: "memory.wiki"
---

# bconklin66's knowledge — concept digest

_40 concepts extracted across this hub. Each entry links to the supporting documents — fetch any of them as `https://memory.wiki/raw/<id>?compact=1` for the dense full text._

## Concepts

### Office Recorder
*entity • weight 5 • 1 doc*

> A local activity recorder for engineering work that tracks timestamps, file changes, and project activity.

- [Office Recorder and its MCP server](https://memory.wiki/SQUMIWlI)
  Office Recorder is a local activity tracking system that uses a background daemon to log timestamped events, such as file changes and window activity, into daily JSONL files. An integrated Model Context Protocol server allows AI clients to query this history or add manual notes to help users resume project work.

_Related:_ uses as server → **office-history**

### Model Context Protocol (MCP)
*concept • weight 4 • 1 doc*

> The communication protocol used by the server to expose activity history and tools to AI clients.

- [Office Recorder and its MCP server](https://memory.wiki/SQUMIWlI)
  Office Recorder is a local activity tracking system that uses a background daemon to log timestamped events, such as file changes and window activity, into daily JSONL files. An integrated Model Context Protocol server allows AI clients to query this history or add manual notes to help users resume project work.

### office-history
*entity • weight 4 • 1 doc*

> The specific MCP server implementation that reads the event store and provides query tools.

- [Office Recorder and its MCP server](https://memory.wiki/SQUMIWlI)
  Office Recorder is a local activity tracking system that uses a background daemon to log timestamped events, such as file changes and window activity, into daily JSONL files. An integrated Model Context Protocol server allows AI clients to query this history or add manual notes to help users resume project work.

_Related:_ implements protocol → **Model Context Protocol (MCP)**

### Daemon
*concept • weight 3 • 1 doc*

> The background process responsible for observing activity sources and writing to JSONL files.

- [Office Recorder and its MCP server](https://memory.wiki/SQUMIWlI)
  Office Recorder is a local activity tracking system that uses a background daemon to log timestamped events, such as file changes and window activity, into daily JSONL files. An integrated Model Context Protocol server allows AI clients to query this history or add manual notes to help users resume project work.

### record_event
*concept • weight 3 • 1 doc*

> An MCP tool used to manually append notes, decisions, or checkpoints to the event store.

- [Office Recorder and its MCP server](https://memory.wiki/SQUMIWlI)
  Office Recorder is a local activity tracking system that uses a background daemon to log timestamped events, such as file changes and window activity, into daily JSONL files. An integrated Model Context Protocol server allows AI clients to query this history or add manual notes to help users resume project work.

_Related:_ is tool of → **office-history**

### reclaim_context
*concept • weight 3 • 1 doc*

> An MCP tool that aggregates event history into a context bundle to assist in project resumption.

- [Office Recorder and its MCP server](https://memory.wiki/SQUMIWlI)
  Office Recorder is a local activity tracking system that uses a background daemon to log timestamped events, such as file changes and window activity, into daily JSONL files. An integrated Model Context Protocol server allows AI clients to query this history or add manual notes to help users resume project work.

_Related:_ is tool of → **office-history**

### Configuration
*concept • weight 3 • 1 doc*

> The JSON-based settings file defining watch roots, polling intervals, and project rules.

- [Office Recorder and its MCP server](https://memory.wiki/SQUMIWlI)
  Office Recorder is a local activity tracking system that uses a background daemon to log timestamped events, such as file changes and window activity, into daily JSONL files. An integrated Model Context Protocol server allows AI clients to query this history or add manual notes to help users resume project work.

## Concept relations
_20 highest-weight edges between the top concepts._

- **memory.wiki** tracks project sources **MISys database interface**
- **Standing workflow** is documented in **memory.wiki**
- **memory.wiki** tracks project sources **QMC-AD330**
- **Standing workflow** is recorded in **memory.wiki**
- **Ongoing work registry** tracks project sources **MISys database interface**
- **memory.wiki** tracks project status **MISys database interface**
- **ChatGPT** provides investigation source **MISys database interface**
- **Codex** contributes to **MISys database interface**
- **memory.wiki** tracks project status **QMC-AD330**
- **Codex** executes tasks for **MISys database interface**
- **Codex** performs tasks for **MISys database interface**
- **ATC-JTS64 schematic part-number annotation** uses as authority **MIITEM.XML**
- **Codex** participates in **MISys database interface**
- **Codex** executes project tasks **MISys database interface**
- **ChatGPT** provides source history **MISys database interface**
- **ChatGPT** provides context for **MISys database interface**
- **memory.wiki** tracks project **MISys database interface**
- **Codex** executes primary task **Build BOM Excel exporter**
- **Codex** performs tasks for **QMC-AD330**
- **Codex** performs tasks for **ATC-JTS64 schematic part-number annotation**

## All documents
_1 public document, ordered by recency. Each entry includes a one-paragraph gist for quick scanning. Fetch any as `https://memory.wiki/raw/<id>?compact=1` for the full body._
- [Office Recorder and its MCP server](https://memory.wiki/SQUMIWlI)
  Office Recorder is a local activity tracking system that uses a background daemon to log timestamped events, such as file changes and window activity, into daily JSONL files. An integrated Model Context Protocol server allows AI clients to query this history or add manual notes to help users resume project work.
  _sections:_ What Office Recorder does: Office Recorder is a local activity recorder for engineering work. A background daemon writes timestamped events, and the office-history Model Context Protocol  | How it works: 1. The daemon observes configured activity sources. | Recorded activity: | Source | Recorded information | | Setup and execution: From a local checkout with Node.js and npm available: | Connecting the MCP server: The server uses stdio. After building, configure an MCP-capable client to launch Node with the compiled CLI: | …

---

_Need everything? [Full hub index](https://memory.wiki/raw/hub/b0bpar81?compact=1) lists every public document. [llms.txt manifest](https://memory.wiki/hub/b0bpar81/llms.txt) explains how to crawl this hub._
