The app census template: one page per app
Verified 24 August 2026
Reviewed by Elon Salfati, Founder
The direct answer
The app census template is one page per app with seven fields: name, owner, runtime, data touched, access review, restore result, and next fix. Fill it for every app your team built with AI. The total page count is the census, and every blank field is a decision still waiting.
One page should survive the builder leaving.
A new owner, auditor, or incident responder should read one page and know what the app does, where it lives, what it can reach, and whether it comes back after failure. If the answer lives only in the builder's memory, the app has no operational record.
Use the same seven fields for every app.
Consistency makes unknowns comparable. Do not hide a missing answer inside notes. Write Unknown, assign an owner, and resolve it.
The template is useful without Salfati Group.
Copy it into your own register and keep it. If the estate is hard to find or the answers need checking, the free census runs the interview and produces the same page for each app.
Sources
Primary documentation opened and checked on 24 August 2026.
- 1. About repositories
GitHub Docs
Repository ownership, permissions, revision history, and collaboration.
- 2. Claude Code overview
Anthropic
What Claude Code reads, edits, runs, and automates inside a codebase.
- 3. Guide to Enterprise Patch Management Planning
NIST
Patch management as identifying, prioritizing, acquiring, installing, and verifying updates.
Next step
Prefer it done for you? A person confirms the register.