Elevate an Existing API
Wrap a current API as a capability to make it easier to discover, reuse, and consume across teams and channels.
Take Me to the Repo
Model the legacy or existing API once in your capability spec with explicit methods, paths, parameters, and body formats. Add a stable capability namespace and expose curated resource paths and tools that are easier to consume than vendor-native endpoints.
Enforce schema-based validation so the elevated contract remains consistent and machine-checkable. Change HTTP methods to expose proper semantics -- for example, adapt read-only POST queries into cacheable GET queries. Convert XML, Avro, and CSV payloads to JSON.
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
Elevate what you have. Ship what you need.
Chart your next course
Compose AI Context
