constant-docs 0.7.0__tar.gz → 0.9.1__tar.gz

{constant_docs-0.7.0 → constant_docs-0.9.1}/PKG-INFO

@@ -1,9 +1,9 @@
 Metadata-Version: 2.4
 Name: constant-docs
-Version: 0.7.0
+Version: 0.9.1
 Summary: Self-maintaining documentation for agentic codebases
 Keywords: documentation,docs,staleness,drift,ci,codegen,agents,llm
-Author: Ashborn Systems
+Author: Daemon Agent
 License-Expression: Apache-2.0
 License-File: LICENSE
 Classifier: Development Status :: 3 - Alpha
@@ -19,12 +19,12 @@ Classifier: Operating System :: OS Independent
 Classifier: Typing :: Typed
 Requires-Dist: pyyaml>=6.0.3
 Requires-Python: >=3.11
-Project-URL: Homepage, https://github.com/ashborn-systems/constant-docs
-Project-URL: Repository, https://github.com/ashborn-systems/constant-docs
-Project-URL: Documentation, https://github.com/ashborn-systems/constant-docs/blob/main/README.md
-Project-URL: Changelog, https://github.com/ashborn-systems/constant-docs/blob/main/docs/CHANGELOG.md
-Project-URL: Issues, https://github.com/ashborn-systems/constant-docs/issues
-Project-URL: Specification, https://github.com/ashborn-systems/constant-docs/blob/main/docs/SPEC.md
+Project-URL: Homepage, https://github.com/daemon-systems/constant-docs
+Project-URL: Repository, https://github.com/daemon-systems/constant-docs
+Project-URL: Documentation, https://github.com/daemon-systems/constant-docs/blob/main/README.md
+Project-URL: Changelog, https://github.com/daemon-systems/constant-docs/blob/main/docs/CHANGELOG.md
+Project-URL: Issues, https://github.com/daemon-systems/constant-docs/issues
+Project-URL: Specification, https://github.com/daemon-systems/constant-docs/blob/main/docs/SPEC.md
 Description-Content-Type: text/markdown
 
 <!-- constant-docs
@@ -51,20 +51,29 @@ constant_docs:
   - src/constant_docs/api.py
   - src/constant_docs/cli.py
   - src/constant_docs/kinds.py
-  source_hash: sha256:99017f4b3440779659af6e13a51d12da0e37146fd449a934a42751f6f6f8d50b
+  source_hash: sha256:aeb0c87c1ea90b23e657543f1eb6c39707733d7def1a6f05096158295d76cec8
   hash_method: sha256-over-sorted-path-and-content
   hash_covers: source_files
-  timestamp: '2026-09-05T13:18:40Z'
-  generator: constant-docs/0.7.0
-  generator_spec: https://github.com/ashborn-systems/constant-docs/blob/main/SPEC.md
+  timestamp: '2026-09-19T13:07:50Z'
+  generator: constant-docs/0.9.1
+  generator_spec: https://github.com/daemon-systems/constant-docs/blob/main/SPEC.md
 -->
 
 
+
+
+
+
+
+
+
+
 # constant-docs
 
 Documentation that fails the build when it drifts.
 
-A Python command-line tool for codebases written with a coding agent. Each
+A Python command-line tool and coding-agent plugin for maintaining source
+documents. Each
 document records a hash of the source files it describes, and `constant-docs
 verify` exits 1 the moment the two disagree. The check is a hash comparison, so
 it needs no model client and no network. Your agent writes the documents. The
@@ -94,8 +103,9 @@ Your coding agent writes every word, because it already holds the source and a
 model connection. constant-docs names the documents that moved and takes the
 new text back.
 
