mokata 0.0.9rc1__tar.gz

mokata-0.0.9rc1/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or Derivative
+          Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work, excluding
+          those notices that do not pertain to any part of the Derivative
+          Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and do
+          not modify the License. You may add Your own attribution notices
+          within Derivative Works that You distribute, alongside or as an
+          addendum to the NOTICE text from the Work, provided that such
+          additional attribution notices cannot be construed as modifying
+          the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 MoStack
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

mokata-0.0.9rc1/NOTICE

@@ -0,0 +1,8 @@
+mokata
+Copyright 2026 MoStack
+
+This product is licensed under the Apache License, Version 2.0 (see LICENSE).
+
+mokata is built clean-room. Its methodology and prompt devices are reimplemented
+in mokata's own terminology; mokata takes no dependency on, and imports no code
+or text from, any other AI-assisted-coding methodology framework.

mokata-0.0.9rc1/PKG-INFO

@@ -0,0 +1,203 @@
+Metadata-Version: 2.4
+Name: mokata
+Version: 0.0.9rc1
+Summary: An open-source, spec-driven TDD framework for Claude Code — governed, knowledge-aware, human-gated.
+Author: MoStack
+License: Apache-2.0
+Keywords: claude-code,tdd,spec-driven,framework,ai-assisted-coding
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: mcp>=1.2; python_version >= "3.10"
+Provides-Extra: schema
+Requires-Dist: jsonschema>=4.0; extra == "schema"
+Provides-Extra: mcp
+Requires-Dist: mcp>=1.2; python_version >= "3.10" and extra == "mcp"
+Provides-Extra: postgres
+Requires-Dist: psycopg>=3.1; extra == "postgres"
+Provides-Extra: neo4j
+Requires-Dist: neo4j>=5.0; extra == "neo4j"
+Dynamic: license-file
+
+# mokata
+
+**The memory + seatbelt for your AI coding agent.** Spec-driven TDD for Claude Code —
+knowledge-aware, self-healing memory, human-gated, local-first. It remembers your project and
+stops the agent shipping the wrong thing.
+
+[![License: Apache-2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](LICENSE)
+[![CI](https://github.com/JasGujral/mokata-oss/actions/workflows/ci.yml/badge.svg)](https://github.com/JasGujral/mokata-oss/actions/workflows/ci.yml)
+[![Version](https://img.shields.io/github/v/release/JasGujral/mokata-oss?label=version)](https://github.com/JasGujral/mokata-oss/releases/latest)
+[![Python](https://img.shields.io/badge/python-3.9%E2%80%933.12-blue.svg)](pyproject.toml)
+[![Docs](https://img.shields.io/badge/docs-mkdocs-blue.svg)](https://jasgujral.github.io/mokata-oss/)
+[![local-first](https://img.shields.io/badge/local--first-no%20telemetry-success.svg)](docs/concepts/governance.md)
+[![OpenSSF Scorecard](https://api.securityscorecards.dev/projects/github.com/JasGujral/mokata-oss/badge)](https://securityscorecards.dev/viewer/?uri=github.com/JasGujral/mokata-oss)
+
+📖 **Full documentation:** **<https://jasgujral.github.io/mokata-oss/>** — quickstart, tutorials, concepts, and the complete CLI + plugin reference.
+
+---
+
+## See it catch a bad change (30 seconds)
+
+An AI agent, mid-task, tries two bad changes — ship code with no spec, and stash a secret.
+mokata stops both, and puts both on the audit ledger. (Real output; run it yourself with
+`mokata init --profile standard --yes` in a scratch repo.)
+
+```console
+$ mokata run develop          # the agent tries to write code with no spec...
+[BLOCKED] spec-persisted — no saved spec — draft and emit it first (/mokata:spec); the completeness gate must pass before implementation.
+
+$ # ...and tries to stash a secret (even with approve=True):
+status: blocked   findings: ['aws-access-key', 'high-entropy-token', 'sensitive-location']
+
+$ mokata audit                # every block is on the ledger
+audit ledger — 2 entries:
+  #1   gate        gate=spec-persisted phase=develop decision=blocked reason=no saved spec ...
+  #2   write_gate  write_kind=memory target=memory:aws.key actor=mcp decision=blocked reason=secret detected
+```
+
+**The full copy-paste demo + a 60-second screencast script:** [mokata catches a bad change](docs/tutorials/catches-a-bad-change.md). See *every* differentiator run in [differentiators in action](docs/tutorials/differentiators-in-action.md).
+
+---
+
+## See mokata in action
+
+A quick tour of the workflow and skills — brainstorm → spec → test → develop → review → ship, with governance, memory, and the always-on status badge.
+
+https://github.com/user-attachments/assets/a6940119-1edb-4017-b935-cd48b80b4ea9
+
+> ▶ Video not playing inline? [Watch it here](https://github.com/user-attachments/assets/a6940119-1edb-4017-b935-cd48b80b4ea9).
+
+---
+
+**mokata** is an open-source framework for Claude Code that brings the best ideas in AI-assisted coding into one governed, knowledge-aware engine. At its core is a spec-driven TDD engine that starts by **brainstorming the problem with you** — one question at a time, weighing two or three real approaches grounded in your actual codebase before committing to anything. Only then does it draft a spec, and no code is written until that specification passes a *provable completeness gate*, every acceptance criterion is statically mapped to a test (RED before GREEN), and the finished code is reviewed back against the spec. Around that engine, mokata builds in the layers a single tool usually leaves out — a **persistent codebase knowledge graph** so the agent navigates by structure instead of guessing, **persistent, self-healing memory** (decisions, conventions, and past conversations that survive across sessions and surface their own contradictions instead of silently rotting), and **active token-and-cost governance** that retrieves just what's needed rather than dumping files into context. **Memory and its self-healing ship as part of the framework, on by default — not an add-on you wire up.** It can also orchestrate the external tools you already trust — like code graphs — under one set of gates with a full audit trail, and every durable write, whether to code, memory, or config, is **human-gated**: nothing silent, nothing autonomous. And it's **fully configurable and composable** — switch any layer or tool on or off, pick a profile, or reach for a single capability on its own: generate tests, debug a failure, or review a diff as a standalone command or directly-invoked skill, entering the pipeline wherever you need rather than running the whole thing. mokata is local-first, phones home nothing by default, is Apache-2.0 licensed, and is built so you can review every decision it makes.
+
+> **Naming:** **mokata** = the framework · **MoStack** = the brand it ships under.
+
+## Why mokata
+
+- **Spec-driven, provable completeness.** No code ships until every acceptance criterion maps to a test (RED before GREEN). The completeness gate *blocks* emit — it never silently passes.
+- **Knowledge + memory built in.** A codebase knowledge graph (adopted, with a grep floor) and persistent, self-healing memory (on by default) — the agent navigates by structure and remembers decisions across sessions.
+- **Governed by default.** Every durable write (code, memory, config) is human-gated; sync hooks block only for security (exit 2), async hooks observe; every gate decision and tool call lands in an append-only audit ledger.
+- **Local-first, no telemetry.** Nothing leaves your machine unless you explicitly wire an external service. The `minimal` profile performs zero network egress.
+- **Configurable & composable.** Toggle any layer/tool, pick a profile, run any capability standalone, and enter the pipeline from any phase.
+- **Meets you where you work, ships trustworthy.** Runs under Claude Code, Cursor, Copilot, Windsurf, Codex, Gemini CLI, and Aider (a VS Code extension is planned, not in 0.0.9); sessions travel between machines; teams share one governed backend safely; and releases carry an SBOM + Sigstore provenance — no telemetry, ever.
+
+## Install
+
+**Start here → [Getting started](docs/getting-started.md).** The canonical, pip-first path.
+
+**In Claude Code (recommended)** — one install, then one command wires the full workflow
+(slash commands + Agent Skills + MCP server + status line), on your existing Claude Code
+sign-in — no API key:
+
+```bash
+pip install mokata               # MCP server works out of the box on Python ≥ 3.10 (SDK is a default dep)
+mokata setup claude              # wires commands + skills + MCP + statusline — human-gated
+# restart Claude Code, then:
+mokata mcp status                # expect: mokata-mcp: CONNECTED ✓
+```
+
+> On **Python 3.9** the MCP server is unavailable (it needs ≥ 3.10) — the CLI and everything
+> else still work.
+
+**As a CLI, with any AI tool** — harness-agnostic (Gemini, Codex, scripts, CI). The CLI is the
+engine's mechanics (no LLM of its own); wire it into any shell- or MCP-capable assistant:
+
+```bash
+pip install mokata
+mokata init
+```
+
+See [Integrate with other AI tools](docs/how-to/integrate-other-ai-tools.md).
+
+<!-- mokata:directory-listing:start -->
+> ⏳ **Pending Claude plugin-directory approval.** A one-click Claude Code **plugin** is
+> **planned, not yet available** — mokata isn't registered on any Claude Code marketplace.
+> The supported way to run mokata inside Claude Code today is the pip-first path:
+> `pip install mokata` → `mokata setup claude`
+> (see [Getting started](https://jasgujral.github.io/mokata-oss/getting-started/)).
+> _(This notice auto-flips once the listing is approved — single source:
+> `scripts/directory_listing.py`.)_
+<!-- mokata:directory-listing:end -->
+
+> **Contributing (developers).** Only clone if you're working on mokata itself — end users never
+> need to: `git clone https://github.com/JasGujral/mokata-oss.git && cd mokata-oss && pip install -e .`
+> (on Python ≥ 3.10 this also pulls the MCP SDK). See [CONTRIBUTING.md](CONTRIBUTING.md).
+
+## Quickstart
+
+**In Claude Code (primary)** — after `mokata setup claude`, drive the workflow with slash commands:
+
+```text
+/mokata:brainstorm        # Socratic pre-spec exploration (HARD-GATE before any spec)
+/mokata:spec              # draft the spec (blocked until every acceptance criterion maps to a test)
+/mokata:test  /mokata:develop    # RED-before-GREEN
+/mokata:review            # spec-compliance, then quality
+```
+
+**Or via the CLI** (outside Claude Code):
+
+```bash
+mokata init                         # scaffold .mokata/ (default profile: standard); human-gated
+mokata brainstorm                   # Socratic pre-spec exploration (HARD-GATE before spec)
+mokata playbook                     # drive the full story end-to-end through the pipeline
+```
+
+> A `pip` CLI install is **terminal-only** — it runs the deterministic engine with no LLM
+> attached. It does **not** put mokata inside Claude Code; for that, install the plugin or run
+> `mokata setup claude`. ([Why two ways](https://jasgujral.github.io/mokata-oss/concepts/execution-model/).)
+
+Full walkthrough: [`docs/quickstart.md`](docs/quickstart.md) · full hands-on guide → [the Complete Guide](https://jasgujral.github.io/mokata-oss/tutorials/mokata-complete-guide/) (with a downloadable PDF) · published docs: <https://jasgujral.github.io/mokata-oss/>
+
+## Core concepts
+
+- **7-phase pipeline + gates** — brainstorm → analysis → strawman → pre-mortem → probes → completeness gate → emit; enter at any phase, each phase's gates still apply.
+- **Knowledge layer** — structural queries (callers/callees/imports/blast-radius) via an adopted graph, grep floor when absent; staleness is surfaced, never served silently.
+- **Memory** — persistent / decision / episodic, on by default, self-healing by *surfacing* old→new diffs for your approval (never a silent rewrite).
+- **Execution modes** — sequential gated flow (default, lowest-cost) or parallel subagents (fresh-context isolation + two-stage review, concurrent fan-out), chosen per run, degrade-safe; optional git-worktree isolation keeps concurrent/paused work off the main tree.
+- **Governance & audit** — 4-tier rules, Karpathy gates, 4-layer secret protection, per-task model routing, reversible writes, full audit ledger. See the governed state at a glance with `mokata govern` (a read-only dashboard) and the *what-it-did-and-why* timeline with `mokata audit --why`.
+- **Session lifecycle & portable sessions** — list runs (`mokata sessions`), resume from the last passed gate (`mokata resume`), pause/resume a mid-brainstorm (the HARD-GATE still holds), and **carry a session across machines or hand it to a teammate**: `mokata session push <tag>` / `pull <tag>` packages checkpoints + approach + in-progress brainstorm + relevant memory into a machine-path-free, versioned, **secret-scanned + human-gated** bundle. Sessions carry a human-friendly name you can `rename`.
+- **Progress & visibility, one model** — one `RunProgress` drives every surface: an always-on **stage badge** (statusline, on by default, merge-safe), the native **to-do widget** where the harness has one, the printed run-progress block, and the per-subagent **lanes** in `mokata watch` / `progress --lanes`. No duplicated progress logic — channel-specific renderers over one source of truth.
+- **Runs under every agent, shows up in your editor** — the engine runs behind a thin boundary (`mokata harness` shows the capability matrix) with in-harness surfaces for **Claude Code, Cursor, GitHub Copilot, Windsurf, Codex, Gemini CLI, and Aider**, each degrading clearly where it lacks a capability. A **VS Code extension** (`editors/vscode`) with a read-only Copilot Chat `@mokata` participant — governance, memory, and run-progress in your editor — is **planned (not in 0.0.9)**.
+- **Team & sharing** — one guided `mokata team join` chains adopt → shared memory (BYO Postgres) → vault pull → onboard → doctor (each human-gated, secret-scanned, reversible); publish/adopt governed per-framework **community stacks** (`mokata stacks`); and the team's **audit/activity logs** can live shared or local, conflict-free — **no telemetry, nothing phoned home**. One shared backend safely hosts **many projects**: every shared row is scoped by a stable project key, so review defaults to your project (`--all` / `--project` to span or pick).
+- **Supply-chain trust** — releases ship a reproducible sdist+wheel, a **CycloneDX SBOM**, and a **Sigstore build-provenance attestation** generated at tag-time in CI (the repo ships no pre-signed artifacts); all five CI workflows are least-privilege and SHA-pinned.
+
+## Profiles & configuration
+
+| Profile | Layers | Capabilities | Network |
+|---|---|---|---|
+| `minimal` | engine, governance | none (engine only) | **zero egress** |
+| `standard` **(default)** | + knowledge, memory | code graph (ripgrep→grep) + memory (SQLite) | local-only |
+| `full` | all | every known graph + memory provider (degrade to floors) | only present tools, all gated |
+
+Per-layer / per-tool toggles, per-adapter trust dials, and profiles are all in the committed manifest. See [`docs/profiles.md`](docs/profiles.md).
+
+## Commands & skills
+
+`mokata skills` lists the catalog. Skills (each a `/mokata:*` command): `brainstorm`, `refine`, `onboard`, `spec`, `test`, `develop`, `review`, `debug`, `optimize`, `bug`, `ship`, `version`.
+
+The CLI exposes 40+ subcommands, including:
+
+- **Pipeline & skills** — `brainstorm`, `spec`, `test`, `develop`, `review`, `ship`, `refine`, `debug`, `bug`, `optimize`, `onboard`, plus `run`/`enter`/`exec`/`playbook` (`--dense`)/`preview`/`chain` and `skill author`.
+- **Inspection (read-only)** — `status`, `query`, `rules`, `audit` (`--why`), `budget`, `coverage`, `lat-check`, `index`, `doctor`, `baseline`, `harness`, `progress` (`--lanes`), `watch`, `govern`, `sessions`.
+- **Memory & knowledge** — `memory` (`edit`/`export`/`import`/`migrate`/`consolidate`), `govern`.
+- **Session lifecycle & portability** — `sessions`, `resume`, `enter`, `session` (`push`/`pull`/`list`/`name`).
+- **Team, stacks & sharing** — `team` (`join`/`adopt`/`connect`), `stacks` (`list`/`search`/`show`/`install`), `vault`, `marketplace`.
+- **Setup, config & distribution** — `init`, `setup`/`unsetup`, `reconfigure`, `tour`, `config`, `bootstrap`, `validate`, `route`, `detect`, `reset`, `suggest`, `mcp`, `ci-check`, `export`/`import`, `version`/`upgrade`, `release-check`.
+
+Full list with flags: the [CLI reference](https://jasgujral.github.io/mokata-oss/reference/cli/).
+
+## Contributing · Security · License
+
+- [`CONTRIBUTING.md`](CONTRIBUTING.md) — dev setup, the clean-room rule, tests in both jsonschema states.
+- [`SECURITY.md`](SECURITY.md) — how to report a vulnerability (privately).
+- [`CODE_OF_CONDUCT.md`](CODE_OF_CONDUCT.md) — Contributor Covenant.
+- [`LICENSE`](LICENSE) — Apache-2.0, © MoStack. mokata is built clean-room (no dependency on any other framework).
+
+## Links
+
+- **Documentation: <https://jasgujral.github.io/mokata-oss/>** (the published docs site; source in `docs/`, built with MkDocs)
+- Changelog: [`CHANGELOG.md`](CHANGELOG.md)
+- Issues & discussions: the repository's Issues / Discussions tabs

mokata-0.0.9rc1/README.md

@@ -0,0 +1,181 @@
+# mokata
+
+**The memory + seatbelt for your AI coding agent.** Spec-driven TDD for Claude Code —
+knowledge-aware, self-healing memory, human-gated, local-first. It remembers your project and
+stops the agent shipping the wrong thing.
+
+[![License: Apache-2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](LICENSE)
+[![CI](https://github.com/JasGujral/mokata-oss/actions/workflows/ci.yml/badge.svg)](https://github.com/JasGujral/mokata-oss/actions/workflows/ci.yml)
+[![Version](https://img.shields.io/github/v/release/JasGujral/mokata-oss?label=version)](https://github.com/JasGujral/mokata-oss/releases/latest)
+[![Python](https://img.shields.io/badge/python-3.9%E2%80%933.12-blue.svg)](pyproject.toml)
+[![Docs](https://img.shields.io/badge/docs-mkdocs-blue.svg)](https://jasgujral.github.io/mokata-oss/)
+[![local-first](https://img.shields.io/badge/local--first-no%20telemetry-success.svg)](docs/concepts/governance.md)
+[![OpenSSF Scorecard](https://api.securityscorecards.dev/projects/github.com/JasGujral/mokata-oss/badge)](https://securityscorecards.dev/viewer/?uri=github.com/JasGujral/mokata-oss)
+
+📖 **Full documentation:** **<https://jasgujral.github.io/mokata-oss/>** — quickstart, tutorials, concepts, and the complete CLI + plugin reference.
+
+---
+
+## See it catch a bad change (30 seconds)
+
+An AI agent, mid-task, tries two bad changes — ship code with no spec, and stash a secret.
+mokata stops both, and puts both on the audit ledger. (Real output; run it yourself with
+`mokata init --profile standard --yes` in a scratch repo.)
+
+```console
+$ mokata run develop          # the agent tries to write code with no spec...
+[BLOCKED] spec-persisted — no saved spec — draft and emit it first (/mokata:spec); the completeness gate must pass before implementation.
+
+$ # ...and tries to stash a secret (even with approve=True):
+status: blocked   findings: ['aws-access-key', 'high-entropy-token', 'sensitive-location']
+
+$ mokata audit                # every block is on the ledger
+audit ledger — 2 entries:
+  #1   gate        gate=spec-persisted phase=develop decision=blocked reason=no saved spec ...
+  #2   write_gate  write_kind=memory target=memory:aws.key actor=mcp decision=blocked reason=secret detected
+```
+
+**The full copy-paste demo + a 60-second screencast script:** [mokata catches a bad change](docs/tutorials/catches-a-bad-change.md). See *every* differentiator run in [differentiators in action](docs/tutorials/differentiators-in-action.md).
+
+---
+
+## See mokata in action
+
+A quick tour of the workflow and skills — brainstorm → spec → test → develop → review → ship, with governance, memory, and the always-on status badge.
+
+https://github.com/user-attachments/assets/a6940119-1edb-4017-b935-cd48b80b4ea9
+
+> ▶ Video not playing inline? [Watch it here](https://github.com/user-attachments/assets/a6940119-1edb-4017-b935-cd48b80b4ea9).
+
+---
+
+**mokata** is an open-source framework for Claude Code that brings the best ideas in AI-assisted coding into one governed, knowledge-aware engine. At its core is a spec-driven TDD engine that starts by **brainstorming the problem with you** — one question at a time, weighing two or three real approaches grounded in your actual codebase before committing to anything. Only then does it draft a spec, and no code is written until that specification passes a *provable completeness gate*, every acceptance criterion is statically mapped to a test (RED before GREEN), and the finished code is reviewed back against the spec. Around that engine, mokata builds in the layers a single tool usually leaves out — a **persistent codebase knowledge graph** so the agent navigates by structure instead of guessing, **persistent, self-healing memory** (decisions, conventions, and past conversations that survive across sessions and surface their own contradictions instead of silently rotting), and **active token-and-cost governance** that retrieves just what's needed rather than dumping files into context. **Memory and its self-healing ship as part of the framework, on by default — not an add-on you wire up.** It can also orchestrate the external tools you already trust — like code graphs — under one set of gates with a full audit trail, and every durable write, whether to code, memory, or config, is **human-gated**: nothing silent, nothing autonomous. And it's **fully configurable and composable** — switch any layer or tool on or off, pick a profile, or reach for a single capability on its own: generate tests, debug a failure, or review a diff as a standalone command or directly-invoked skill, entering the pipeline wherever you need rather than running the whole thing. mokata is local-first, phones home nothing by default, is Apache-2.0 licensed, and is built so you can review every decision it makes.
+
+> **Naming:** **mokata** = the framework · **MoStack** = the brand it ships under.
+
+## Why mokata
+
+- **Spec-driven, provable completeness.** No code ships until every acceptance criterion maps to a test (RED before GREEN). The completeness gate *blocks* emit — it never silently passes.
+- **Knowledge + memory built in.** A codebase knowledge graph (adopted, with a grep floor) and persistent, self-healing memory (on by default) — the agent navigates by structure and remembers decisions across sessions.
+- **Governed by default.** Every durable write (code, memory, config) is human-gated; sync hooks block only for security (exit 2), async hooks observe; every gate decision and tool call lands in an append-only audit ledger.
+- **Local-first, no telemetry.** Nothing leaves your machine unless you explicitly wire an external service. The `minimal` profile performs zero network egress.
+- **Configurable & composable.** Toggle any layer/tool, pick a profile, run any capability standalone, and enter the pipeline from any phase.
+- **Meets you where you work, ships trustworthy.** Runs under Claude Code, Cursor, Copilot, Windsurf, Codex, Gemini CLI, and Aider (a VS Code extension is planned, not in 0.0.9); sessions travel between machines; teams share one governed backend safely; and releases carry an SBOM + Sigstore provenance — no telemetry, ever.
+
+## Install
+
+**Start here → [Getting started](docs/getting-started.md).** The canonical, pip-first path.
+
+**In Claude Code (recommended)** — one install, then one command wires the full workflow
+(slash commands + Agent Skills + MCP server + status line), on your existing Claude Code
+sign-in — no API key:
+
+```bash
+pip install mokata               # MCP server works out of the box on Python ≥ 3.10 (SDK is a default dep)
+mokata setup claude              # wires commands + skills + MCP + statusline — human-gated
+# restart Claude Code, then:
+mokata mcp status                # expect: mokata-mcp: CONNECTED ✓
+```
+
+> On **Python 3.9** the MCP server is unavailable (it needs ≥ 3.10) — the CLI and everything
+> else still work.
+
+**As a CLI, with any AI tool** — harness-agnostic (Gemini, Codex, scripts, CI). The CLI is the
+engine's mechanics (no LLM of its own); wire it into any shell- or MCP-capable assistant:
+
+```bash
+pip install mokata
+mokata init
+```
+
+See [Integrate with other AI tools](docs/how-to/integrate-other-ai-tools.md).
+
+<!-- mokata:directory-listing:start -->
+> ⏳ **Pending Claude plugin-directory approval.** A one-click Claude Code **plugin** is
+> **planned, not yet available** — mokata isn't registered on any Claude Code marketplace.
+> The supported way to run mokata inside Claude Code today is the pip-first path:
+> `pip install mokata` → `mokata setup claude`
+> (see [Getting started](https://jasgujral.github.io/mokata-oss/getting-started/)).
+> _(This notice auto-flips once the listing is approved — single source:
+> `scripts/directory_listing.py`.)_
+<!-- mokata:directory-listing:end -->
+
+> **Contributing (developers).** Only clone if you're working on mokata itself — end users never
+> need to: `git clone https://github.com/JasGujral/mokata-oss.git && cd mokata-oss && pip install -e .`
+> (on Python ≥ 3.10 this also pulls the MCP SDK). See [CONTRIBUTING.md](CONTRIBUTING.md).
+
+## Quickstart
+
+**In Claude Code (primary)** — after `mokata setup claude`, drive the workflow with slash commands:
+
+```text
+/mokata:brainstorm        # Socratic pre-spec exploration (HARD-GATE before any spec)
+/mokata:spec              # draft the spec (blocked until every acceptance criterion maps to a test)
+/mokata:test  /mokata:develop    # RED-before-GREEN
+/mokata:review            # spec-compliance, then quality
+```
+
+**Or via the CLI** (outside Claude Code):
+
+```bash
+mokata init                         # scaffold .mokata/ (default profile: standard); human-gated
+mokata brainstorm                   # Socratic pre-spec exploration (HARD-GATE before spec)
+mokata playbook                     # drive the full story end-to-end through the pipeline
+```
+
+> A `pip` CLI install is **terminal-only** — it runs the deterministic engine with no LLM
+> attached. It does **not** put mokata inside Claude Code; for that, install the plugin or run
+> `mokata setup claude`. ([Why two ways](https://jasgujral.github.io/mokata-oss/concepts/execution-model/).)
+
+Full walkthrough: [`docs/quickstart.md`](docs/quickstart.md) · full hands-on guide → [the Complete Guide](https://jasgujral.github.io/mokata-oss/tutorials/mokata-complete-guide/) (with a downloadable PDF) · published docs: <https://jasgujral.github.io/mokata-oss/>
+
+## Core concepts
+
+- **7-phase pipeline + gates** — brainstorm → analysis → strawman → pre-mortem → probes → completeness gate → emit; enter at any phase, each phase's gates still apply.
+- **Knowledge layer** — structural queries (callers/callees/imports/blast-radius) via an adopted graph, grep floor when absent; staleness is surfaced, never served silently.
+- **Memory** — persistent / decision / episodic, on by default, self-healing by *surfacing* old→new diffs for your approval (never a silent rewrite).
+- **Execution modes** — sequential gated flow (default, lowest-cost) or parallel subagents (fresh-context isolation + two-stage review, concurrent fan-out), chosen per run, degrade-safe; optional git-worktree isolation keeps concurrent/paused work off the main tree.
+- **Governance & audit** — 4-tier rules, Karpathy gates, 4-layer secret protection, per-task model routing, reversible writes, full audit ledger. See the governed state at a glance with `mokata govern` (a read-only dashboard) and the *what-it-did-and-why* timeline with `mokata audit --why`.
+- **Session lifecycle & portable sessions** — list runs (`mokata sessions`), resume from the last passed gate (`mokata resume`), pause/resume a mid-brainstorm (the HARD-GATE still holds), and **carry a session across machines or hand it to a teammate**: `mokata session push <tag>` / `pull <tag>` packages checkpoints + approach + in-progress brainstorm + relevant memory into a machine-path-free, versioned, **secret-scanned + human-gated** bundle. Sessions carry a human-friendly name you can `rename`.
+- **Progress & visibility, one model** — one `RunProgress` drives every surface: an always-on **stage badge** (statusline, on by default, merge-safe), the native **to-do widget** where the harness has one, the printed run-progress block, and the per-subagent **lanes** in `mokata watch` / `progress --lanes`. No duplicated progress logic — channel-specific renderers over one source of truth.
+- **Runs under every agent, shows up in your editor** — the engine runs behind a thin boundary (`mokata harness` shows the capability matrix) with in-harness surfaces for **Claude Code, Cursor, GitHub Copilot, Windsurf, Codex, Gemini CLI, and Aider**, each degrading clearly where it lacks a capability. A **VS Code extension** (`editors/vscode`) with a read-only Copilot Chat `@mokata` participant — governance, memory, and run-progress in your editor — is **planned (not in 0.0.9)**.
+- **Team & sharing** — one guided `mokata team join` chains adopt → shared memory (BYO Postgres) → vault pull → onboard → doctor (each human-gated, secret-scanned, reversible); publish/adopt governed per-framework **community stacks** (`mokata stacks`); and the team's **audit/activity logs** can live shared or local, conflict-free — **no telemetry, nothing phoned home**. One shared backend safely hosts **many projects**: every shared row is scoped by a stable project key, so review defaults to your project (`--all` / `--project` to span or pick).
+- **Supply-chain trust** — releases ship a reproducible sdist+wheel, a **CycloneDX SBOM**, and a **Sigstore build-provenance attestation** generated at tag-time in CI (the repo ships no pre-signed artifacts); all five CI workflows are least-privilege and SHA-pinned.
+
+## Profiles & configuration
+
+| Profile | Layers | Capabilities | Network |
+|---|---|---|---|
+| `minimal` | engine, governance | none (engine only) | **zero egress** |
+| `standard` **(default)** | + knowledge, memory | code graph (ripgrep→grep) + memory (SQLite) | local-only |
+| `full` | all | every known graph + memory provider (degrade to floors) | only present tools, all gated |
+
+Per-layer / per-tool toggles, per-adapter trust dials, and profiles are all in the committed manifest. See [`docs/profiles.md`](docs/profiles.md).
+
+## Commands & skills
+
+`mokata skills` lists the catalog. Skills (each a `/mokata:*` command): `brainstorm`, `refine`, `onboard`, `spec`, `test`, `develop`, `review`, `debug`, `optimize`, `bug`, `ship`, `version`.
+
+The CLI exposes 40+ subcommands, including:
+
+- **Pipeline & skills** — `brainstorm`, `spec`, `test`, `develop`, `review`, `ship`, `refine`, `debug`, `bug`, `optimize`, `onboard`, plus `run`/`enter`/`exec`/`playbook` (`--dense`)/`preview`/`chain` and `skill author`.
+- **Inspection (read-only)** — `status`, `query`, `rules`, `audit` (`--why`), `budget`, `coverage`, `lat-check`, `index`, `doctor`, `baseline`, `harness`, `progress` (`--lanes`), `watch`, `govern`, `sessions`.
+- **Memory & knowledge** — `memory` (`edit`/`export`/`import`/`migrate`/`consolidate`), `govern`.
+- **Session lifecycle & portability** — `sessions`, `resume`, `enter`, `session` (`push`/`pull`/`list`/`name`).
+- **Team, stacks & sharing** — `team` (`join`/`adopt`/`connect`), `stacks` (`list`/`search`/`show`/`install`), `vault`, `marketplace`.
+- **Setup, config & distribution** — `init`, `setup`/`unsetup`, `reconfigure`, `tour`, `config`, `bootstrap`, `validate`, `route`, `detect`, `reset`, `suggest`, `mcp`, `ci-check`, `export`/`import`, `version`/`upgrade`, `release-check`.
+
+Full list with flags: the [CLI reference](https://jasgujral.github.io/mokata-oss/reference/cli/).
+
+## Contributing · Security · License
+
+- [`CONTRIBUTING.md`](CONTRIBUTING.md) — dev setup, the clean-room rule, tests in both jsonschema states.
+- [`SECURITY.md`](SECURITY.md) — how to report a vulnerability (privately).
+- [`CODE_OF_CONDUCT.md`](CODE_OF_CONDUCT.md) — Contributor Covenant.
+- [`LICENSE`](LICENSE) — Apache-2.0, © MoStack. mokata is built clean-room (no dependency on any other framework).
+
+## Links
+
+- **Documentation: <https://jasgujral.github.io/mokata-oss/>** (the published docs site; source in `docs/`, built with MkDocs)
+- Changelog: [`CHANGELOG.md`](CHANGELOG.md)
+- Issues & discussions: the repository's Issues / Discussions tabs