API Reusability
Turn reuse into a measurable, repeatable practice -- by making capabilities discoverable.
Take Me to the Repo
API reuse is not just discipline -- it is visibility and incentives. Teams rebuild what already exists because reuse is invisible. Manual catalog registration goes stale. Reuse metrics are activity-based, not outcome-based.
Naftiko defines reuse by domain, capability, and contract. Measure and communicate reuse in leadership language -- lead time, throughput, reliability. Surface discovery where developers make decisions: IDE and copilot workflows.
The Naftiko Fleet — six components, all at v1.0.0-alpha3
Spec-Driven Integration (SDI) ties every component to a single declarative YAML spec — authored once, linted by Polychro, executed by Ikanos, authored in Crafter, governed by Warden, orchestrated by Skipper, and documented in Shipyard.
Shipyard
The documentation hub and public front door for the Fleet. Tutorials, concepts, editions. Soon: a hosted Playground and AI-assisted Ask Navi search across the corpus.
Ikanos
The OSS capability engine. Runs a Naftiko spec as a multi-protocol server — REST, MCP, and Skill from the same definition. Apache 2.0.
Polychro
The OSS deterministic AI-era linter for YAML, JSON, and Markdown specs. The new Spectral for SDI. Apache 2.0.
Crafter
The capability builder for VS Code and most AI IDEs. Visual + spec-driven authoring with inline governance and live topology.
Warden
Capability governance and policy enforcement for Backstage. Scorecards, scaffolding, fleet explorer, impact tracing.
Skipper
Fleet-wide orchestration for Kubernetes — across teams, regions, and compliance domains. Continuous compliance and FinOps tagging.
Start small, scale smart
Reuse doesn't scale without discoverability.
Chart your next course
Agent Orchestration
