---
name: repository-ledger-visualization
description: "On-demand, on-brand HTML snapshot of the whole file repository — folders/files grouped into a small number of meaningful categories, rendered from a one-time-derived, locked design template rather than redesigned per request; the first feature in this catalog to use the POINTER-STYLE mechanism, with its raw HTML/CSS template and a fabricated-data live preview hosted as their own standalone asset files. Use when a person asks to install or apply \"Repository Ledger Visualization\" (FTR-34) in a project, or when working in a project that has it installed."
---

# Repository Ledger Visualization (FTR-34, version 1.0)

> Generated from library record FTR-34 version 1.0, publish 20261102a. Review status: unreviewed. The complete specification is in references/spec.md and is the authority; this file is the operating procedure drawn from it.

## What this does

On-demand, on-brand HTML snapshot of the whole file repository — folders/files grouped into a small number of meaningful categories, rendered from a one-time-derived, locked design template rather than redesigned per request; the first feature in this catalog to use the POINTER-STYLE mechanism, with its raw HTML/CSS template and a fabricated-data live preview hosted as their own standalone asset files

## When to use this skill

- A person asks to install, apply or update "Repository Ledger Visualization" (FTR-34) in a project.
- A project's agent instructions list repository-ledger-visualization as installed and the task touches what it covers.
- No other feature is required first.
- Works better with, if installed: FTR-04 (skill agent-role-and-project-identity), FTR-13 (skill document-tracker-system).

## Install procedure

Steps run in order. Assess comes first, every question in the Ask step is answered by the person before anything is written, and every write merges additively into the existing project files (read the file first, update an existing section in place, never overwrite).

### Assess first
- Confirm the project's actual subject matter is already established (should exist from Agent Role & Project Identity, FTR-04) — the palette/type derivation needs something real to derive from, not a guess.
- Check whether FTR-13 (Document Tracker System) is installed — if so, category boundaries can draw on existing tracker metadata; if not, this feature still works from a plain folder scan, per its soft dependency.
- Check whether a template file already exists at the expected location (per Storage above) — if so, this is a re-invocation, not a first install; skip the design-derivation step entirely and go straight to a fresh data scan against the existing locked template.
- Check whether `admin\feature-prompts\` already exists as a folder in this project (per the pointer-style mechanism) — if not, it gets created as part of this feature's own install.

### Ask, only if needed
- If the project's subject matter genuinely isn't clear enough to derive a fitting palette from: ask plainly what the project is about, rather than defaulting to a generic palette.
- Present the derived palette + type pairing + any layout idea for confirmation before locking it into the template file — this is not optional, per the design-derivation section above.
- If a template already exists and the person is invoking this for the first time in the current session: no need to ask anything — just re-scan and render against the existing template.

### Write

The full Write payload is in references/write-payload.md. It is applied exactly as written, with the merge rule above.

### Confirm
Confirm: the pointer stub is in `admin\AGENT_INSTRUCTIONS.md`, the full operating content (including the raw template, pulled from its hosted source) is in `admin\feature-prompts\repository-ledger-visualization.md`, and — if this was a first install rather than a re-invocation — the derived palette and type pairing were actually confirmed with the person before the template file was locked in. Want to run it now to see the first render, or is that everything for now?

## Other sections in the specification

- Why this exists, and how it's different from FTR-15 and FTR-22
- The one-time design derivation
- Category grouping
- Data source rule
- Storage
- Customization stays open after first generation

These are in references/spec.md.

## Files in this skill

- references/spec.md: the complete specification, unabridged.
- references/write-payload.md: the Write step on its own.