-That one command is also the whole CI integration. It exits 1 on drift, so a
-change that alters behaviour and leaves its document behind does not merge:
+That one command is also the whole continuous-integration check. It exits 1 on
+drift, so a change that alters behaviour and leaves its document behind does
+not merge:
 
 ```yaml
 - run: constant-docs verify
@@ -167,13 +177,15 @@ clean report on no evidence. `plan --json` considers every module whatever the
 marks say. `verify` hashes everything and exits 1 on drift. Keep `verify` as
 the gate.
 
-Claude Code gets a plugin. Install it and two hooks run those commands for you:
-`PostToolUse` runs `mark`, `Stop` runs `settle --hook`. Edit a file, stop the
-turn, and its document is up to date. Any harness that can run a command on
-write and at turn end does the same job.
+Codex and Claude Code can load the plugin. Its two document hooks run these
+commands:
+`PostToolUse` runs `mark` after each edit, and `Stop` runs `settle --hook` when
+the turn ends. The agent reads the returned plan and updates the affected documents before
+verification. Any
+harness that can run a command on write and at turn end does the same job.
 
-Regeneration happens at quiescence, never mid-edit, so the generator and the
-coding loop never write the same file at once. The dirty set lives in
+Regeneration happens at the end of a turn, never mid-edit, so the generator and
+the coding loop never write the same file at once. The dirty set lives in
 `.constant-docs/dirty.json`, which is gitignored, so a crashed session is
 picked up on the next run.
 
@@ -181,9 +193,9 @@ The [harness guide](guides/harness-integration.md) walks through each route.
 
 ## Kinds
 
-A document is not always a module explainer. Its kind decides which sections it
-must carry, which prompt its generator is handed, and whether a regeneration
-replaces the body or appends to it.
+Every document has a kind. The kind decides which sections its body must carry,
+which prompt its generator is handed, and whether a regeneration replaces the
+body or appends an entry.
 
 | Kind | For | Mode |
 |---|---|---|
@@ -191,9 +203,10 @@ replaces the body or appends to it.
 | `spec` | What a subsystem promises, and why | replace |
 | `log` | A changelog or build log | **append** |
 | `architecture` | The module map, with a diagram | replace |
-| `errors` | Every message the tool can emit | replace |
+| `errors` | Every message the covered code can raise | replace |
 | `config-reference` | Every configuration key | replace |
 | `cli-reference` | Every command and flag | replace |
+| `manual-page` | One user task, written for the person doing it | replace |
 
 ```yaml
 modules:
@@ -212,8 +225,25 @@ An append never rewrites or reorders what is already there. Pass a whole body
 to a log, or a single entry to a module document, and the tool refuses it. A
 configuration that has never heard of kinds behaves exactly as it did.
 
-One house style governs every generated document. It lives in a single file
-that all seven built-in prompts receive, so the rules cannot drift apart.
+One shared writing register governs documents written from built-in prompts. It
+lives in a single file that all eight built-in prompts receive, and is checked
+against the canonical technical-writing skill. The smaller shared core can also
+be consumed by other agents through a pinned import.
+The [writing-register guide](guides/writing-register.md) describes the exports.
+
+## User manuals
+
+A user manual is an ordered collection of small task pages. Each page is a
+normal tracked document, so a product change makes only the affected pages
+stale. Constant-Docs assembles the navigation without a model call.
+
+Manuals declare input and output token ceilings. A page already above its input
+ceiling appears under `blocked` and is never handed to the supplied generation
+workflow. Split that page by user task, narrow its source, or change the budget
+deliberately.
+
+This repository uses the feature itself. Start with the [Constant-Docs user
+manual](docs/user-manual/index.md).
 
 ## Finding what is undocumented
 
@@ -223,17 +253,18 @@ constant-docs coverage      # source no module covers, by directory
 constant-docs completeness  # kinds of document the contents warrant
 ```
 
-`verify` can only check what has been declared, so a repository could otherwise
-drift to a large fraction undocumented while every check passed. `coverage`
-does one thing: a set difference. Declare the directories that should carry no
-document in the configuration, with a reason each. An exclusion nobody
-justified is one nobody decided.
+`verify` can only check what has been declared, so a repository can drift a
+long way undocumented while every check passes. `coverage` does one thing: a
+set difference. It reports the files no declared glob matches and no exclusion
+names. Declare the directories that should carry no document in the
+configuration, with a reason each. An exclusion nobody justified is one nobody
+decided.
 
 Coverage answers whether a file has a document. It cannot answer whether the
-set of documents is complete: a document that was never written cannot drift,
-and a module document covers its files, so a repository with a document per
-module and no specification passes everything. `completeness` proposes the
-kinds your contents warrant, each with the fact behind it:
+set of documents is complete. A document that was never written cannot drift,
+and a repository with a document per module and no specification passes every
+coverage check. `completeness` proposes the kinds your contents warrant, each
+with the fact behind it:
 
 ```
 Warranted and not written (2):
