Context Engineering
Deliver the right context to AI -- less noise, more relevance -- without MCP sprawl.
Take Me to the Repo
1:1 endpoint-to-tool MCP exports waste context windows and reduce agent quality. Tool lists grow, prompts bloat, and hallucination risk climbs. Naftiko curates fields, schemas, and descriptions so tool discovery is semantic -- and shapes response payloads into smaller, typed outputs aligned to tasks.
Standardize packaging and boundaries so security review scales. Right-size context into capabilities that agents can use reliably, not raw provider complexity dumped into a prompt.
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
AI will figure it out without documentation -- it won't.
Chart your next course
API Reusability
