B.1.6:8 - Common Anti-Patterns and How to Avoid Them

Overread	Repair
A method or algorithm is treated as the work-resource roll-up.	Use `A.3.1` or `A.3.2`; use `B.1.6` only for the resource aggregation claim.
A work plan is treated as measured work.	Use `A.15.2` for the plan and `A.15.1` for performed work evidence.
A phase label or timeline is treated as a resource ledger or as proof of a Work relation.	Recover the exact subject first: A.15.1 for Work temporal parts or occurrences, the carrier’s identity pattern plus A.14 for proper non-Work `PhaseOf`, and B.1.4 only for bounded aggregation of already recovered temporal relations. Add B.1.6 only when typed resource values are being aggregated.
A resource gain is treated as emergence.	Use measurement and evidence-use patterns first; use `B.2` when whole identity remains the question; use `B.2.P` for unresolved emergence-family wording.
A ledger, dashboard, or report total is treated as the aggregation result.	Recover the source publications, C.16 measurements, work set and relations, policy, dated aggregation work, B.1.6 result, C.2.1 episteme, and A.10/G.6 provenance.