This appendix defines a compact set of recommended warning and error identifiers for codex-mem v1.
The goal is consistency across implementations and easier debugging during conformance testing.
- Warnings indicate degraded but usable outcomes.
- Errors indicate that the intended operation could not complete safely or meaningfully.
- Identifiers are stable categories, not user-facing prose.
Meaning:
- No open handoff was found for the current workspace or project during bootstrap.
Meaning:
- No relevant high-value notes were found for the current scope.
Meaning:
- Scope resolution succeeded, but only with partial confidence or fallback logic.
Meaning:
- Weaker identity evidence was used, such as local path fallback.
Meaning:
- Related-project retrieval was requested or possible, but was skipped due to policy or missing relations.
Meaning:
- Related-project retrieval was attempted but returned no results.
Meaning:
- Bootstrap used a recovery-generated handoff because no stronger continuation source was available.
Meaning:
- A write operation matched an existing record and deduplication logic was applied.
Meaning:
- Optional related project ids or note references were provided, but some could not be resolved.
Meaning:
- A handoff was accepted, but missing optional fields may reduce future recovery quality.
Meaning:
- An AGENTS target file already existed and safe mode skipped modification.
Meaning:
- AGENTS installation succeeded, but some placeholders remain for manual completion.
Meaning:
- An imported artifact was ignored due to privacy, dedupe, or stronger explicit memory already existing.
Meaning:
- Required input is missing, malformed, or semantically invalid.
Meaning:
- The provided or resolved scope is incomplete, inconsistent, or unsafe to use.
Meaning:
- Scope evidence or stored mappings conflict and safe identity cannot be maintained.
Meaning:
- A referenced session does not exist.
Meaning:
- A requested note or handoff id does not exist.
Meaning:
- A requested state or state transition is invalid for the operation.
Meaning:
- The durable storage backend is unavailable or failed the operation.
Meaning:
- A write operation could not be completed.
Meaning:
- A read operation could not be completed.
Meaning:
- AGENTS installation failed because the target path could not be written safely.
Meaning:
- An invalid target or mode was supplied to
memory_install_agents.
- Return user-facing explanatory text alongside these identifiers.
- Preserve identifiers in debug or audit output where possible.
- Use one or more warnings rather than an error when the system can still proceed safely.