@@ -247,11 +278,11 @@ Warranted and not written (2):
 It proposes from evidence in the repository, such as a console script or an
 exception hierarchy. The existence of a kind is not itself evidence. A library
 with no command line is not offered a CLI reference, because a document nobody
-needs still has to be kept true and still refuses a commit when it drifts.
+needs still has to be kept true and still fails the build when it drifts.
 Nothing warrants a changelog: every repository could keep one, so the signal
 fires everywhere and says nothing.
 
-Write the document, or decline the kind under `unwarranted:` with a reason and
+Write the document, or decline the kind under `unwarranted:` with a reason, and
 it stops being proposed.
 
 `verify --coverage` and `verify --completeness` fold the two into the gate,
@@ -261,13 +292,14 @@ document, and `prune` deletes it.
 ## Files it will not touch
 
 Pointing the tool at a `docs/` folder the repository already has is safe. Every
-document this tool writes carries a block naming the tool, and, when you
-declare a `project` id, the project that wrote it. A markdown file without that
-block belongs to somebody else, and three commands act on the difference:
+document this tool writes carries a block naming the tool and, when you declare
+a `project` id, the project that wrote it. A markdown file without that block
+belongs to somebody else, and three commands act on the difference:
 
 - `apply` refuses to write over one. It names the file and changes no byte
 - `prune` refuses to delete one, and names every file it left alone
-- `verify` lists them under a heading of their own, and they fail nothing
+- `verify` lists them under a heading of their own, and none of them fails the
+  check
 
 Take one over when you want it maintained:
 
@@ -288,7 +320,7 @@ rewrite it. Every body your agent generates still carries those headings, and
 `apply` checks before it writes a byte.
 
 A glob that matches no file gets the same restraint. `verify` names the module
-and exits 1, `apply` refuses to record a digest over nothing, and the document
+and exits 1, `apply` refuses to record a hash over nothing, and the document
 stays where it is. A mistyped glob costs you a failing check and nothing else.
 
 ## Documents outside the repository
@@ -309,12 +341,14 @@ real directory on this machine: where to open the file.
 
 The variable must resolve when the configuration loads. Unset, empty, relative,
 or naming a directory that is not there, each refuses the configuration and
-says which. A store landing inside `.ssh`, `Secret/`, a cache or any other
-directory on the deny list is refused too. The tool declines to read those
-directories, so it declines to write documents into them. Plain `${NAME}` is
-the whole syntax. A default value would let a machine without the vault write
-documents into the repository and report success. The Stop hook blocks on the
-same failure, so a missing variable cannot switch the gate off quietly.
+says which. A store landing inside `.ssh`, `Secret/`, a cache, or any other
+directory on the deny list is refused too: the tool declines to read those
+directories, so it declines to write documents into them.
+
+Plain `${NAME}` is the whole syntax. A default value would let a machine
+without the vault write documents into the repository and report success. The
+Stop hook blocks on the same failure, so a missing variable cannot switch the
+gate off quietly.
 
 Deletion changes as well. A repository's documents ride the branch, and `git
 checkout` brings one back. A store stands still while the checkout moves, so
@@ -334,12 +368,14 @@ auto:
   budget: 5
 ```
 
-The tool still calls no model. constant-docs splits your command with `shlex`
-and runs it directly, so an agent CLI, a script and a Makefile target all work.
-No credential goes in it. The command's success is checked: `auto` re-runs
-`verify` afterwards. It exits 0 when everything is clean, 1 when something is
-still stale, and 2 when the command could not run or exited non-zero. Three
-outcomes, because a scheduler that confuses the last two retries the wrong one.
+constant-docs itself calls no model. It splits your command with `shlex` and
+runs it directly, so an agent CLI, a script, and a Makefile target all work. No
+credential goes in it. The command's success is checked: `auto` re-runs
+`verify` afterwards.
+
+It exits 0 when everything is clean, 1 when something is still stale, and 2
+when the command could not run or exited non-zero. Three outcomes, because a
+scheduler that confuses the last two retries the wrong one.
 
 ## Three things it checks that a hash cannot
 
@@ -354,9 +390,10 @@ document, with a date.
 in those modules' files by name, so it goes stale when their boundary moves.
 
 **An error catalogue agrees with the source, both ways.** Every message the
