Shokunin Platform

Shokunin is an AI-powered platform built around the principles of Japanese craftsmanship — deliberate, precise, and built to last.

What is Shokunin?

The Shokunin platform provides teams with tools to manage AI-assisted workflows, agents, workshops, and knowledge libraries. It is designed to make complex AI operations predictable and maintainable.

Core Principles

Craftsmanship — Quality over speed. Every interface and API is designed with care.
Transparency — Agents and workflows are observable and auditable.
Composability — Build complex workflows from simple, well-defined primitives.
Reliability — The platform is built for production workloads.

Platform Areas

Area	Description
Workshops	Managed workspaces for AI agent teams
Agents	Individual AI agent management and monitoring
Knowledge Library	Curated knowledge bases for agent context
AI Chat	Conversational interface for platform interaction
Docs	This documentation site

Implementation Status Matrix

This matrix shows the current state of each platform component across operational areas. Use it to quickly assess platform maturity and understand the roadmap. Status key:

✅ Implemented — exists in the codebase, functional today
🔄 In Progress — active development underway (open PRD or beads epic)
📋 Planned — PRD exists, not yet started
⬜ Not Yet Planned — recognized need, no PRD yet

Component	User-Facing Features	Operational (Observability)	Administrative	Developer Tooling
Platform UI	✅ Next.js app, authenticated routes, workshop/agent/project pages	⬜ No metrics/tracing UI	✅ Infrastructure Dashboard at `/admin/infrastructure`	✅ Feature flags, dark mode, dev container
Workshop Containers	✅ Agent Control Panel: provisioning, SSE session status, container health	⬜ Not yet planned	⬜ Not yet planned	✅ `infrastructure/shokunin-agent` (Fastify, GKE) + `infrastructure/shokunin-provisioner` (Cloud Run)
OpenCode Integration	✅ SSE session stream via `AgentRuntimeProvider`; deep links per active session	⬜ Not yet planned	⬜ Not yet planned	✅ OpenCode plugin (`plugins/agent/`) functional
Shokunin Agent	✅ TypeScript service; Agent Control Panel UI; REST control API	⬜ Not yet planned	⬜ Not yet planned	✅ `plugins/agent/` — agents, commands, skills bundled
Beads (Task Tracking)	✅ Kanban, list, dependency graph UI in the platform	⬜ Not yet planned	⬜ Not yet planned	✅ `bd` CLI fully functional; Dolt backend local
Forge (Git/Merge)	⬜ No UI surface	⬜ Not yet planned	⬜ Not yet planned	📋 Referenced in agent workflow PRD as planned
Authentication / Identity	📋 Login/register pages need wiring (PRD: prd-auth-identity-access.md)	⬜ Not yet planned	📋 User/seat/role model in PRD	⬜ Not yet planned
Audit Logging	⬜ No UI viewer (write-only by design per PRD)	📋 Dual Firestore write backend (PRD written, not implemented)	📋 Per-tenant and platform-wide audit log planned	⬜ Not yet planned
Admin Tenant Ops	⬜ Not yet planned	⬜ Not yet planned	📋 Tenant CRUD, plan config, audit log UI (PRD written)	📋 Logging + notification abstractions in PRD
Profile Settings	📋 Profile page, theme, notification preferences (PRD written)	⬜ Not yet planned	⬜ Not yet planned	⬜ Not yet planned
Knowledge Library	📋 PRD exists, route placeholder in app	⬜ Not yet planned	⬜ Not yet planned	⬜ Not yet planned
Infrastructure (GCP)	⬜ No user-facing infra features	🔄 GCS manifest (live GCP API polling implemented; manifest schema alignment in progress)	✅ Infrastructure Dashboard — Cloud Run, GKE, tenant workloads, IAM, Cloud Tasks	✅ Terraform IaC: GKE Autopilot, GKE Gateway, Workshop Provisioner, Tenant modules
Docs (Mintlify)	✅ `/docs` route with embed support	⬜ Not yet planned	⬜ Not yet planned	✅ Mintlify v4 scaffold at `apps/mfe-docs/`

Reading the Matrix

User-Facing Features — what end users (contributors, platform users) can interact with today
Operational — observability, logging, metrics, tracing — what ops teams need to run the platform
Administrative — tenant management, user management, plan configuration
Developer Tooling — tools, CLIs, plugins, and abstractions that help contributors work on the platform

Status is derived from: existing code in this repo, open beads issues, and PRD files in tasks/. “Implemented” means the feature exists in the codebase today — not just planned.

This documentation site is a work in progress. Content will be expanded as the platform evolves.

Overview

Architecture

Getting Started

Repo Map

Infrastructure

Overview

Shokunin Platform

What is Shokunin?

Core Principles

Platform Areas

Implementation Status Matrix

Reading the Matrix

​Shokunin Platform

​What is Shokunin?

​Core Principles

​Platform Areas

​Implementation Status Matrix

​Reading the Matrix

Shokunin Platform

What is Shokunin?

Core Principles

Platform Areas

Implementation Status Matrix

Reading the Matrix