Themes
Fiction Lab / Theme
AI stewardship
Long-term ownership of AI continuity, portability, migration and retirement.
Why it matters
A short deployment can create a decade-long dependency that outlives its vendor, team and runtime.
Recurring mechanisms
1
Critical capability loses its lifecycle owner
2
Migration preserves access but loses state
3
Vendor exit becomes operational failure
Five system dimensions
authority
One owner remains accountable for lifecycle
information
Provenance and evaluations survive migration
resources
Runtime, data and maintenance funding persist
incentives
Growth incentives cannot erase continuity duties
adaptation
Portability and retirement are rehearsed
Discussion prompt
How should an organisation govern an AI system that may outlive its product, vendor or team?