Golden-File Convention Pointers

These examples and illustrative results are independently authored teaching materials, not measured model results.

Use case

Add a connector to a legacy project with inconsistent exemplars. Teaching file A shows current registration, B bounded retries, and old C swallows errors and returns success. Maintained guidance explicitly supersedes C’s structure. Inherit valid conventions without copying its defect.

Mechanism

Select relevant current exemplars and compare file anatomy, state/control flow, shared infrastructure and error handling. Annotate what each demonstrates and where it does not apply. Resolve real conflicts from maintained decisions/call contracts rather than age or majority. Implement selected conventions and verify against examples plus task acceptance.

Bad example

Copy old connector C wholesale, including swallowed errors, because style matching matters more than inspecting the current interface.

Good example

Create concrete convention pointers: cite A's current registration and B's bounded retry with applicable portions. Use maintained guidance to mark C's structure superseded; swallowed errors are not a style to preserve. Compare new anatomy, state, infrastructure and error behavior with valid examples/task requirements. Record evidence/open decisions for material conflicts rather than judging correctness by counts.

Why the change matters

Follow project style does not identify a mechanism. Concrete pointers connect rules to actual interfaces/state while separating evolution, accidental inconsistency and known defects.

Observable expectation

An illustrative table maps A→registration, B→retry and C→superseded layout/error defect. Inspect registration, bounded retries and failures not disguised as success.

Trace rules to current exemplars or maintained decisions. Copying C or using a majority to override an explicit contract fails.

Limits

Exemplars expire and need current content/environment checks. Source percentage thresholds are workflow choices, not proof that minority patterns are wrong. Name necessary variants instead of removing business differences for uniformity.