Walkthrough at a glance

Build a useful schema for the fictional workstation: choose what matters, make different applications understandable in one view, keep noise out, and prove the result against real changes.

The schema-authoring workflow#

You'll start by choosing what is worth tracking. Then you'll describe important configuration clearly, keep noisy files out and test the result against real changes. Finally, you'll extend the same schema beyond files. The highlighted stage shows where you are in that workflow.

1. Define what matters — Start with a blank project and choose exactly what your schema tracks.
2. See inside configuration files — Track individual settings inside configuration files, not just the files.
3. Unify application configuration — Present configuration from different applications in one readable view.
4. Keep noise out — Keep high-churn files out so a Capture shows only the configuration you chose.
5. Prove the schema works — Change the workstation and see precise, useful differences without unrelated churn.
6. Track Registry state — Track a precise Registry value, including the state where it is absent.
7. Track Windows settings — Extend the schema to live Windows master audio settings.

What the finished schema includes#

Application	Required tracking	Optional or deliberately left out
Presentation	session/mode in presenter.ini	Three other INI settings are optional practice
Screen recorder	capture/frame_rate and capture/capture_cursor in recorder.ini; the rest of the recorder folder automatically	buffer/seconds is optional; the cache and log are excluded
Media encoder	encoder-core.dll, five settings in encoding.xml and every *.codec file in codecs	Codec files still under available/
Windows	Pinman's startup Registry value and master Volume/Mute	Other startup values and other Windows settings