-code raises appears in the catalogue, and every entry still exists in the code.
-Neither needs parsing beyond a string scan, so it costs nothing, and it is the
-one document here the tool can actually guarantee. The rest are only fresh.
+code raises appears in the catalogue, and every entry listed is still raised in
+the code. The check needs no parsing beyond a string scan, so it costs nothing,
+and it is the one document here the tool can guarantee. The rest are only
+fresh.
 
 ## What a document looks like
 
@@ -381,8 +418,8 @@ constant_docs:
   hash_method: sha256-over-sorted-path-and-content
   hash_covers: source_files
   timestamp: '2026-08-19T09:14:00Z'
-  generator: constant-docs/0.7.0
-  generator_spec: https://github.com/ashborn-systems/constant-docs/blob/main/SPEC.md
+  generator: constant-docs/0.8.0
+  generator_spec: https://github.com/daemon-systems/constant-docs/blob/main/SPEC.md
 ---
 ## Purpose
 
@@ -404,7 +441,7 @@ report records that it happened.
 
 The frontmatter stands alone. An agent that has never run this tool can see
 what the document describes, where its source lives, and how to recompute the
-digest. `project` answers the question asked before every overwrite and every
+hash. `project` answers the question asked before every overwrite and every
 deletion: whose document is this. The tool keeps everything it owns under one
 `constant_docs` key, an Open Knowledge Format producer extension. `type`,
 `title`, `tags` and the two dates stay yours, and unknown keys survive a write.
@@ -424,11 +461,11 @@ prune()  # deletes orphans; under a store, lists them
 
 ## What it does not do
 
-A module names a glob, and the tool digests the bytes of the files that glob
-matches. Nothing in that step knows a language, which is what makes yours work:
-no model client, no network call, no AST, no import graph. The cost is that any
-byte moves the hash. Fixing a typo in a comment reports the module stale, and
-your agent rewrites a document the edit never touched.
+A module names a glob, and the tool hashes the bytes of the files that glob
+matches. Nothing in that step knows a language, which is what makes it work on
+yours: no model client, no network call, no syntax tree, no import graph. The
+cost is that any byte moves the hash. Fixing a typo in a comment reports the
+module stale, and your agent rewrites a document the edit never touched.
 
 It watches files and nothing else. A document quoting a queue depth or a
 production URL stays fresh for ever, because nobody edited anything. Hash what

{constant_docs-0.7.0 → constant_docs-0.9.1}/README.md

@@ -22,20 +22,29 @@ constant_docs:
   - src/constant_docs/api.py
   - src/constant_docs/cli.py
   - src/constant_docs/kinds.py
-  source_hash: sha256:99017f4b3440779659af6e13a51d12da0e37146fd449a934a42751f6f6f8d50b
+  source_hash: sha256:aeb0c87c1ea90b23e657543f1eb6c39707733d7def1a6f05096158295d76cec8
   hash_method: sha256-over-sorted-path-and-content
   hash_covers: source_files
-  timestamp: '2026-09-05T13:18:40Z'
-  generator: constant-docs/0.7.0
-  generator_spec: https://github.com/ashborn-systems/constant-docs/blob/main/SPEC.md
+  timestamp: '2026-09-19T13:07:50Z'
+  generator: constant-docs/0.9.1
+  generator_spec: https://github.com/daemon-systems/constant-docs/blob/main/SPEC.md
 -->
 
 
+
+
+
+
+
+
+
+
 # constant-docs
 
 Documentation that fails the build when it drifts.
 
-A Python command-line tool for codebases written with a coding agent. Each
+A Python command-line tool and coding-agent plugin for maintaining source
+documents. Each
 document records a hash of the source files it describes, and `constant-docs
 verify` exits 1 the moment the two disagree. The check is a hash comparison, so
 it needs no model client and no network. Your agent writes the documents. The
@@ -65,8 +74,9 @@ Your coding agent writes every word, because it already holds the source and a
 model connection. constant-docs names the documents that moved and takes the
 new text back.
 
