# Google Code Wiki — tools that shaped CodeVetter

> Canonical page: https://codevetter.com/inspiration/google-code-wiki

Repository explanations should be refreshed as code changes.

## What we admire

Google Code Wiki’s continuously updated wiki is a useful counterpoint to one-time documentation generation. It treats freshness as part of the reader’s experience, not an implementation detail.

## The principle that stayed

A wiki should say which version of the repository it describes. Regeneration alone is not enough if readers cannot trace an important statement to source or distinguish an inferred relationship.

## Where CodeVetter stands

Repo Unpack artifacts carry a scanned commit and evidence links. We researched Code Wiki as a documentation pattern; CodeVetter does not generate a continuously hosted wiki.

## Sources

- [Google introduces Code Wiki](https://developers.googleblog.com/introducing-code-wiki-accelerating-your-code-understanding/) — the creator's own source
- [CodeVetter codebase-context research](https://github.com/Codevetter/codevetter/blob/main/docs/knowledge/codebase-context-tools-landscape.md) — the CodeVetter project record

This is independent appreciation, not endorsement, partnership, code reuse, or feature parity.

## Public product links

- [CodeVetter](https://codevetter.com/)
- [Download](https://codevetter.com/download)
- [Documentation](https://codevetter.com/docs/)
- [Source](https://github.com/Codevetter/codevetter)