Naftiko Fleet¶
Naftiko Fleet is a family of components built around Spec-Driven Integration, a methodology that elevates AI integration from a coding project to a specification task.
It includes the open-source Ikanos capability engine and the open-source Polychro linter for AI, together with Naftiko Crafter a VS Code extension for capability editing and linting compatible with most AI IDEs, Naftiko Warden a Backstage integration for capability scaffolding and cataloging, and Naftiko Skipper a Kubernetes integration for capability delivery and operations.
Why the Naftiko Fleet¶
| Pain | What the Fleet does about it |
|---|---|
| API sprawl across SaaS, microservices, and legacy systems | Declare integrations once as a capability — one spec, many transports |
| Agents unreliability | Deterministic engine + linter ensure the spec executes exactly as written - limiting drift, hallucinations, and contract breakings |
| Context bloat for AI tasks | Right-size MCP tools and resources directly in the capability spec |
| Boilerplate code for HTTP clients, auth, format conversion | Declarative consumes/exposes adapters cover the 90% case in YAML |
What the Fleet is¶
The Naftiko Fleet delivers Spec-Driven Integration end to end, from authoring a capability to running, governing, and orchestrating it at scale. It builds on the open-source foundation of Ikanos (the capability engine) and Polychro (the AI-era linter), and adds three product components that each own one step of the workflow:
- Crafter — an extension for VS Code-compatible IDEs to edit Ikanos specs and lint them with Polychro.
- Warden — a Backstage integration to help with cataloguing, scaffolding, and delivery of Ikanos capabilities.
- Skipper — a Kubernetes integration to deploy and operate a fleet of capabilities.
A fleet is what you call a group of ships sailing together — here, a group of capabilities running and governed as one.
What the Fleet is not¶
- Not a single monolithic product. The Fleet is a set of independently usable components, not one binary. You can adopt Crafter, Warden, or Skipper only when you need them.
- Not a paywall on the essentials. The Fleet always relies on Ikanos and Polychro, which are fully open-source under Apache 2.0.
- Not an all-or-nothing platform. Components compose, but none requires the others.
Where to start¶
| If you are… | Go to |
|---|---|
| New to Spec-Driven Integration | Overview → Spec-Driven Integration |
| Ready to install and try it | Getting Started → Installation |
| Looking for hands-on practice | Quickstart |
| Evaluating components | Fleet → Overview |
| Comparing Fleet editions | Fleet → Editions |
The Fleet components¶
| Component | Purpose | Status |
|---|---|---|
| Ikanos | The OSS capability engine — runs a Naftiko spec as a multi-protocol server | v1.0.0-beta2 |
| Polychro | The OSS deterministic AI-era linter for YAML, JSON, and Markdown specs | v1.0.0-beta2 |
| Crafter | The capability builder for VS Code and most AI IDEs — visual + spec-driven authoring | v1.0.0-beta2 |
| Warden | Capability governance and policy enforcement for Backstage | v1.0.0-beta2 |
| Skipper | Fleet-wide orchestration for Kubernetes, across teams, regions, and compliance domains | v1.0.0-beta2 |
| Shipyard | Documentation hub — and soon a hosted Playground and AI-assisted search | This site |