1 / 2
Automation system
Memory Preview — Human-Governed AI Knowledge System
A governed AI knowledge system that separates conversational reasoning from durable project memory. ChatGPT can propose structured knowledge updates through an MCP bridge, while provenance, project isolation, duplicate and conflict checks, and explicit human approval control what becomes permanent. Approved knowledge is versioned in GitHub and can be retrieved later as project-scoped context, preserving traceability and human oversight.
- The business problem
- AI conversations contain valuable project decisions, requirements, and lessons, but that context is often lost between sessions or stored without clear ownership, provenance, or review. The challenge was to create durable project memory without allowing an AI agent to write directly into trusted knowledge. The system also needed to prevent cross-project leakage, detect duplicates and conflicts, preserve source evidence, and require explicit human approval before any proposed knowledge became permanent.
- The system designed
- ChatGPT performs conversational reasoning and prepares structured knowledge proposals through a project-scoped MCP integration. The MCP server acts as the controlled bridge between ChatGPT and the knowledge repository, enforcing project authorization, schema validation, provenance requirements, duplicate and conflict checks, and approval workflows. Proposed changes remain drafts until a human confirms the exact approval challenge. Confirmed proposals open a draft GitHub pull request, where version history, review, and traceability are preserved. Compiled project knowledge can then be retrieved in later sessions through authorized, project-scoped context tools.
- What it does in operation
- Memory Preview gives AI-assisted projects continuity without sacrificing human control. Teams can preserve decisions, requirements, architecture choices, project state, and validated learnings across sessions while keeping every permanent update reviewable and traceable. Project isolation reduces the risk of knowledge leaking between clients or workspaces, provenance shows where information came from, and GitHub-based versioning provides an auditable change history. The result is a safer and more maintainable way to use long-term AI memory in real project workflows.