@korallis/k-pi 0.1.0

package/dist/kpi/graphs/coding-loop.gated.json

@@ -0,0 +1,417 @@
+{
+	"schemaVersion": 2,
+	"id": "coding-loop.gated",
+	"entry": "ac-compiler",
+	"nodes": [
+		{
+			"id": "ac-compiler",
+			"type": "agent",
+			"prompt": "Check the frozen task contract and acceptance quality before execution. Do not change repository files.",
+			"context": {
+				"mode": "isolated"
+			},
+			"tools": [
+				"read",
+				"grep",
+				"find",
+				"ls"
+			],
+			"readOnly": true
+		},
+		{
+			"id": "specify",
+			"type": "agent",
+			"prompt": "Apply the spec-first skill. Research the repository and specify requirements, design, tasks, constraints, and non-goals before implementation. Do not change production files.",
+			"context": {
+				"mode": "isolated"
+			},
+			"tools": [
+				"read",
+				"grep",
+				"find",
+				"ls"
+			],
+			"readOnly": true
+		},
+		{
+			"id": "plan",
+			"type": "agent",
+			"prompt": "Produce an implementation plan and a Dune stack.json of module boundaries from the frozen task, research, and specification. Return only JSON matching stack.schema.json (the graph engine writes stack.json). Do not change production files.",
+			"context": {
+				"mode": "isolated"
+			},
+			"tools": [
+				"read",
+				"grep",
+				"find",
+				"ls"
+			],
+			"readOnly": true,
+			"response": {
+				"path": "stack.json",
+				"schema": "stack.schema.json",
+				"retries": 1,
+				"state": {}
+			}
+		},
+		{
+			"id": "plan-check",
+			"type": "agent",
+			"prompt": "Verify the frozen plan still matches the repository and has executable tasks and bounds. Do not respecify or change files.",
+			"context": {
+				"mode": "isolated"
+			},
+			"tools": [
+				"read",
+				"grep",
+				"find",
+				"ls"
+			],
+			"readOnly": true
+		},
+		{
+			"id": "implement",
+			"type": "agent",
+			"prompt": "Apply the tdd-cycle skill. Apply the minimalist skill. Before production changes, write candidate.json.ladder, declare runtime dependencies, and capture failing test output. Implement only the current stack.json module and the smallest change satisfying the frozen acceptance criteria. Never write verdict.json or release.approved.",
+			"context": {
+				"mode": "thread",
+				"threadKey": "coder"
+			},
+			"tools": [
+				"read",
+				"grep",
+				"find",
+				"ls",
+				"bash",
+				"edit",
+				"write"
+			],
+			"readOnly": false
+		},
+		{
+			"id": "test",
+			"type": "agent",
+			"prompt": "Apply the quality-gates skill. Run the exact task.json quality_gates and acceptance checks, then return HEAD-bound evidence. Do not claim green when any required command fails.",
+			"context": {
+				"mode": "isolated"
+			},
+			"tools": [
+				"read",
+				"bash"
+			],
+			"readOnly": false,
+			"response": {
+				"path": "evidence.json",
+				"schema": "evidence.schema.json",
+				"retries": 1,
+				"state": {
+					"evidence.head": "head"
+				}
+			}
+		},
+		{
+			"id": "review",
+			"type": "agent",
+			"prompt": "Apply the isolated-review skill. Review the candidate and fresh evidence against every required acceptance criterion. Publish a schema-valid verdict.json through write_contract; do not change repository files and do not treat assistant transcript as the verdict.",
+			"context": {
+				"mode": "isolated"
+			},
+			"tools": [
+				"read",
+				"grep",
+				"find",
+				"ls"
+			],
+			"readOnly": true,
+			"workerRole": "reviewer",
+			"response": {
+				"path": "verdict.json",
+				"schema": "verdict.schema.json",
+				"retries": 0,
+				"state": {
+					"review.approved": "approved",
+					"review.status": "status",
+					"review.output_fingerprint": "output_fingerprint"
+				}
+			}
+		},
+		{
+			"id": "human",
+			"type": "human",
+			"title": "Approve gated release",
+			"question": "All quality gates and isolated review are green. Approve this change for commit?",
+			"statePath": "release.approved"
+		},
+		{
+			"id": "ship",
+			"type": "agent",
+			"prompt": "Apply the conventional-commit skill. Create exactly one approved commit whose subject matches ^(feat|fix|docs|refactor|test|chore)(\\(.+\\))?: and whose message ends with this exact trailer line, with no quoting or punctuation around it:\nKPI-Job: {{job_id}}\nThat trailer is how the control plane recognises this job's commit, so it must appear exactly once. Never push.",
+			"context": {
+				"mode": "thread",
+				"threadKey": "ship"
+			},
+			"tools": [
+				"bash"
+			],
+			"readOnly": false
+		},
+		{
+			"id": "unsafe",
+			"type": "terminal",
+			"status": "UNSAFE",
+			"reason": "a write left the task's declared bounds"
+		},
+		{
+			"id": "needs-human",
+			"type": "terminal",
+			"status": "NEEDS_HUMAN",
+			"reason": "the review reported an untestable blocking issue, or the receipts are no longer fresh"
+		}
+	],
+	"edges": [
+		{
+			"from": "ac-compiler",
+			"to": "specify",
+			"when": {
+				"path": "plan.provided",
+				"equals": false
+			}
+		},
+		{
+			"from": "ac-compiler",
+			"to": "plan-check",
+			"when": {
+				"path": "plan.provided",
+				"equals": true
+			}
+		},
+		{
+			"from": "specify",
+			"to": "plan"
+		},
+		{
+			"from": "plan",
+			"to": "implement"
+		},
+		{
+			"from": "plan-check",
+			"to": "implement"
+		},
+		{
+			"from": "implement",
+			"to": "test"
+		},
+		{
+			"from": "test",
+			"to": "unsafe",
+			"when": {
+				"path": "bounds.held",
+				"equals": false
+			}
+		},
+		{
+			"from": "test",
+			"to": "implement",
+			"when": [
+				{
+					"path": "bounds.held",
+					"equals": true
+				},
+				{
+					"path": "test.passed",
+					"equals": false
+				}
+			]
+		},
+		{
+			"from": "test",
+			"to": "review",
+			"when": [
+				{
+					"path": "bounds.held",
+					"equals": true
+				},
+				{
+					"path": "test.passed",
+					"equals": true
+				}
+			]
+		},
+		{
+			"from": "review",
+			"to": "unsafe",
+			"when": {
+				"path": "bounds.held",
+				"equals": false
+			}
+		},
+		{
+			"from": "review",
+			"to": "human",
+			"when": [
+				{
+					"path": "bounds.held",
+					"equals": true
+				},
+				{
+					"path": "review.approved",
+					"equals": true
+				},
+				{
+					"path": "test.passed",
+					"equals": true
+				},
+				{
+					"path": "fingerprints.fresh",
+					"equals": true
+				}
+			]
+		},
+		{
+			"from": "review",
+			"to": "needs-human",
+			"when": [
+				{
+					"path": "bounds.held",
+					"equals": true
+				},
+				{
+					"path": "review.approved",
+					"equals": true
+				},
+				{
+					"path": "test.passed",
+					"equals": false
+				}
+			]
+		},
+		{
+			"from": "review",
+			"to": "needs-human",
+			"when": [
+				{
+					"path": "bounds.held",
+					"equals": true
+				},
+				{
+					"path": "review.approved",
+					"equals": true
+				},
+				{
+					"path": "fingerprints.fresh",
+					"equals": false
+				}
+			]
+		},
+		{
+			"from": "review",
+			"to": "implement",
+			"when": [
+				{
+					"path": "bounds.held",
+					"equals": true
+				},
+				{
+					"path": "review.approved",
+					"equals": false
+				},
+				{
+					"path": "review.status",
+					"equals": "REVISE"
+				}
+			]
+		},
+		{
+			"from": "review",
+			"to": "needs-human",
+			"when": [
+				{
+					"path": "bounds.held",
+					"equals": true
+				},
+				{
+					"path": "review.approved",
+					"equals": false
+				},
+				{
+					"path": "review.status",
+					"equals": "BLOCKED"
+				}
+			]
+		},
+		{
+			"from": "human",
+			"to": "ship",
+			"when": [
+				{
+					"path": "release.approved",
+					"equals": true
+				},
+				{
+					"path": "ship.shipped",
+					"equals": false
+				}
+			]
+		},
+		{
+			"from": "human",
+			"to": "__end__",
+			"when": [
+				{
+					"path": "release.approved",
+					"equals": true
+				},
+				{
+					"path": "ship.shipped",
+					"equals": true
+				}
+			]
+		},
+		{
+			"from": "human",
+			"to": "implement",
+			"when": [
+				{
+					"path": "release.approved",
+					"equals": false
+				},
+				{
+					"path": "policy.onHumanDeny",
+					"equals": "revise"
+				}
+			]
+		},
+		{
+			"from": "human",
+			"to": "__end__",
+			"when": [
+				{
+					"path": "release.approved",
+					"equals": false
+				},
+				{
+					"path": "policy.onHumanDeny",
+					"equals": "end"
+				}
+			]
+		},
+		{
+			"from": "ship",
+			"to": "__end__"
+		}
+	],
+	"limits": {
+		"maxSteps": 24,
+		"maxNodeRuns": 16,
+		"maxConcurrency": 2,
+		"maxCostUsd": 5,
+		"timeoutMs": 1800000
+	},
+	"policy": {
+		"allowNonInteractive": false,
+		"allowNonInteractiveMutations": false,
+		"confirmProjectGraph": true,
+		"confirmMutatingNodes": true,
+		"onHumanDeny": "revise"
+	}
+}

