Agent artifact lifecycle

Know what your agents run.

SkillMeat manages the reusable artifacts behind agent workflows, from canonical source to every deployed copy, with version history, lineage, and drift detection.

Start with one artifact Evaluate for your team

Catalog the source. Bind its destinations. Inspect every exception.

The managed artifact estate

Read left to right from canonical source to deployed copies.

Managed artifact estate map A canonical source registers artifacts in a collection. Four typed artifact cards deploy to twelve project tiles. One project is labeled Drift and returns a dashed drift path to the collection. Artifact estate One registered source becomes traceable deployments across a project estate. Source Canonical source release-reviewer sha:3f9a… Registered Collection 6 artifacts · 4 types registered Skill typed card Agent typed card Command typed card Context typed card Deployed Project estate 12 projects Project 01current Project 02current Project 03current Project 04current Project 05current Project 06current Project 07current Project 08Drift Project 09current Project 10current Project 11current Project 12current Drift returns for inspection Legend Deployed path Drift Canonical store Deployed copy

Legend slot: source · registered · deployed · drift

Concept model · available mechanics

Artifact and estate

The files behind agent behavior are infrastructure.

An agent artifact is a reusable instruction, agent, command, workflow, context pack, or tool configuration. Your artifact estate is the set of sources, versions, project copies, and relationships your teams depend on.

01 / Artifact

A reusable unit of behavior

Content travels with its dependencies, version, owner, and target profile.

02 / Estate

The full deployed field

Sources, registry records, projects, and harnesses form one inspectable system.

Artifact anatomy inside the estate

Start with one artifact, then zoom out to every source and destination.

Artifact anatomy inside an estate An Artifact frame lists content, dependencies, version, owner, and target profile. A single zoom connector places that artifact inside a wider Estate frame containing sources, a collection, projects, and harnesses. Mental model An artifact has its own anatomy and belongs to a wider managed estate. Artifact Reusable unit Content source Dependencies refs Version v2.4 Owner platform Target profile codex zoom out Estate Managed scope Sources Artifact Collection registered Projects copies project-a project-b project-c Harnesses Claude Code · Codex · Gemini · Cursor Legend Nested scope Zoom connector Canonical store

Legend slot: artifact · metadata · estate boundary

Concept model · available mechanics

How it works

Catalog. Bind. Deploy. Reconcile.

Register a reusable artifact. Declare where it belongs. Render it for each agent tool. Compare deployed copies with their source, inspect the diff, then bring them back into agreement.

01

Catalog

Register the reusable source with its type, version, owner, and dependencies.

02

Bind

Declare the projects and agent tools where the artifact belongs.

03

Deploy

Render the approved version into each target profile and preserve its lineage.

04

Reconcile

Check deployed copies, preview any diff, and choose how to restore agreement.

Four operations, one record

Each operation changes a declared part of the artifact estate.

Four SkillMeat operations A horizontal flow moves through Catalog, Bind, Deploy, and Reconcile. Each operation names its object and exposes a text state. How it works Four operations connect a reusable artifact to a checked deployment. 01 Catalog Artifact Indexed 02 Bind Project Bound 03 Deploy Profile Rendered 04 Reconcile Drift Checked Legend Operation path Text state Canonical store

Legend slot: source · binding · deployment · reconciliation

Workflow model · available mechanics

Product family

One product in the Agentic OS family.

SkillMeat owns the artifact lifecycle. Visit the Agentic OS Atlas to see how IntentTree, MeatyWiki, Research Foundry, ARC, and the Operator connect around it.

Abstract cartographic atlas with connected technical territories and SkillMeat as the detailed artifact-lifecycle region
Agentic OS AtlasEditorial system map · product labels remain outside the image
SkillMeatIntentTreeMeatyWikiResearch FoundryARCOperator
Concepts

Concepts: instances, versions, lifecycle

Three tiers keep authority visible.

Capabilities

Capabilities

The lifecycle, operation by operation.

Example

Example deployment set

One deployment set. Twelve repositories. One visible exception.

Enterprise

Enterprise readiness

Governance starts with traceable artifacts.

Agentic OS

Built inside an Agentic OS

Built for the loop around agent work.

Docs

Start with one artifact

Start with one artifact.

Start with one artifact.