-That one command is also the whole CI integration. It exits 1 on drift, so a
-change that alters behaviour and leaves its document behind does not merge:
+That one command is also the whole continuous-integration check. It exits 1 on
+drift, so a change that alters behaviour and leaves its document behind does
+not merge:
 
 ```yaml
 - run: constant-docs verify
@@ -138,13 +148,15 @@ clean report on no evidence. `plan --json` considers every module whatever the
 marks say. `verify` hashes everything and exits 1 on drift. Keep `verify` as
 the gate.
 
-Claude Code gets a plugin. Install it and two hooks run those commands for you:
-`PostToolUse` runs `mark`, `Stop` runs `settle --hook`. Edit a file, stop the
-turn, and its document is up to date. Any harness that can run a command on
-write and at turn end does the same job.
+Codex and Claude Code can load the plugin. Its two document hooks run these
+commands:
+`PostToolUse` runs `mark` after each edit, and `Stop` runs `settle --hook` when
+the turn ends. The agent reads the returned plan and updates the affected documents before
+verification. Any
+harness that can run a command on write and at turn end does the same job.
 
-Regeneration happens at quiescence, never mid-edit, so the generator and the
-coding loop never write the same file at once. The dirty set lives in
+Regeneration happens at the end of a turn, never mid-edit, so the generator and
+the coding loop never write the same file at once. The dirty set lives in
 `.constant-docs/dirty.json`, which is gitignored, so a crashed session is
 picked up on the next run.
 
@@ -152,9 +164,9 @@ The [harness guide](guides/harness-integration.md) walks through each route.
 
 ## Kinds
 
-A document is not always a module explainer. Its kind decides which sections it
-must carry, which prompt its generator is handed, and whether a regeneration
-replaces the body or appends to it.
+Every document has a kind. The kind decides which sections its body must carry,
+which prompt its generator is handed, and whether a regeneration replaces the
+body or appends an entry.
 
 | Kind | For | Mode |
 |---|---|---|
@@ -162,9 +174,10 @@ replaces the body or appends to it.
 | `spec` | What a subsystem promises, and why | replace |
 | `log` | A changelog or build log | **append** |
 | `architecture` | The module map, with a diagram | replace |
-| `errors` | Every message the tool can emit | replace |
+| `errors` | Every message the covered code can raise | replace |
 | `config-reference` | Every configuration key | replace |
 | `cli-reference` | Every command and flag | replace |
+| `manual-page` | One user task, written for the person doing it | replace |
 
 ```yaml
 modules:
@@ -183,8 +196,25 @@ An append never rewrites or reorders what is already there. Pass a whole body
 to a log, or a single entry to a module document, and the tool refuses it. A
 configuration that has never heard of kinds behaves exactly as it did.
 
-One house style governs every generated document. It lives in a single file
-that all seven built-in prompts receive, so the rules cannot drift apart.
+One shared writing register governs documents written from built-in prompts. It
+lives in a single file that all eight built-in prompts receive, and is checked
+against the canonical technical-writing skill. The smaller shared core can also
+be consumed by other agents through a pinned import.
+The [writing-register guide](guides/writing-register.md) describes the exports.
+
+## User manuals
+
+A user manual is an ordered collection of small task pages. Each page is a
+normal tracked document, so a product change makes only the affected pages
+stale. Constant-Docs assembles the navigation without a model call.
+
+Manuals declare input and output token ceilings. A page already above its input
+ceiling appears under `blocked` and is never handed to the supplied generation
+workflow. Split that page by user task, narrow its source, or change the budget
+deliberately.
+
+This repository uses the feature itself. Start with the [Constant-Docs user
+manual](docs/user-manual/index.md).
 
 ## Finding what is undocumented
 
@@ -194,17 +224,18 @@ constant-docs coverage      # source no module covers, by directory
 constant-docs completeness  # kinds of document the contents warrant
 ```
 
-`verify` can only check what has been declared, so a repository could otherwise
-drift to a large fraction undocumented while every check passed. `coverage`
-does one thing: a set difference. Declare the directories that should carry no
-document in the configuration, with a reason each. An exclusion nobody
-justified is one nobody decided.
+`verify` can only check what has been declared, so a repository can drift a
+long way undocumented while every check passes. `coverage` does one thing: a
+set difference. It reports the files no declared glob matches and no exclusion
+names. Declare the directories that should carry no document in the
+configuration, with a reason each. An exclusion nobody justified is one nobody
+decided.
 
 Coverage answers whether a file has a document. It cannot answer whether the
-set of documents is complete: a document that was never written cannot drift,
-and a module document covers its files, so a repository with a document per
-module and no specification passes everything. `completeness` proposes the
-kinds your contents warrant, each with the fact behind it:
+set of documents is complete. A document that was never written cannot drift,
+and a repository with a document per module and no specification passes every
+coverage check. `completeness` proposes the kinds your contents warrant, each
+with the fact behind it:
 
 ```
 Warranted and not written (2):
