artifacts/standard-named
Dependency, Support, and Burden Matrix
artifacts/standard-named/20260715__TELIC-FIELDS__MATRIX__WORKING__HI-5__dependency-support-and-burden.mdRendered from markdown source. Open raw source on GitHub.
Dependency, Support, and Burden Matrix
Status: candidate pre-production Content canon status: unset
| Relation | Required visibility | Primary question | Failure mode | |---|---|---|---| | Person supplies labor | Scope, hours, authority, burden, exit | What was actually agreed? | Role expansion and unpaid structural work | | User supplies data | Artifact, purpose, recipient, duration, downstream use | Which use is authorized? | Hidden recruitment and data capture | | Community supplies legitimacy | Name, mandate, governance, correction | May the loop speak in the community's name? | Legitimacy laundering | | Funder supplies money | Restrictions, reporting burden, expiry, reliance | Which purpose does the funding govern? | Mission and beneficiary drift | | Maintainer supplies repair | Availability, on-call burden, replacement, governance | Is maintenance structurally recognized? | Single-point capture | | Institution supplies authority | Operation, scope, validity, review | Which acts may the loop perform? | Authority drift | | Infrastructure supplies continuity | Portability, custody, switching cost, failure path | Can the loop leave or replace it? | Vendor or technical lock-in | | Family supplies care | Duration, reciprocity, outer support, refusal | Can the caregiver stop without collapse? | Care capture | | Public supplies trust | Transparency, recourse, mandate, succession | Does the loop still represent the public basis? | Institutional self-preservation | | Environment supplies material capacity | Resource use, restoration, future standing | Who inherits depletion or damage? | Unrecorded externalization |
Legitimate dependency test
A dependency is presumptively governable when it preserves:
visible contribution
valid support authority
bounded burden
recognized reciprocity
correction
review
practical exit
residual obligation
Capture warning
A dependency requires independent review when:
support is critical
exit is ineffective
authority is withdrawn
support continues
the dependent loop controls review
Governing distinction
Dependence describes relation. Capture describes the loss of a legitimate way to refuse or redirect that relation.