Module discovery, visibility and topology

What it covers

• Static system domains are combined with dynamically registered modules.
• A dynamic module requires a registry record, manifest, product presence and service/binary/marker evidence.
• Visibility can hide a not-applicable, invalid/integrity-failed, missing-product/backend, disabled or unauthorised module.
• Topology connects module, service, worker, capability and entry point; domain closure checks completeness.

How to use it

1. Run visibility audit.
2. Open topology report.
3. Run registry reconciliation.
4. Fix the actual dependency.

Important rules

• Do not copy a manifest from another machine.
• Do not create a fake marker.
• A visible screen without runtime closure is misleading.