formwork-kit 0.2.0__tar.gz → 0.2.1__tar.gz

{formwork_kit-0.2.0 → formwork_kit-0.2.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: formwork-kit
-Version: 0.2.0
+Version: 0.2.1
 Summary: You bring the idea. It brings the whole team. Rules your coding agent cannot ignore.
 Project-URL: Homepage, https://github.com/makariim/formwork
 Project-URL: Source, https://github.com/makariim/formwork
@@ -182,7 +182,19 @@ pipx install formwork-kit
 ```
 
 pipx puts the `formwork` command on your path and keeps it in its own
-environment, away from your project's packages. Then, in your project:
+environment, away from your project's packages.
+
+> [!IMPORTANT]
+> **If you used plain `pip` instead, `formwork` will say `command not found`.**
+> It installed fine. pip put the command in a folder your shell does not
+> search. You do not have to fix anything: put `python3 -m formwork_cli` in
+> front of every command below and they all work.
+>
+> ```
+> python3 -m formwork_cli init
+> ```
+
+Then, in your project:
 
 ```
 cd /your/project

{formwork_kit-0.2.0 → formwork_kit-0.2.1}/README.md

@@ -153,7 +153,19 @@ pipx install formwork-kit
 ```
 
 pipx puts the `formwork` command on your path and keeps it in its own
-environment, away from your project's packages. Then, in your project:
+environment, away from your project's packages.
+
+> [!IMPORTANT]
+> **If you used plain `pip` instead, `formwork` will say `command not found`.**
+> It installed fine. pip put the command in a folder your shell does not
+> search. You do not have to fix anything: put `python3 -m formwork_cli` in
+> front of every command below and they all work.
+>
+> ```
+> python3 -m formwork_cli init
+> ```
+
+Then, in your project:
 
 ```
 cd /your/project

{formwork_kit-0.2.0 → formwork_kit-0.2.1}/formwork/first-run.md

@@ -10,8 +10,10 @@ about a second. Your share is step 4, which is real work on your own project,
 and nobody can time that for you.
 
 > [!TIP]
-> **`command not found: formwork`?** Every command here has a second form that
-> needs nothing installed. [`troubleshooting.md`](troubleshooting.md) has both.
+> **`command not found: formwork`?** It installed fine, and pip put it
+> somewhere your shell does not search. Put `python3 -m formwork_cli` in front
+> of every command here and they all work.
+> [`troubleshooting.md`](troubleshooting.md) has the other two ways.
 
 ---
 

{formwork_kit-0.2.0 → formwork_kit-0.2.1}/formwork/limits.md

@@ -131,19 +131,29 @@ wrong assumption shows up as a refusal rather than as silent permission.
 
 ---
 
-## Four things nobody has run
-
-Written, tested where a program can test them, used by nobody.
+## What has been run, and what has not
 
 | | |
 |---|---|
-| **The director role** | the upper layer that holds the plan. It has never held a real project |
-| **A split brief** | `lead` cutting one brief into pieces and joining the reports back. Never done once |
-| **The folder route** | briefs and reports as numbered files, rather than pasted into a chat |
-| **`formwork setup`** | its tests pass. No stranger has answered the questions |
-
-**NOT ESTABLISHED** for all four. They are shapes that work when a check is
-pointed at them, which is a much smaller claim than working.
+| **`formwork setup`** | run on a new project. Its questions have been answered once, by the author |
+| **The director role** | **run twice**, on a different project. It held the plan, wrote the briefs and the decision records, and kept the standing brief true. It also offered to do the building four times, which its own page names as the way this role fails, and the human caught it rather than the kit |
+| **The folder route** | used in that same session. The number came from the check, the brief was saved under it |
+| **A split brief** | `lead` cutting one brief into pieces and joining the reports back. **Never done once** |
+
+**One run by the person who wrote the method is not a trial.** What it
+establishes is narrow: the shape holds together for one turn, on a project that
+is not this one. It says nothing about the second week, about somebody else's
+judgement of the briefs, or about whether any of it survives a person who did
+not design it.
+
+**A split brief remains NOT ESTABLISHED**, and so does everything about more
+than one person.
+
+**And one thing the second run established that nobody wanted:** with the
+planning layer inside the repository, the separation between planning and
+building is a sentence in a file and nothing else. It failed within a day. The
+role now carries the words to say instead, and whether that is enough is itself
+NOT ESTABLISHED. See entry 12 of `docs/dogfood.md`, in the source repository.
 
 ---
 

{formwork_kit-0.2.0 → formwork_kit-0.2.1}/formwork/roles/method/director.md

@@ -189,6 +189,24 @@ splits it, hands the pieces out, and returns one report. Do not split it
 yourself. Deciding what the pieces are is that role's job and it has rules for
 it.
 
+### The sentence that ends your turn
+
+When the brief is written, you are finished. Say this, or something very like
+it, and stop:
+
+> The brief is ready. Open a working session and give it brief 0007.
+
+**It is here because the alternative is always easier to reach for.** You will
+have just spent the turn working out what needs doing, so you know how to do
+it, and "I will start on it now" is the obvious next sentence. It is also the
+end of the two layers, because the plan and the work are then in one window
+again.
+
+Running inside the repository, nothing stops you. The tools are there. The
+guards cannot tell a director from a worker, and they never will be able to.
+**This sentence is the whole of what holds the line**, which is why it is
+written out rather than left as a rule about what not to do.
+
 **When the report comes back, read the whole thing.** The three lines that
 matter are the ones a summary would drop first: what was done without being
 asked, what was skipped, and what the brief got wrong. If the human hands you a
@@ -217,5 +235,10 @@ big one feels responsible. It is the fastest way to make somebody abandon this.
 briefing it. Now the plan and the work are in one window again, which is what
 the two layers exist to prevent.
 
+**This one has happened**, on the first real use of this role, inside a
+repository where the tools were to hand. It offered to build four times in one
+conversation and the human caught it, not the kit. That is what the sentence
+above is for.
+
 **It keeps going when it should stop.** A decision was needed, it took the small
 version of it, and nobody was asked.

{formwork_kit-0.2.0 → formwork_kit-0.2.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "formwork-kit"
-version = "0.2.0"
+version = "0.2.1"
 description = "You bring the idea. It brings the whole team. Rules your coding agent cannot ignore."
 readme = "README.md"
 requires-python = ">=3.8"