SpecPunk is built around a small core and a clear operator path.

​
Current slice

The active v0 public surface is centered on:
  • specpunk
  • punk-domain
  • punk-events
  • punk-vcs
  • punk-core
  • punk-orch
  • punk-gate
  • punk-proof
  • punk-adapters
The current vertical slice is: 
plot contract -> approve -> cut run -> gate run -> proof

​
Target shape

The long-term target architecture has four pillars:
  1. Kernel
  2. Stewardship
  3. Council
  4. Skill and eval ratchet
The current public product is earlier than that full target shape.

​
What is not current today

  • punk-council is in-tree but inactive
  • punk-shell is planned only
  • punk-skills is planned only
  • punk-eval is planned only
  • punk-research is planned only

​
Core architectural rules

The public architectural story is built around a few rules:
  • one CLI: punk
  • one vocabulary: plot / cut / gate
  • one state truth: append-only event log plus derived views
  • one final decision writer: gate
  • contract first
  • frozen verification context for gate
  • provider wrapping where possible instead of provider duplication

​
Why the current slice is narrow

SpecPunk is trying to keep the core legible and trustworthy first. That is why the current public path is deliberately small instead of pretending the full target shape is already available.

​
Canonical source

The detailed architectural source of truth for the project lives in docs/product/ARCHITECTURE.md in the repository. This public page is the short external overview.