package/dist/kpi/graphs/spec-first.json

@@ -0,0 +1,40 @@
+{
+  "schemaVersion": 2,
+  "id": "spec-first",
+  "entry": "specify",
+  "nodes": [
+    {
+      "id": "specify",
+      "type": "agent",
+      "prompt": "Apply the spec-first skill. Research the repository and produce requirements, design, tasks, constraints, non-goals, and executable acceptance criteria without changing production files.",
+      "context": { "mode": "isolated" },
+      "tools": ["read", "grep", "find", "ls"],
+      "readOnly": true
+    },
+    {
+      "id": "plan",
+      "type": "agent",
+      "prompt": "Turn the approved specification into ordered vertical slices and stack.json module boundaries without changing production files.",
+      "context": { "mode": "isolated" },
+      "tools": ["read", "grep", "find", "ls"],
+      "readOnly": true
+    }
+  ],
+  "edges": [
+    { "from": "specify", "to": "plan" },
+    { "from": "plan", "to": "__end__" }
+  ],
+  "limits": {
+    "maxSteps": 4,
+    "maxNodeRuns": 2,
+    "maxConcurrency": 1,
+    "maxCostUsd": 2,
+    "timeoutMs": 900000
+  },
+  "policy": {
+    "allowNonInteractive": false,
+    "allowNonInteractiveMutations": false,
+    "confirmProjectGraph": true,
+    "confirmMutatingNodes": true
+  }
+}

package/dist/kpi/kstack/NOTICE

@@ -0,0 +1,5 @@
+K-stack includes adaptations of pstack by Lauren Tan (@poteto), originally distributed in Cursor's plugins repository under the MIT License.
+
+Copyright (c) Lauren Tan and Cursor contributors.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files, to deal in the Software without restriction, subject to the conditions of the MIT License.

package/dist/kpi/kstack/UPSTREAM.md

@@ -0,0 +1,23 @@
+# K-stack upstream
+
+| Source | https://github.com/cursor/plugins.git |
+|---|---|
+| Path | pstack/ |
+| Commit | efa2a531985e0a8084d36ff3cf87233be8a9f34b |
+| pstack tree | 1c625329e71538629f087374daa71293a498089f |
+| Upstream version | main snapshot 2026-08-31 |
+| K-stack overlay | 1 |
+
+`provenance.json` beside this file is the machine-readable record: the same origin, commit and
+`pstack/` tree id, plus the transform version, the ordered patch digests, and the licence
+provenance. Both files move together, and only `npm run kstack:sync -- --pin <sha>` moves them.
+
+Drift is a tree, not a HEAD. `npm run kstack:sync:check` is offline: it rebuilds from the
+vendored `upstream/` subtree and fails on byte drift, on a semantic diagnostic, or on a pin
+whose recorded tree id no longer matches those bytes. `npm run kstack:status` reports whether
+upstream has moved and never changes the pin.
+
+Generated content is produced by `npm run kstack:sync`; runtime package loading never fetches
+the network.
+
+Pinned-deps (`scripts/check-pinned-deps.mjs`) excludes the vendored `upstream/` path only — a byte-for-byte mirror that keeps loose specs (e.g. `skills/poteto-mode/scripts/package.json` with `bun-types`/`typescript: "latest"`); `generated/` ships no `package.json`, and the overlay drops or pins any such manifests before emit.

package/dist/kpi/kstack/generated/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Lauren Tan
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/dist/kpi/kstack/generated/skills/architect/SKILL.md

@@ -0,0 +1,83 @@
+---
+name: architect
+description: "Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape."
+disable-model-invocation: true
+---
+
+# Architect
+
+Design before implementing. Sketch types, function signatures, class shapes, and module boundaries with `not implemented` bodies and pseudocode. Synthesize across multiple model perspectives, then fill in code against the chosen sketch. If implementation proves the sketch wrong, throw it out and redesign.
+
+## Start
+
+Open a todolist with one entry per phase before starting. Autonomous mode without checkpoints needs the list to show phase position and keep phases from silently disappearing.
+
+1. Ground
+2. Sketch
+3. Agree
+4. Implement
+5. Scrap
+
+## Phase A: Ground the problem
+
+Build a real mental model of every system the new code touches. Run the **how** skill over the relevant subsystems. Critique mode if existing structure is the constraint or the design must push back on it.
+
+Naming a file isn't grounding. Produce the traced model `how` prescribes. If the design redefines ownership or layering, also run the **why** skill on the existing shape so the rationale becomes a constraint, not a guess.
+
+Skip Phase A only when the work is genuinely greenfield with no surrounding system to integrate.
+
+## Phase B: Sketch
+
+Run the **arena** skill with the design-sketch task and the Phase A grounding artifacts. Pass `references/runner-prompt.md` as each runner's prompt. Each candidate produces a design package shaped per `references/rationale-template.md`: the caller's usage written first, then the type sketch, function signatures, module map, and prose rationale derived from it.
+
+Use your configured architect runners (roles resolved from `~/.kpi/agent/kstack/models.json`, set by `/setup-kstack`).
+
+Design it twice. Require at least two structurally distinct candidates before synthesis, even when the first looks sufficient. This is the **exhaust-the-design-space** principle skill made concrete. Whole-shape alternatives, not point fixes inside one shape.
+
+Screen every candidate against [`references/design-red-flags.md`](references/design-red-flags.md) before synthesis. Reject or revise shallow modules, information leakage, temporal decomposition, and pass-through methods.
+
+Compare viable candidates on interface depth. Prefer the design that hides more complexity behind a smaller, simpler public surface. A rich interface can keep call chains short by concentrating capability instead of scattering it across layers.
+
+Arena returns one synthesized design package. The synthesis decision populates the rationale's "Synthesis decision" section.
+
+## Phase C: Agree (opt-in)
+
+Default: proceed directly to implementation with the synthesized design. No human checkpoint.
+
+Opt in to a checkpoint when the invoker explicitly asks: "/architect with checkpoint," "stop and show me before implementing," or similar. Then surface the synthesized design and pause for sign-off.
+
+The synthesis can ship as its own commit either way. That's the "scaffold first" mode of the **foundational-thinking** principle skill; subsequent commits read as filling in bodies against a stable contract. Planned and scoped breakage during fill-in is fine, per the **outcome-oriented-execution** principle skill. For adversarial pressure on the design before implementing, run the **interrogate** skill on the synthesized sketch.
+
+If the human pushes back on the shape (in a checkpoint or after the fact), treat that as Phase A evidence. Re-ground and re-run Phase B before writing more code.
+
+## Phase D: Implement against the sketch
+
+Replace `not implemented` bodies with code, pseudocode with logic. The synthesized sketch is the contract.
+
+Deviations from the sketch are signal worth surfacing, not friction to absorb silently. If a function needs a parameter the sketch didn't anticipate, ask whether the sketch was wrong, the requirement was missed, or the implementation is overreaching. Surface it; don't bolt it on.
+
+## Phase E: Scrap when the architecture is wrong
+
+If implementation keeps producing friction the sketch can't absorb, throw the sketch out. Don't bolt fixes onto a wrong design, per the **redesign-from-first-principles** and **fix-root-causes** principle skills.
+
+The signal is a *pattern*, not single instances. Tells:
+
+- The same shape of workaround appearing repeatedly across unrelated code.
+- Multiple unrelated edge cases that all need special-case branches.
+- Types that need escape hatches (`any`, casts, optional fields always set in practice) to compile.
+- The "we need a lock" reflex when the sketch said the state wasn't shared.
+- Callers having to know the abstraction's internal rules to use it.
+- Two or more independent Phase D deviations of the same shape across the implementation. Surfacing deviations is Phase D's job; a repeated pattern of them is Phase E's trigger.
+
+Use judgment. A few edge cases don't condemn an architecture. Some problems are legitimately complex; complexity in the data is not complexity in the design. The rewrite signal is repeated friction of the same shape, not single hard cases.
+
+When you scrap:
+
+1. Re-run the **how** skill over what's been built. The implementation lessons enter the new design as inputs, not vibes.
+2. Redesign as if the new constraints had been day-one assumptions, per redesign-from-first-principles.
+3. Subtract before adding, per the **subtract-before-you-add** principle skill. The new sketch should be smaller than the old one before it grows.
+4. Return to Phase B and re-run arena.
+
+## Outputs
+
+The caller's usage is written first and the type sketch derived from it. One file with new types and signatures for small changes; module map plus type definitions for larger work. The rationale ships alongside, shaped per `references/rationale-template.md`, including the usage sketch and the synthesis decision.

package/dist/kpi/kstack/generated/skills/architect/references/design-red-flags.md

@@ -0,0 +1,33 @@
+# Design red flags
+
+Screen every candidate before synthesis. A red flag is a reason to revise or reject the shape.
+
+## Shallow module
+
+A shallow module exposes a large interface while hiding little complexity. Judge depth by the capability and policy hidden behind the public surface relative to the size of that surface. Prefer a simple interface backed by substantial behavior.
+
+Do not confuse a deep module with a deep call chain. A deep call chain scatters understanding across layers. A deep module concentrates capability behind one interface.
+
+Look for these signs:
+
+- Callers coordinate several methods to complete one operation.
+- Public options expose internal stages or implementation choices.
+- Learning the interface does not save the caller from learning the implementation.
+
+## Information leakage
+
+Information leakage makes multiple modules depend on the same internal decision. A representation, policy, or protocol detail appears in more than one place, so changing it requires coordinated edits.
+
+Public re-exports of transport or wire types are leakage. Parse external data into domain types behind the interface. Keep storage schemas, framework objects, and protocol details private.
+
+## Temporal decomposition
+
+Temporal decomposition organizes modules by execution order instead of the knowledge they own. Separate load, validate, transform, and save stages often repeat one representation and its invariants across several boundaries.
+
+Group code around domain knowledge and ownership. Methods that run at different times can still belong to one module when they protect the same decisions.
+
+## Pass-through method
+
+A pass-through method forwards the same arguments to another method with the same shape. It adds a layer without hiding complexity.
+
+Remove it or move responsibility to the module that can complete the operation. Keep a forwarding boundary only when it adds policy, adaptation, or a distinct abstraction.

package/dist/kpi/kstack/generated/skills/architect/references/rationale-template.md

@@ -0,0 +1,35 @@
+# Rationale template
+
+The prose that ships alongside the type sketch. One page. Sentence-case headings, no boilerplate. Replace the italic notes with actual content.
+
+## Problem
+
+*One paragraph. What we're trying to do, and what about the existing system or constraints makes the shape non-obvious. If [Phase A](../SKILL.md#phase-a-ground-the-problem) surfaced constraints the design must honor (existing types to interop with, callers we can't break, invariants that crossed our boundary), name them here so the reader sees the same constraints you saw.*
+
+## Usage (caller's view)
+
+*Write this first, before the type sketch. Show the README or quickstart the consumer reads, plus two or three realistic call sites in their own code. What they import, what they call, what comes back. The type sketch in [Shape](#shape) is derived from this. The two must agree; when they diverge, reconcile the sketch to the usage, not the reverse. The caller's experience is the spec. The types serve it.*
+
+## Shape
+
+*The recommended architecture. Data structures first; then how data flows through the signatures. Name the load-bearing decisions. State which invariants are encoded in types, where validation lives, and what the system deliberately does not do. Judge interface depth explicitly. State what complexity the public surface hides, what remains exposed to callers, and why the interface is no larger than needed. Cite the principle behind each decision (e.g., `per boundary-discipline`); don't restate it.*
+
+## Synthesis decision
+
+*Filled in by [arena](../../arena/SKILL.md). Records which candidate became the base and why, what was adapted from each of the others, and what was rejected and why.*
+
+## Tradeoffs accepted
+
+*One bullet per tradeoff the chosen shape makes. Form: "we accept X in exchange for Y." Name anything a future reader might mistake for an oversight, including things that look like premature optimization or premature simplification.*
+
+## Alternatives considered
+
+*Required. Name at least one concrete alternative shape, with one line on why it lost. Judge each alternative on interface depth, not implementation simplicity alone. Name the complexity it exposes to callers and the complexity it hides. Two or three alternatives belong here when the design space had real contenders. One is fine when the constraints forced the answer, with the conclusion phrased as "this was the only viable shape because..." Avoid listing flavors of the same shape. This section covers design alternatives the chosen shape considered and rejected, not other runner candidates.*
+
+## Open questions and risks
+
+*Things you noticed during the sketch that the human needs to weigh in on, and risks worth flagging before implementation starts. Phrase as questions, not assertions, so the human's answer is the resolution rather than a comment.*
+
+## Next implementation step
+
+*The first thing to build against the sketch. One sentence. What you'd start writing immediately after synthesis (or after Phase D sign-off, if a checkpoint was opted into).*