CodePlans / Assets

Know your system, and what shipped in it

Assets are the services, apps, libraries and datastores your products are made of. CodePlans maps them, tracks their health and debt, and keeps a record of what each one does, built from delivered work.

A system map drawn from your inventory

Products become columns, and assets are placed by layer with dependency edges between them. Lenses recolor the map by health, debt or delivery activity. Hover an asset to see its blast radius. Grid and table views sit beside it.

Read the guide →

The Asset Atlas: assets by product with dependency edges and a health lens

What an asset actually does, with evidence

The Record tab is a capabilities register built from delivered work. Each claim carries its work item, plan, release and the spec version it implemented. Active specs show current intent next to the latest version confirmed by delivery. Known issues and debt are derived from open work.

Asset history & record guide →

Auth Service record: spec coverage and a graduated capability with its lineage

A version ladder for every asset

Releases shipped, plans delivered, debt opened and resolved, and spec revisions, grouped by version. Humans and agents add design notes worth keeping; agent-written notes carry an agent badge.

Asset history grouped by version with a design note and plan delivery

Both directions of the graph

What an asset depends on and what depends on it, feeding impact analysis whenever a plan targets it. Owners, discussion and a personal Mute switch live on the same page.

Modeling monorepos →

Auth Service dependencies: depends on PostgreSQL, depended on by the web app and gateway