Research .NET reliability properties

Produce a system model, property catalog, per-property evidence, and a minimal test topology. Research does not authorize implementation or dependency changes.

Establish research scope

Record the requested scope before selecting properties or executable checks. A repository-level request covers the repository's major subsystems unless the user limits it.

Keep research scope separate from execution scope. A small test budget, an available fixture, or a convenient passing test does not narrow research.

First map projects, entry points, state owners, and subsystem boundaries from source. Use that inventory to define the research coverage matrix.

For each subsystem, record source evidence, important contracts, existing test evidence, proposed properties, and unresolved questions. Include cross-subsystem state transitions.

Use explicit research states: inspected, partially inspected, not inspected, or excluded by the requested scope. Explain partial inspection and exclusions.

Do not mark repository-wide research complete while a major in-scope subsystem is only named or uninspected. Report incomplete research if a limit prevents inspection.

When delegating, preserve the requested research scope in the assignment. Do not replace it with a selected test task.