01

guides are repositories

Every repair guide on CFP1 is like a code repository. It has an owner, a history of every change ever made, and a canonical "main" version that represents the current best knowledge.

A guide covers one job, scoped to a specific model, engine, and year range. "Replace the front crankshaft oil seal — Series 3 2.25 petrol" is a guide. "Engine repairs" is not.

02

changes go through review

Anyone on a WRENCH or WORKSHOP plan can propose a change to any guide. This works like a pull request:

1. 1.you find an error, a better method, or a missing step
2. 2.you submit your proposed change with a short explanation
3. 3.a maintainer with relevant experience reviews it
4. 4.if it's correct, it merges into the main guide
5. 5.the old version is preserved in history — nothing is lost

This means every guide improves over time, and every improvement is traceable. You can see exactly who changed what, when, and why.

03

issues track problems

If something in a guide is wrong but you're not sure of the fix, open an issue. Issues are attached to specific guides and specific steps.

"Step 4 assumes the late-spec transfer box — doesn't apply to pre-'94 models" is a good issue. Maintainers can acknowledge it, link it to a fix, or close it if it's resolved.

Issues keep the guides honest. They're the community saying: this needs attention.

04

the parts registry

Every guide links to parts by canonical ID. The parts registry maps OEM part numbers to aftermarket equivalents, flags superseded numbers, and links to suppliers.

When Land Rover supersedes a part number — and they do, constantly — the registry updates. Every guide that referenced the old number shows the change.

05

plan tiers control contribution