This page is the outsider-facing proof map for Fileman.
In plain language: it tells a first-time visitor what Fileman already proves in public, where to click for live evidence, and what Fileman still does not claim yet.
analyze -> manifest -> dry-run apply without touching real folders by default.Fileman MCP v1 exists as a local-first stdio extension surface, but it is not the main product claim.Use these routes when you want current public evidence instead of marketing prose:
| What you want to verify | Live route |
|---|---|
| Public source repo | GitHub repository |
| Public release trail | GitHub Releases |
| Public front door | GitHub Pages site |
| Current docs landing page | docs/index.md |
| Safe first-look workflow | Quickstart |
| Review-first operator contract | README.md and Operator Guide |
| Agent/developer extension surface | Fileman MCP v1 |
Fileman is intentionally explicit about the boundaries it has not crossed yet:
Think of it like a well-run workshop that already has a real front door, a real service desk, and real receipts, but has not yet turned itself into a shopping mall with billboards claiming world domination.
The current proof posture is best understood in three layers:
| Layer | What it proves | What it does not prove |
|---|---|---|
| Repo-side proof | the shipped workflow, docs, gates, and local-first runtime surfaces are real | that every live GitHub/platform detail is currently aligned |
| Public platform proof | the repo, Pages, releases, and public-facing GitHub surfaces are live | that every deeper manual or admin-only platform toggle is already perfect |
| Manual / human proof | recorded human baselines, rubric reviews, and broader user trust signals | anything the repo has not explicitly published yet |
Fileman already had a lot of serious engineering proof, but too much of it was hidden in operator docs and workflow files.
This page exists so the front door can answer three normal outsider questions faster: