Understand INI structure and option relationships

Chapter overview

Bottom line: Draw only an offline responsibility map and sort settings into labeled drawers. Do not enter values, write files, or apply settings.

Purpose

Use labeled drawers to separate INI sections, options, and generation responsibilities.

Prepare

A blank sheet of paper with the responsibility classifications for Chapters 7–8; no configuration files or execution data required.

Time

About 20 minutes

System change

Do not modify the INI or start or stop the Add-on; only read the pinned version of the managed template offline.

Expected result

Relate INI sections and options to the component that generates them without treating the template as deployable live configuration.

Stop conditions

• You need to fill in the real environment values or write the template directly into the system.
• Steps require applying settings, installing or restarting the Add-on.

Scope and safety boundaries

This chapter is only classified on paper. Do not paste hosts, addresses, ports, devices, serial numbers, secrets, or live settings. Do not read local results, and do not use the template as the current setting.

This chapter does not add the repository, install or start it. This site lacks approved immutable artifact/image digest and source-to-build proof, so all execution is blocked.

Do not connect the interface or KNX bus. Group reading, group writing, telegram transmission, ETS programming or downloads and physical control are prohibited. Paper comparisons cannot prove daemon, listener, integration or bus results.

Core concepts

Your diagram only needs four drawers: "Main Responsibility", "Service Responsibility", "Record Responsibility" and "Interface Responsibility". If a piece of information cannot be classified based on pinned sources alone, it is put into "pending evidence".

Preparation and prerequisites

Take a piece of paper and draw five empty frames. The first four boxes are the four accountability drawers. The fifth box is "Evidence to be supplemented". Only put category words in each box.

• Write "Offline Responsibility Chart" at the top of the paper.
• Write "does not contain live values".
• Write "No execution results were generated, applied, or read."
• Address version differences under Versions and compatibility; do not mix content from other versions.

If the information at hand contains environmental identification content, do not copy it. Record only "requires confirmation by authorized personnel at a controlled location".

Steps

1. Put the main responsibilities first. Put the overall connection and coordination roles into the main drawer. Do not fill in any value.
2. Then put the service responsibility. Put roles waiting for handover from other software into the service drawer. Do not infer that the service exists.
3. Separate documentation responsibilities. Put message levels and record categories into the record drawer. Do not copy local logs.
4. Separate interface responsibilities. Write device, filter, or network inputs as categories only. Don't put paths or endpoints.
5. Mark source boundaries. Each category card indicates that it comes from an input schema or a managed template. Don't write two sources as if they were the same thing.
6. Write a limited conclusion. Finally, just write "Offline responsibilities have been compared" or "There are still gaps." Do not write deployed or ready for use.

Verification and evidence

The finished product must be a responsibility map without live values. It identifies which category owns each type of data but does not describe what a system is currently doing.

• I have five drawers: main, service, record, interface and pending evidence.
• I label input schemas and managed templates separately.
• My image has no host, address, port, path, serial number, secret or live settings.
• I did not write files, apply, install, start or stop, or read execution results, nor did I declare any bus or integration results.

Next step: Go to Chapter 10, use handover checkpoints to distinguish the evidence layers of driver, interface and bus.

Troubleshooting

• You do not know which drawer applies: Put the item in "Pending evidence." Do not guess from its name.
• Someone posted the official value: Stop sharing and remove content. Responsibility diagrams only keep categories.
• The template looks complete: Still marked as source material. A complete appearance does not mean it has been generated or applied.
• The input schemas do not match the template: Record the two sources separately and mark the gaps. Don't make up the relationship on your own.
• Someone asked for immediate application: Stop. There is no writing, installing, or starting or stopping programs in this chapter.

FAQ