@@ -218,11 +249,11 @@ Warranted and not written (2):
 It proposes from evidence in the repository, such as a console script or an
 exception hierarchy. The existence of a kind is not itself evidence. A library
 with no command line is not offered a CLI reference, because a document nobody
-needs still has to be kept true and still refuses a commit when it drifts.
+needs still has to be kept true and still fails the build when it drifts.
 Nothing warrants a changelog: every repository could keep one, so the signal
 fires everywhere and says nothing.
 
-Write the document, or decline the kind under `unwarranted:` with a reason and
+Write the document, or decline the kind under `unwarranted:` with a reason, and
 it stops being proposed.
 
 `verify --coverage` and `verify --completeness` fold the two into the gate,
@@ -232,13 +263,14 @@ document, and `prune` deletes it.
 ## Files it will not touch
 
 Pointing the tool at a `docs/` folder the repository already has is safe. Every
-document this tool writes carries a block naming the tool, and, when you
-declare a `project` id, the project that wrote it. A markdown file without that
-block belongs to somebody else, and three commands act on the difference:
+document this tool writes carries a block naming the tool and, when you declare
+a `project` id, the project that wrote it. A markdown file without that block
+belongs to somebody else, and three commands act on the difference:
 
 - `apply` refuses to write over one. It names the file and changes no byte
 - `prune` refuses to delete one, and names every file it left alone
-- `verify` lists them under a heading of their own, and they fail nothing
+- `verify` lists them under a heading of their own, and none of them fails the
+  check
 
 Take one over when you want it maintained:
 
@@ -259,7 +291,7 @@ rewrite it. Every body your agent generates still carries those headings, and
 `apply` checks before it writes a byte.
 
 A glob that matches no file gets the same restraint. `verify` names the module
-and exits 1, `apply` refuses to record a digest over nothing, and the document
+and exits 1, `apply` refuses to record a hash over nothing, and the document
 stays where it is. A mistyped glob costs you a failing check and nothing else.
 
 ## Documents outside the repository
@@ -280,12 +312,14 @@ real directory on this machine: where to open the file.
 
 The variable must resolve when the configuration loads. Unset, empty, relative,
 or naming a directory that is not there, each refuses the configuration and
-says which. A store landing inside `.ssh`, `Secret/`, a cache or any other
-directory on the deny list is refused too. The tool declines to read those
-directories, so it declines to write documents into them. Plain `${NAME}` is
-the whole syntax. A default value would let a machine without the vault write
-documents into the repository and report success. The Stop hook blocks on the
-same failure, so a missing variable cannot switch the gate off quietly.
+says which. A store landing inside `.ssh`, `Secret/`, a cache, or any other
+directory on the deny list is refused too: the tool declines to read those
+directories, so it declines to write documents into them.
+
+Plain `${NAME}` is the whole syntax. A default value would let a machine
+without the vault write documents into the repository and report success. The
+Stop hook blocks on the same failure, so a missing variable cannot switch the
+gate off quietly.
 
 Deletion changes as well. A repository's documents ride the branch, and `git
 checkout` brings one back. A store stands still while the checkout moves, so
@@ -305,12 +339,14 @@ auto:
   budget: 5
 ```
 
-The tool still calls no model. constant-docs splits your command with `shlex`
-and runs it directly, so an agent CLI, a script and a Makefile target all work.
-No credential goes in it. The command's success is checked: `auto` re-runs
-`verify` afterwards. It exits 0 when everything is clean, 1 when something is
-still stale, and 2 when the command could not run or exited non-zero. Three
-outcomes, because a scheduler that confuses the last two retries the wrong one.
+constant-docs itself calls no model. It splits your command with `shlex` and
+runs it directly, so an agent CLI, a script, and a Makefile target all work. No
+credential goes in it. The command's success is checked: `auto` re-runs
+`verify` afterwards.
+
+It exits 0 when everything is clean, 1 when something is still stale, and 2
+when the command could not run or exited non-zero. Three outcomes, because a
+scheduler that confuses the last two retries the wrong one.
 
 ## Three things it checks that a hash cannot
 
