Need to Define What Reuse Means
Pat has been asked to drive API reuse but the organization has never defined what reuse means.
Take Control Of Your Signals — Become a Naftiko Design Partner Today!
Persona Story:
Pat, the head of platforms, has been asked to drive API reuse but the organization has never defined what reuse means—and attempts to create taxonomies keep failing.
Problem Context
- Organization funded a Backstage team and created a “Reuse Strategy Lead” role
- Multiple failed attempts to define reusability taxonomies and standards
- “Reusability levels” became checkbox criteria scoring that misses business alignment
Problem Impact
- Can’t mark things as “reusable” in Backstage without agreeing on what that means
- Architecture standards for reusability get rejected because they don’t work at system/container level
- Leadership asks for reuse metrics but the organization can’t define what to measure
Naftiko Today
- Executable YAML capability specs provide a concrete, machine-readable unit of reuse — a capability is either consumed by another spec or it is not, replacing subjective “reusability level” scoring
- Agent Skills exposure organizes capabilities into business-level skill groupings, defining reuse in terms of task outcomes rather than abstract taxonomies
- Backstage Integration in Fleet registers capabilities as catalog entities, giving the Backstage team a tangible artifact type to track in their existing developer portal
- Multi-source consumption with unique namespaces makes dependency relationships explicit, so “reuse” becomes measurable as “how many capabilities consume this source”
Naftiko Tomorrow
- Naftiko Shipyard MVP (Fleet Second Alpha) will provide a centralized registry where reuse is defined by consumption relationships between capabilities, not manual tagging
- Capability scaffolding from existing APIs (Fleet Second Alpha) will help teams express what they already have as reusable capability specs, making the existing landscape countable
- Tech Radar plugin (Fleet GA) will classify capabilities by adoption stage (assess, trial, adopt, hold), giving leadership a lifecycle-based reuse vocabulary
- Fabric capability discovery (v1.1) will enable cross-team reuse tracking, expanding the definition of reuse beyond a single team’s catalog