splent.manifest.json

The manifest tracks the known state of each feature in the product. It is the source of truth for feature health.

Table of contents

• Inspecting the manifest
• Cleanup
• Format reference
• See also

---

Inspecting the manifest

splent feature:status

  Feature status — my_first_app
  ─────────────────────────────────────────────────────────────────────────────
  Feature                                        Mode      Progress   State
  ─────────────────────────────────────────────────────────────────────────────
  splent_io/splent_feature_auth@v1.5.8           pinned    ●─●─●─●   active
  splent_io/splent_feature_public@v1.6.0         pinned    ●─●─●─●   active
  splent_io/splent_feature_redis@v1.5.6          pinned    ●─●─○─○   installed
  splent_io/splent_feature_mail@v1.3.6           pinned    ●─○─○─○   declared

  ─────────────────────────────────────────────────────────────────────────────
  Progress: declared → installed → migrated → active
  Modes:    pinned = versioned release   editable = local development

Only features declared in the current pyproject.toml are shown. Stale entries are hidden.

---

Cleanup

When upgrading features to a new version, old manifest entries become stale. splent product:resolve automatically:

1. Removes entries for features no longer in pyproject.toml
2. Ensures every current feature has at least a “declared” entry

---

Format reference

For the full field reference and update rules, see Feature state — splent.manifest.json.

---

See also

• States — what each state means
• feature:status — CLI command to inspect the manifest
• product:resolve — sync symlinks and clean stale entries