opl-memory-artifact-lifecycle-curator

To compile lifecycle references without modifying core data, gather existing memory refs, artifact refs, provenance, and retention notes into structured, refs-only briefs. This curation process ensures provenance tracking and owner routing are documented without altering any core project data.

Artifact provenance tracking documents the origin and history of project artifacts. You need lifecycle gap classification when managing long-running research projects to identify missing owner actions, ambiguous memory refs, and unmet retention route requirements.

Generate a lifecycle handoff brief by compiling all artifact versions, memory entries, provenance, and retention details into a structured document. The brief outlines existing refs, identified lifecycle gaps, and recommended next legal actions for the project owner.

Yes, lifecycle curation supports owner routing and retention policy enforcement by identifying owner routes and classifying unmet retention requirements. It compiles existing material into briefs that recommend next legal actions without making unauthorized authority claims.

Memory artifact lifecycle curation works without external dependencies, relying solely on existing memory refs and artifact refs. It operates as a non-authoritative curation layer, compiling structured briefs and gap classifications independently.

Refs-only lifecycle briefs are limited to compiling existing references and identifying gaps without modifying core memory or artifact data. They provide non-authoritative curation, meaning they cannot execute owner actions or enforce retention policies directly.