Model availability does not remove the cost of wrapping, pipelines and domain integration.
No quantified cost comparison.
Likely speaker
Zineb BhabyAI Lead · Norwegian Refugee Council
Making AI Useful in Humanitarian ResponseWatch passage →
DEFINITION USED IN THIS COLLECTION
Capacity.
Staff time, skills, organisational resources or complementary capability required to act.
What it includes
Staff time, skills, organisational resources or complementary capability required to act.
Where the boundary lies
A rule assigning responsibility does not establish capacity to fulfil it.
How speakers put it.
The definition above is used to organise this collection. The passages below show how the idea appears in discussion.
Evidence in practice.
All 127 coded passages →Analyst applies. Model availability does not remove the cost of wrapping, pipelines and domain integration.
Qualifies the boundary. A rule assigning responsibility does not establish capacity to fulfil it.
Participants distinguish policy-bearing data exchange from an API that merely passes data.
Technical attachment does not itself demonstrate enforcement.
Likely speaker
Unidentified speaker
Multi-stakeholder, Sovereign, Agentic Workflows / Data Models, Evidence, and VerificationWatch passage →
Differences and limits.
No event-wide agreement is inferred from coding. Compare the attributed examples and boundaries; co-occurrence is not evidence of agreement.
A rule assigning responsibility does not establish capacity to fulfil it.
Related concepts.
adoption →
Actual use differs from the staff, skills and resources that make use possible.
Codes that occur in the same passages
Co-occurrence describes coding, not equivalence, causation or agreement.