Attribution

Workstreams

A workstream code here is the same code that appears in the T661 Part 2 narrative, so hours roll up to the technical story without a mapping step in between. The rules below are how raw capture gets attributed — a field, a pattern, and a weight, sorted so the strongest signal is visible. Weights add up: three weak agreeing signals beat one loud one.

adminoverhead

Name: Administration and overhead
Default claim: Hours are tracked but never claimed. The denominator has to be visible for the allocation to be auditable.
Attribution rules: Field Pattern Weight
title /Inbox|Expensify|Payroll|Invoice|Calendar/i 20
app /^(Mail|Calendar)$/i 15

Field	Pattern	Weight
title	/Inbox\|Expensify\|Payroll\|Invoice\|Calendar/i	20
app	/^(Mail\|Calendar)$/i	15

ws-arc-platformsr&ed eligible

Name: ARC Proof anchoring platform
Default claim: Hours default to claimed; an engineer can unclaim any entry.
Attribution rules: Field Pattern Weight
title /arc-proofing|merkle|anchor|cadence/i 20
url /github\.com/cachecow/arc-proofing/i 20
branch /^ws-arc|^main$/i 18

Field	Pattern	Weight
title	/arc-proofing\|merkle\|anchor\|cadence/i	20
url	/github\.com/cachecow/arc-proofing/i	20
branch	/^ws-arc\|^main$/i	18

ws-sip-integrationsr&ed eligible

Name: SiP integration — energy-harvesting frontend
Default claim: Hours default to claimed; an engineer can unclaim any entry.
Attribution rules: Field Pattern Weight
branch /^ws-sip/i 20
title /sip-|thermal|bond-?out|antenna/i 15
app /Saleae|Altium|LTspice/i 12

Field	Pattern	Weight
branch	/^ws-sip/i	20
title	/sip-\|thermal\|bond-?out\|antenna/i	15
app	/Saleae\|Altium\|LTspice/i	12