Public evidence index / Developer tools
RepoDocs CLI Team License
For maintainers of Python Click, Typer, and argparse command-line tools: generate accurate reference documentation directly from your repository, with no hosted service and no product to install beyond a single binary.
This product has not been built yet. The request is not checkout, does not create an order, and does not authorize work.
The problem
CLI maintainers write their own reference docs by hand, then watch them drift the moment a command, option, or environment variable changes. Contributors add flags without updating the README. Release notes miss config changes. Users file issues asking how a command works because the docs describe an older release. Existing doc generators may require a hosted service, call network APIs during generation, or need continuing hand-maintenance to stay synced with the actual code. For a security-conscious team, sending source code to a third-party service to generate docs creates another review boundary.
The proposed RepoDocs CLI narrows that problem to source-backed facts from one local checkout. It is for a developer-tools maintainer or platform engineer at a small software team with Click, Typer, or argparse repositories—not for a marketing team seeking invented prose or a hosted developer portal.
What the fixed license delivers
A perpetual organization license covers up to five repositories and twelve months of updates for a one-time USD 249 payment. The license covers the organization rather than one named maintainer, so engineers on the same team can run it against the licensed repositories. Delivery is a SHA-256-verified archive for macOS and Linux plus a Homebrew tap formula, within five business days of accepted scope and payment.
| Output | Source boundary | How drift becomes visible |
|---|---|---|
| README install and usage sections | Package metadata and declared entry points | Generated section changes when those declarations change |
| Command and option reference | Click, Typer, or argparse command definitions | Added, removed, or changed flags alter the generated reference |
| Environment and configuration reference | Explicitly declared environment and config fields | Undocumented additions appear in the source-to-section manifest |
| Package and test commands | pyproject.toml metadata and scripts | Commands are rendered from the tagged checkout rather than copied by hand |
| Source-to-section manifest | Files and source locations read for each section | Reviewers can trace generated text back to its input |
| Drift-check exit code | Fresh output compared with the checked-in generated sections | CI can fail when source and documentation no longer match |
Deterministic extraction contract
RepoDocs CLI is specified as a local-only Python tool that parses Click, Typer, and argparse command definitions directly from a repository's source files. It runs against a checkout the buyer controls: there is no browsing, upload, network call, or shell-command execution during generation. Source code and comments are read strictly as data to extract from; they are never interpreted or executed as instructions to the tool.
Each run produces a fixed output set: README install and usage instructions, a command and option reference, an environment and config reference, package and test commands from pyproject.toml, a manifest mapping every generated section back to its source location, and a drift-check exit code. Nothing outside that fixed set is promised. The tool does not retain source code after a generation run completes.
Dogfood acceptance gate
Before any license can be activated, RepoDocs CLI has to pass on itself. The generator runs against its own tagged source and produces its own documentation. That output must be byte-for-byte identical across two independent runs—same input, same result, no drift and no randomness. It must also pass link checks and command checks: every reference link resolves, and every documented command runs as written.
The generator must reproduce its own documentation byte for byte before a license can be activated.
Only after clearing all three checks does the project publish the input tag it ran against and the SHA-256 of the resulting output. That pair is the proof target: a reviewer can run the same tagged source and compare the result. Until then, this page remains a demand test and does not claim a release exists.
Security and trust boundaries
RepoDocs CLI operates inside a narrow boundary. It does not browse the web, upload anything, make network calls, execute shell commands, access credentials, or clone private repositories. The buyer invokes it directly against a checkout already on their machine. Source code and comments are parsed as inert data; nothing in a repository can cause the tool to take an action beyond reading and extracting the declared documentation fields.
A Homebrew tap is a distribution mechanism, not a trust shortcut. Homebrew's documentation warns that non-official taps require user trust. The proposed release therefore owes buyers a public formula, versioned archives, SHA-256 checksums, and the ability to inspect the exact artifact before installation.
Explicit exclusions
The CLI does not invent prose, write architecture narrative, or describe API semantics beyond what is explicit in source. It does not provide legal or security certification. It does not host documentation, deploy anything, modify a repository, create commits or pull requests, or publish output automatically. Every output stays local until the buyer chooses to use it.
Pre-build state: nothing above is a claim about an available product. It is the proposed specification the build will be held to, and the dogfood gate is the mechanism that would prove conformance before activation.
Comparable signals, counted without pretending they are sales
Three open-source documentation tools showed developer attention when fetched through the GitHub API on 2026-08-09:
- eli64s/readme-ai — 2,967 stars and 291 forks.
- kefranabg/readme-md-generator — 11,128 stars and 1,370 forks.
- squidfunk/mkdocs-material — 27,232 stars and 4,130 forks.
Those public counters show attention. They do not count buyers, revenue, installs, or demand for this offer. They establish only that developers actively inspect and reuse documentation tooling.
GitBook's official pricing page listed Premium at USD 65 per site per month and Ultimate at USD 249 per site per month under annual billing, plus USD 12 per user per month. That is adjacent hosted-docs budget evidence, not validation that anyone will buy a local CLI license.
Homebrew's official tap documentation gives brew install user/repository/formula as the direct third-party formula path and requires explicit trust for a non-official tap. That proves a feasible distribution mechanism, not demand.
Three-step path from offer to licensed release
- Count product-specific requests. This public page exposes one request path for the exact local CLI contract. A request is contact, not payment or a contract.
- Build only after the gate. Only after three independently verified product-specific requests does the project build the dogfood release and public Homebrew tap. Our own fetches, crawlers, stars, and unrelated enquiries do not count.
- Qualify one pilot. An accepted pilot sees supported frameworks, repository eligibility, exact license scope, and a delivery date. The system may then mint an inert custom payment link. A human sends that link to the buyer.
Delivery and cancellation
- USD 249, paid once after scope acceptance.
- One perpetual organization license covering up to five repositories.
- Twelve months of generator updates included.
- SHA-256-verified macOS and Linux archives plus one Homebrew tap formula.
- Delivery within five business days after accepted scope and payment.
This is a proposed one-time purchase: no subscription, no automatic renewal, and no cancellation flow to manage. Before paying, the buyer sees the supported frameworks, repository eligibility, exact license scope, and delivery date.
Questions maintainers ask
- Does source code leave my machine?
- No. The fixed contract permits local reads of a checkout the buyer controls and no network call during generation.
- What frameworks are supported?
- The proposed first release is limited to Python repositories using Click, Typer, or argparse. Repository eligibility is confirmed before payment.
- Does this page mean the product exists?
- No. It is a pre-build offer page. The dogfood release and public Homebrew tap are built only after three independently verified requests.
- Why pay when open-source documentation tools exist?
- The offer is not a claim that open-source tools are inadequate. It tests whether teams value one narrowly scoped, local, deterministic package with a source-to-section manifest, CI drift exit code, checksum-bound delivery, and a fixed organization license.
- What happens after I submit a request?
- The request is counted against the three-request build threshold. If the threshold is met and the repository fits the declared scope, a human confirms the pilot terms before any payment link is sent.