napkinstack 0.7.0__tar.gz → 0.7.2__tar.gz

{napkinstack-0.7.0 → napkinstack-0.7.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: napkinstack
-Version: 0.7.0
+Version: 0.7.2
 Summary: Engineering framework for several teams and their agents working in one repository: modules, contracts, guardrails in CI.
 License-Expression: MIT
 License-File: LICENSE
@@ -20,27 +20,9 @@ modules, contracts, guardrails in CI. On the Django or Rails model, one command
 the project, which then receives new versions on demand; no application stack is imposed.
 Positioning and vocabulary: [`PRODUCT.md`](PRODUCT.md) §1.
 
-> **Status: v0.6.2, published** ([PyPI](https://pypi.org/project/napkinstack/)): what the
-> framework announces, it refuses — and what it cannot refuse, it says. The boundaries read the
-> contracts a module uses, a contract version someone relies on changes only with a proof that
-> runs in the base's tree, the module checks and stale approvals are enforced, a verifier is not
-> an author, and every verdict names the framework that gave it. Since v0.6.0, a document still
-> holding its template's words is refused, a deprecated module's consumers are named with their
-> removal date, and a contract change runs the checks of both sides — the producer and every
-> declared consumer. The diagnosis says whether anything refuses at all; a record names what
-> reached the default branch outside a pull request, and never refuses it. Since v0.6.2, each
-> version's notes are published, engine and project apart, and an update names every version it
-> crosses. A first real project, public, has run two cycles on it; **M11**, in progress, makes
-> the framework charge what a failure costs, and nothing more ([PDR-0011](docs/pdr/0011-ceremony-follows-consequence.md)).
-> Tracking: [engine roadmap](docs/governance/plans/2026-09-15-engine-v0.1.0.md),
-> [move to English](docs/governance/plans/2026-09-16-english-migration.md),
-> [frame, verify, approve](docs/governance/plans/2026-09-16-v0.3.0-frame-verify-approve.md),
-> [every barrier refuses](docs/governance/plans/2026-09-19-v0.4.0-every-barrier-refuses.md),
-> [a proof that cannot be rewritten](docs/governance/plans/2026-09-20-v0.5.0-a-proof-that-cannot-be-rewritten.md),
-> [the conformance suite](docs/governance/plans/2026-09-20-m12-conformance-suite.md),
-> [what is announced refuses](docs/governance/plans/2026-09-20-v0.6.0-what-is-announced-refuses.md),
-> [ceremony follows consequence](docs/governance/plans/2026-09-23-m11-ceremony-follows-consequence.md),
-> [`docs/governance/workstreams.md`](docs/governance/workstreams.md).
+> **Status: v0.7.2, published** on [PyPI](https://pypi.org/project/napkinstack/).
+> What each version changes, engine and project apart: [`CHANGELOG.md`](CHANGELOG.md).
+> What is open: [`docs/governance/workstreams.md`](docs/governance/workstreams.md).
 
 ## A project's journey
 
@@ -102,8 +84,8 @@ To try it without installing anything, or to install it from this repository ins
 registry — always pinned to a release tag:
 
 ```bash
-uvx --from "git+https://github.com/NapkinStack/engineering-os@v0.6.2" nstack init my-project
-uv tool install "napkinstack @ git+https://github.com/NapkinStack/engineering-os@v0.6.2"
+uvx --from "git+https://github.com/NapkinStack/engineering-os@v0.7.2" nstack init my-project
+uv tool install "napkinstack @ git+https://github.com/NapkinStack/engineering-os@v0.7.2"
 ```
 
 **Two channels, one published artefact.** The registry publishes: the PyPI artefact of a
@@ -124,11 +106,13 @@ Each project then pins its version and changes it through `nstack update`.
 |---|---|
 | `nstack init <folder>` | Creates the project: skeleton, git repository, initial commit, GitHub checklist |
 | `nstack doctor` | Checks the workstation and the GitHub settings, read-only |
+| `nstack settings` | Prints the calls that would bring the GitHub settings to the checklist; changes nothing |
 | `nstack new-module <name> <owner> <criticality>` | Creates a module, with no imposed stack |
+| `nstack new-contract <name>` | Creates a contract and, the first time, the module that holds them all |
 | `nstack check`, `test`, `bootstrap` `[module]`; `nstack run <module>` | Run the commands declared in the module's manifest |
 | `nstack discover <idea-file>` | Starts a discovery for your agent: the idea kept, its document created |
 | `nstack plan` | The discovery, the charter and the cycles: formats, one cycle at a time, closures |
-| `nstack fitness` | Manifests, boundaries between modules, skills, plan, hygiene |
+| `nstack fitness` | Manifests, boundaries between modules, skills, plan, hygiene — each also runs alone: `manifests`, `boundaries`, `skills`, `plan`, `hygiene` |
 | `nstack pr-scope` | One PR = one module, review budget |
 | `nstack modules [--changed-since <base>]` | The project's modules, or those with a file changed since a base |
 | `nstack compat [module] --base <base>` | A contract version consumed or stable changes only with the project's merged comparator |

{napkinstack-0.7.0 → napkinstack-0.7.2}/README.md

@@ -5,27 +5,9 @@ modules, contracts, guardrails in CI. On the Django or Rails model, one command
 the project, which then receives new versions on demand; no application stack is imposed.
 Positioning and vocabulary: [`PRODUCT.md`](PRODUCT.md) §1.
 
-> **Status: v0.6.2, published** ([PyPI](https://pypi.org/project/napkinstack/)): what the
-> framework announces, it refuses — and what it cannot refuse, it says. The boundaries read the
-> contracts a module uses, a contract version someone relies on changes only with a proof that
-> runs in the base's tree, the module checks and stale approvals are enforced, a verifier is not
-> an author, and every verdict names the framework that gave it. Since v0.6.0, a document still
-> holding its template's words is refused, a deprecated module's consumers are named with their
-> removal date, and a contract change runs the checks of both sides — the producer and every
-> declared consumer. The diagnosis says whether anything refuses at all; a record names what
-> reached the default branch outside a pull request, and never refuses it. Since v0.6.2, each
-> version's notes are published, engine and project apart, and an update names every version it
-> crosses. A first real project, public, has run two cycles on it; **M11**, in progress, makes
-> the framework charge what a failure costs, and nothing more ([PDR-0011](docs/pdr/0011-ceremony-follows-consequence.md)).
-> Tracking: [engine roadmap](docs/governance/plans/2026-09-15-engine-v0.1.0.md),
-> [move to English](docs/governance/plans/2026-09-16-english-migration.md),
-> [frame, verify, approve](docs/governance/plans/2026-09-16-v0.3.0-frame-verify-approve.md),
-> [every barrier refuses](docs/governance/plans/2026-09-19-v0.4.0-every-barrier-refuses.md),
-> [a proof that cannot be rewritten](docs/governance/plans/2026-09-20-v0.5.0-a-proof-that-cannot-be-rewritten.md),
-> [the conformance suite](docs/governance/plans/2026-09-20-m12-conformance-suite.md),
-> [what is announced refuses](docs/governance/plans/2026-09-20-v0.6.0-what-is-announced-refuses.md),
-> [ceremony follows consequence](docs/governance/plans/2026-09-23-m11-ceremony-follows-consequence.md),
-> [`docs/governance/workstreams.md`](docs/governance/workstreams.md).
+> **Status: v0.7.2, published** on [PyPI](https://pypi.org/project/napkinstack/).
+> What each version changes, engine and project apart: [`CHANGELOG.md`](CHANGELOG.md).
+> What is open: [`docs/governance/workstreams.md`](docs/governance/workstreams.md).
 
 ## A project's journey
 
@@ -87,8 +69,8 @@ To try it without installing anything, or to install it from this repository ins
 registry — always pinned to a release tag:
 
 ```bash
-uvx --from "git+https://github.com/NapkinStack/engineering-os@v0.6.2" nstack init my-project
-uv tool install "napkinstack @ git+https://github.com/NapkinStack/engineering-os@v0.6.2"
+uvx --from "git+https://github.com/NapkinStack/engineering-os@v0.7.2" nstack init my-project
+uv tool install "napkinstack @ git+https://github.com/NapkinStack/engineering-os@v0.7.2"
 ```
 
 **Two channels, one published artefact.** The registry publishes: the PyPI artefact of a
@@ -109,11 +91,13 @@ Each project then pins its version and changes it through `nstack update`.
 |---|---|
 | `nstack init <folder>` | Creates the project: skeleton, git repository, initial commit, GitHub checklist |
 | `nstack doctor` | Checks the workstation and the GitHub settings, read-only |
+| `nstack settings` | Prints the calls that would bring the GitHub settings to the checklist; changes nothing |
 | `nstack new-module <name> <owner> <criticality>` | Creates a module, with no imposed stack |
+| `nstack new-contract <name>` | Creates a contract and, the first time, the module that holds them all |
 | `nstack check`, `test`, `bootstrap` `[module]`; `nstack run <module>` | Run the commands declared in the module's manifest |
 | `nstack discover <idea-file>` | Starts a discovery for your agent: the idea kept, its document created |
 | `nstack plan` | The discovery, the charter and the cycles: formats, one cycle at a time, closures |
-| `nstack fitness` | Manifests, boundaries between modules, skills, plan, hygiene |
+| `nstack fitness` | Manifests, boundaries between modules, skills, plan, hygiene — each also runs alone: `manifests`, `boundaries`, `skills`, `plan`, `hygiene` |
 | `nstack pr-scope` | One PR = one module, review budget |
 | `nstack modules [--changed-since <base>]` | The project's modules, or those with a file changed since a base |
 | `nstack compat [module] --base <base>` | A contract version consumed or stable changes only with the project's merged comparator |

{napkinstack-0.7.0 → napkinstack-0.7.2}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "napkinstack"
-version = "0.7.0"
+version = "0.7.2"
 description = "Engineering framework for several teams and their agents working in one repository: modules, contracts, guardrails in CI."
 requires-python = ">=3.12"
 license = "MIT"

{napkinstack-0.7.0 → napkinstack-0.7.2}/pyproject.toml.orig

@@ -1,6 +1,6 @@
 [project]
 name = "napkinstack"
-version = "0.7.0"
+version = "0.7.2"
 description = "Engineering framework for several teams and their agents working in one repository: modules, contracts, guardrails in CI."
 requires-python = ">=3.12"
 license = "MIT"