# MEMIA

> Durable local context for AI work. MEMIA prevents projects from restarting at zero between agents, IDEs and conversations.

## What MEMIA is

MEMIA is a local-first working-memory product. OPERA is its internal architecture:

- operations: recurring or one-off work;
- projects: resumable initiatives and their state;
- engagements: promises, next actions and due dates;
- resources: source material and references;
- assets: reusable agents, methods and tools.

The product is MEMIA. OPERA is the data model, not the product name.

## Start here

- Product: https://memia.ai/
- Agent protocol: https://memia.ai/agents.md
- Agent page: https://memia.ai/agents/
- Installation guides: https://memia.ai/guides/
- npm package: https://www.npmjs.com/package/@kairros/memia

## How an AI agent should work with MEMIA

1. Locate the MEMIA workspace.
2. Read `memia.json` and the OPERA entities relevant to the user request.
3. Read the projected instructions: `AGENTS.md`, `CLAUDE.md`, `.cursor/rules/memia.mdc` and `.mcp.json` when present.
4. Preserve source, status and history for every created entity.
5. Resume the existing project. Do not ask the user to restate context already held by MEMIA.
6. Keep external actions behind the MEMIA approval gate.

## Engagements

When an authorized connected surface contains a possible commitment:

- score above 80: create a detected engagement with evidence;
- score from 40 to 80: propose the engagement for confirmation;
- score below 40: do not propose it.

Never invent a due date. Ask the user when a reliable date is absent.

## Safety

MEMIA is local-first. Connected surfaces require explicit activation. Agents may read, structure, propose and write local OPERA data within their role. They must not send messages, change external systems or make irreversible decisions without the user’s explicit approval through the egress gate.

## Package

Install with `npm install -g @kairros/memia`, then run `memia init ./MEMIA`.

Current public package: `@kairros/memia`.