Skip to main content

ops project

Project registry management. Projects are defined in TOML manifests at manifests/builtin/*.toml. This command group is used to inspect, validate, and diagnose individual projects.

IDs and Aliases Are Interchangeable

Anywhere a project is named, you can use its ID or any of its registered aliases. For example, wdp, wdp-import, and import all resolve to the same project. Use ops project aliases to see every alias in the registry.

When to Use

🔍

Discovery

list, show, and search let you explore what's registered without grepping through TOML files.

Validation

validate runs schema and uniqueness checks on a manifest before you commit it — catches duplicate aliases and missing fields early.

🩺

Diagnosis

health exercises a project's adapter end-to-end; explain generates an AI-written project description from the manifest plus its lat.md.

Subcommands

SubcommandDescription
listList all registered projects
showShow details for a specific project
aliasesShow all registered aliases
validateValidate a project manifest file
searchSearch for projects by name, ID, or description
healthCheck health of a project via its adapter
explainGenerate an AI-powered project explanation using explain_project.md template

ops project list

List every project in the registry, including its ID, category (owned, support), and type.

Every project the registry knows about
Terminal
$ops project list

ops project show

Show the full record for a single project: ID, name, type, path, category, aliases, and any extra manifest fields.

Full registry record for wdp-import
Terminal
$ops project show wdp-import

ops project aliases

Dump every alias in the registry, mapped to the canonical project ID. Handy when you've forgotten what short forms are wired up.

Alias → project ID map
Terminal
$ops project aliases
Alias Uniqueness

Every alias must be unique across all manifests. ops project validate will reject a manifest whose alias collides with one already in the registry.


Fuzzy-search the registry by name, ID, or description text.

Find every project whose name, ID, or description mentions 'billing'
Terminal
$ops project search billing

ops project health

Run the project's adapter health check end-to-end. Returns adapter status, downstream service reachability, and any recent errors.

Adapter-level health check for one project
Terminal
$ops project health wdp-import
Same check, JSON output (for scripts and the dashboard)
Terminal
$ops project health wdp-import --json

ops project validate

Validate a TOML manifest against the registry schema. Checks required fields, alias uniqueness, and path resolution.

Lint a manifest before committing it
Terminal
$ops project validate manifests/builtin/wdp-import.toml
Pre-Commit Habit

Run ops project validate on any manifest you've touched before committing. It catches schema mistakes and duplicate aliases that would otherwise blow up at registry load time.


ops project explain

Generate an AI-powered project explanation using the explain_project.md prompt template. The output stitches together the manifest, the project's lat.md content, and recent activity into a readable summary — useful for onboarding or stakeholder briefings.

Generate a narrative explanation of the wdp-import project
Terminal
$ops project explain wdp-import

Combined Workflow: Adding a New Project

# 1. Write a new manifest
$EDITOR manifests/builtin/my-new-project.toml

# 2. Validate it before committing
ops project validate manifests/builtin/my-new-project.toml

# 3. Confirm it shows up in the registry
ops project show my-new-project
ops project aliases | grep my-new

# 4. Smoke-test the adapter
ops project health my-new-project
No Code Changes Needed

Adding a project is purely declarative — drop a TOML file in manifests/builtin/, validate it, and ops digest, ops portfolio, and the dashboard all pick it up automatically.