@@ -325,9 +361,10 @@ document, with a date.
 in those modules' files by name, so it goes stale when their boundary moves.
 
 **An error catalogue agrees with the source, both ways.** Every message the
-code raises appears in the catalogue, and every entry still exists in the code.
-Neither needs parsing beyond a string scan, so it costs nothing, and it is the
-one document here the tool can actually guarantee. The rest are only fresh.
+code raises appears in the catalogue, and every entry listed is still raised in
+the code. The check needs no parsing beyond a string scan, so it costs nothing,
+and it is the one document here the tool can guarantee. The rest are only
+fresh.
 
 ## What a document looks like
 
@@ -352,8 +389,8 @@ constant_docs:
   hash_method: sha256-over-sorted-path-and-content
   hash_covers: source_files
   timestamp: '2026-08-19T09:14:00Z'
-  generator: constant-docs/0.7.0
-  generator_spec: https://github.com/ashborn-systems/constant-docs/blob/main/SPEC.md
+  generator: constant-docs/0.8.0
+  generator_spec: https://github.com/daemon-systems/constant-docs/blob/main/SPEC.md
 ---
 ## Purpose
 
@@ -375,7 +412,7 @@ report records that it happened.
 
 The frontmatter stands alone. An agent that has never run this tool can see
 what the document describes, where its source lives, and how to recompute the
-digest. `project` answers the question asked before every overwrite and every
+hash. `project` answers the question asked before every overwrite and every
 deletion: whose document is this. The tool keeps everything it owns under one
 `constant_docs` key, an Open Knowledge Format producer extension. `type`,
 `title`, `tags` and the two dates stay yours, and unknown keys survive a write.
@@ -395,11 +432,11 @@ prune()  # deletes orphans; under a store, lists them
 
 ## What it does not do
 
-A module names a glob, and the tool digests the bytes of the files that glob
-matches. Nothing in that step knows a language, which is what makes yours work:
-no model client, no network call, no AST, no import graph. The cost is that any
-byte moves the hash. Fixing a typo in a comment reports the module stale, and
-your agent rewrites a document the edit never touched.
+A module names a glob, and the tool hashes the bytes of the files that glob
+matches. Nothing in that step knows a language, which is what makes it work on
+yours: no model client, no network call, no syntax tree, no import graph. The
+cost is that any byte moves the hash. Fixing a typo in a comment reports the
+module stale, and your agent rewrites a document the edit never touched.
 
 It watches files and nothing else. A document quoting a queue depth or a
 production URL stays fresh for ever, because nobody edited anything. Hash what

{constant_docs-0.7.0 → constant_docs-0.9.1}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "constant-docs"
-version = "0.7.0"
+version = "0.9.1"
 description = "Self-maintaining documentation for agentic codebases"
 readme = "README.md"
 requires-python = ">=3.11"
@@ -32,15 +32,15 @@ classifiers = [
 dependencies = ["pyyaml>=6.0.3"]
 
 [[project.authors]]
-name = "Ashborn Systems"
+name = "Daemon Agent"
 
 [project.urls]
-Homepage = "https://github.com/ashborn-systems/constant-docs"
-Repository = "https://github.com/ashborn-systems/constant-docs"
-Documentation = "https://github.com/ashborn-systems/constant-docs/blob/main/README.md"
-Changelog = "https://github.com/ashborn-systems/constant-docs/blob/main/docs/CHANGELOG.md"
-Issues = "https://github.com/ashborn-systems/constant-docs/issues"
-Specification = "https://github.com/ashborn-systems/constant-docs/blob/main/docs/SPEC.md"
+Homepage = "https://github.com/daemon-systems/constant-docs"
+Repository = "https://github.com/daemon-systems/constant-docs"
+Documentation = "https://github.com/daemon-systems/constant-docs/blob/main/README.md"
+Changelog = "https://github.com/daemon-systems/constant-docs/blob/main/docs/CHANGELOG.md"
+Issues = "https://github.com/daemon-systems/constant-docs/issues"
+Specification = "https://github.com/daemon-systems/constant-docs/blob/main/docs/SPEC.md"
 
 [project.scripts]
 constant-docs = "constant_docs.cli:main"