whyline 0.1.0__tar.gz

whyline-0.1.0/.gitignore

@@ -0,0 +1,12 @@
+__pycache__/
+*.py[cod]
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+.venv/
+phase0/results/
+.whyline/ledger.jsonl
+.whyline/index.db
+dist/
+*.egg-info/
+.DS_Store

whyline-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 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 [yyyy] [name of copyright owner]
+
+   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.

whyline-0.1.0/PKG-INFO

@@ -0,0 +1,171 @@
+Metadata-Version: 2.5
+Name: whyline
+Version: 0.1.0
+Summary: Records why your code exists, and tells the next agent.
+Project-URL: Homepage, https://github.com/anishmoncivarghese/whyline
+Project-URL: Source, https://github.com/anishmoncivarghese/whyline
+Project-URL: Issues, https://github.com/anishmoncivarghese/whyline/issues
+Author: Anish Varghese
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: agents,ai,claude-code,codex,decision-log,git,handoff,provenance
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: MacOS
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Documentation
+Classifier: Topic :: Software Development :: Version Control :: Git
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+
+# whyline
+
+Use Claude Code and Codex on the same project without either one starting blind.
+
+```
+$ whyline explain src/tsconfig/resolve.ts:41
+
+Decision          Treat only canonical in-repo workspace package exports as internal
+Because           node_modules must be readable for resolution but never indexed
+Rejected          classify any resolvable node_modules target as internal
+                  indexes third-party declarations and violates FR-005
+Confidence        High — a recorded decision matches the commit for this line.
+```
+
+Free, Apache-2.0, local-only. No accounts, no telemetry, no paid tier, ever.
+
+## The problem this solves
+
+Claude Code and Codex are good at different things. You might want Claude to plan
+a feature and write the tests, then Codex to review the diff — or the reverse.
+That combination is genuinely useful, and today it is genuinely painful: the
+second agent starts from nothing. It has no idea what the first one concluded,
+what it tried, or what it deliberately ruled out. So you re-explain, or paste, or
+just give up and use one agent for everything.
+
+whyline fixes that with a decision record both agents write to and read from. The
+one that finishes leaves behind what it decided and what it rejected; the one that
+starts picks it up. Neither has to be told twice.
+
+**On the subscriptions you already pay for.** whyline never touches a credential.
+It launches the vendor's own CLI with `exec`, so Claude Code authenticates as
+Claude Code and Codex authenticates as Codex. No API keys, no per-token billing,
+nothing metered on top of what you already have.
+
+And because the record is committed to your repository as plain Markdown, it
+outlives the session. Six months later, `whyline explain` still answers why a line
+of code exists — which is the same mechanism, read at a longer horizon.
+
+## Install
+
+Not yet published. From a clone:
+
+```bash
+uv tool install --from . whyline
+```
+
+Zero production dependencies — standard library only. Python 3.11+, plus `git`.
+
+## Quickstart
+
+```bash
+whyline init                     # scaffold, add instructions, install the hook
+```
+
+Then work normally. Your agents record their own decisions, because `init` adds an
+instruction to `AGENTS.md` asking them to. When you want to switch:
+
+```bash
+whyline run codex "review the caching change"
+```
+
+That composes what Claude decided and hands the terminal to Codex with it attached.
+The reverse works the same way: `whyline run claude "..."`.
+
+The rest of the surface:
+
+```bash
+whyline brief                    # print the handoff context without launching
+whyline explain src/a.py:14      # why does this line exist?
+whyline note "chose X" --because "Y" --rejected "Z: too slow" --file src/a.py
+whyline timeline --file src/a.py
+whyline status
+```
+
+## How it works
+
+Three layers feed one ledger:
+
+1. **git** resolves a line to a commit via `git blame`. Works before whyline has
+   recorded anything.
+2. **A hook** silently records sessions, instructions and file edits. It can never
+   fail your session — every path exits 0.
+3. **Your agent** records the reasoning. `whyline init` adds an `AGENTS.md`
+   instruction asking agents to log decisions and rejected alternatives. This is
+   the only layer that captures *why*.
+
+`.whyline/decisions.md` is committed and readable with whyline uninstalled.
+`.whyline/ledger.jsonl` is gitignored, because it holds your prompt text.
+
+## Does the third layer actually work?
+
+It was the design's one unproven assumption, so it was measured before the
+features depending on it were built. Over three days across two agents on a real
+project, 19 decisions were recorded across 14 commits — Claude Code 150% of its
+non-trivial changes, Codex 130%, against a 60% threshold. Every one carried a
+rationale and a concrete rejected alternative. Codex was never reminded.
+
+Full method and caveats: [`m0/RESULTS.md`](m0/RESULTS.md).
+
+## Honest limitations
+
+- **Switching agents is a relay, not a shared conversation.** Vendor CLIs are
+  separate processes with separate context windows. `brief` hands the next agent a
+  written summary; it cannot continue the previous conversation. Nothing can.
+- **`explain` reports confidence and will say when it does not know.** An empty
+  ledger produces an honest empty answer, not a guess. File-level `explain` never
+  claims high confidence, because without a line there is no blamed commit.
+- **The hook is Claude Code only** in v1. Codex and Gemini both support hooks, so
+  this is a limit of scope, not of design.
+- **Gemini is not supported by `run`** — its free personal tier was withdrawn.
+- **Parallel agents are not coordinated.** No worktree isolation in v1.
+- **`brief` degrades on a fresh clone.** The ledger is gitignored, so a clone has
+  only the committed `decisions.md`, which carries day precision rather than full
+  timestamps. `brief` merges both sources and tells you which is which.
+- **macOS and Linux are verified; Windows is not.** CI passes on `ubuntu-latest`
+  and `macos-latest` across Python 3.11 and 3.13. Windows via WSL is untested — a
+  plausible claim, not an observation.
+
+## Credentials
+
+whyline never reads, stores, forwards or proxies a vendor token. `run` replaces
+itself with the vendor's own CLI via `exec`, which does its own authentication.
+Your subscription works because the official CLI is what talks to the vendor.
+Permission-bypass flags are never added.
+
+## Performance
+
+Measured on an M-series Mac, median of seven runs, against a 200 ms target:
+
+| Command | Total | whyline's own cost |
+|---|---:|---:|
+| `brief` | 41 ms | 23 ms |
+| `timeline` | 46 ms | 27 ms |
+| `status` | 47 ms | 28 ms |
+| `explain` | 79 ms | 60 ms |
+
+Bare Python interpreter startup is 19 ms of every figure above, so the right-hand
+column is what whyline actually costs. `explain` is dearer because it shells out
+to `git blame`.
+
+On a 50,000-event, 6.5 MB ledger `explain` takes ~159 ms against a 1 s target —
+which is why there is no SQLite index.
+
+## Licence
+
+Apache-2.0.

whyline-0.1.0/README.md

@@ -0,0 +1,146 @@
+# whyline
+
+Use Claude Code and Codex on the same project without either one starting blind.
+
+```
+$ whyline explain src/tsconfig/resolve.ts:41
+
+Decision          Treat only canonical in-repo workspace package exports as internal
+Because           node_modules must be readable for resolution but never indexed
+Rejected          classify any resolvable node_modules target as internal
+                  indexes third-party declarations and violates FR-005
+Confidence        High — a recorded decision matches the commit for this line.
+```
+
+Free, Apache-2.0, local-only. No accounts, no telemetry, no paid tier, ever.
+
+## The problem this solves
+
+Claude Code and Codex are good at different things. You might want Claude to plan
+a feature and write the tests, then Codex to review the diff — or the reverse.
+That combination is genuinely useful, and today it is genuinely painful: the
+second agent starts from nothing. It has no idea what the first one concluded,
+what it tried, or what it deliberately ruled out. So you re-explain, or paste, or
+just give up and use one agent for everything.
+
+whyline fixes that with a decision record both agents write to and read from. The
+one that finishes leaves behind what it decided and what it rejected; the one that
+starts picks it up. Neither has to be told twice.
+
+**On the subscriptions you already pay for.** whyline never touches a credential.
+It launches the vendor's own CLI with `exec`, so Claude Code authenticates as
+Claude Code and Codex authenticates as Codex. No API keys, no per-token billing,
+nothing metered on top of what you already have.
+
+And because the record is committed to your repository as plain Markdown, it
+outlives the session. Six months later, `whyline explain` still answers why a line
+of code exists — which is the same mechanism, read at a longer horizon.
+
+## Install
+
+Not yet published. From a clone:
+
+```bash
+uv tool install --from . whyline
+```
+
+Zero production dependencies — standard library only. Python 3.11+, plus `git`.
+
+## Quickstart
+
+```bash
+whyline init                     # scaffold, add instructions, install the hook
+```
+
+Then work normally. Your agents record their own decisions, because `init` adds an
+instruction to `AGENTS.md` asking them to. When you want to switch:
+
+```bash
+whyline run codex "review the caching change"
+```
+
+That composes what Claude decided and hands the terminal to Codex with it attached.
+The reverse works the same way: `whyline run claude "..."`.
+
+The rest of the surface:
+
+```bash
+whyline brief                    # print the handoff context without launching
+whyline explain src/a.py:14      # why does this line exist?
+whyline note "chose X" --because "Y" --rejected "Z: too slow" --file src/a.py
+whyline timeline --file src/a.py
+whyline status
+```
+
+## How it works
+
+Three layers feed one ledger:
+
+1. **git** resolves a line to a commit via `git blame`. Works before whyline has
+   recorded anything.
+2. **A hook** silently records sessions, instructions and file edits. It can never
+   fail your session — every path exits 0.
+3. **Your agent** records the reasoning. `whyline init` adds an `AGENTS.md`
+   instruction asking agents to log decisions and rejected alternatives. This is
+   the only layer that captures *why*.
+
+`.whyline/decisions.md` is committed and readable with whyline uninstalled.
+`.whyline/ledger.jsonl` is gitignored, because it holds your prompt text.
+
+## Does the third layer actually work?
+
+It was the design's one unproven assumption, so it was measured before the
+features depending on it were built. Over three days across two agents on a real
+project, 19 decisions were recorded across 14 commits — Claude Code 150% of its
+non-trivial changes, Codex 130%, against a 60% threshold. Every one carried a
+rationale and a concrete rejected alternative. Codex was never reminded.
+
+Full method and caveats: [`m0/RESULTS.md`](m0/RESULTS.md).
+
+## Honest limitations
+
+- **Switching agents is a relay, not a shared conversation.** Vendor CLIs are
+  separate processes with separate context windows. `brief` hands the next agent a
+  written summary; it cannot continue the previous conversation. Nothing can.
+- **`explain` reports confidence and will say when it does not know.** An empty
+  ledger produces an honest empty answer, not a guess. File-level `explain` never
+  claims high confidence, because without a line there is no blamed commit.
+- **The hook is Claude Code only** in v1. Codex and Gemini both support hooks, so
+  this is a limit of scope, not of design.
+- **Gemini is not supported by `run`** — its free personal tier was withdrawn.
+- **Parallel agents are not coordinated.** No worktree isolation in v1.
+- **`brief` degrades on a fresh clone.** The ledger is gitignored, so a clone has
+  only the committed `decisions.md`, which carries day precision rather than full
+  timestamps. `brief` merges both sources and tells you which is which.
+- **macOS and Linux are verified; Windows is not.** CI passes on `ubuntu-latest`
+  and `macos-latest` across Python 3.11 and 3.13. Windows via WSL is untested — a
+  plausible claim, not an observation.
+
+## Credentials
+
+whyline never reads, stores, forwards or proxies a vendor token. `run` replaces
+itself with the vendor's own CLI via `exec`, which does its own authentication.
+Your subscription works because the official CLI is what talks to the vendor.
+Permission-bypass flags are never added.
+
+## Performance
+
+Measured on an M-series Mac, median of seven runs, against a 200 ms target:
+
+| Command | Total | whyline's own cost |
+|---|---:|---:|
+| `brief` | 41 ms | 23 ms |
+| `timeline` | 46 ms | 27 ms |
+| `status` | 47 ms | 28 ms |
+| `explain` | 79 ms | 60 ms |
+
+Bare Python interpreter startup is 19 ms of every figure above, so the right-hand
+column is what whyline actually costs. `explain` is dearer because it shells out
+to `git blame`.
+
+On a 50,000-event, 6.5 MB ledger `explain` takes ~159 ms against a 1 s target —
+which is why there is no SQLite index.
+
+## Licence
+
+Apache-2.0.

whyline-0.1.0/pyproject.toml

@@ -0,0 +1,67 @@
+[project]
+name = "whyline"
+version = "0.1.0"
+description = "Records why your code exists, and tells the next agent."
+requires-python = ">=3.11"
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+readme = "README.md"
+authors = [{ name = "Anish Varghese" }]
+keywords = [
+    "ai",
+    "agents",
+    "claude-code",
+    "codex",
+    "provenance",
+    "git",
+    "handoff",
+    "decision-log",
+]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Environment :: Console",
+    "Intended Audience :: Developers",
+    "License :: OSI Approved :: Apache Software License",
+    "Operating System :: MacOS",
+    "Operating System :: POSIX :: Linux",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Topic :: Software Development :: Version Control :: Git",
+    "Topic :: Software Development :: Documentation",
+]
+dependencies = []
+
+[project.urls]
+Homepage = "https://github.com/anishmoncivarghese/whyline"
+Source = "https://github.com/anishmoncivarghese/whyline"
+Issues = "https://github.com/anishmoncivarghese/whyline/issues"
+
+[project.scripts]
+whyline = "whyline.cli:entry"
+whyline-hook = "whyline.hook_entry:entry"
+
+[build-system]
+requires = ["hatchling", "editables"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/whyline"]
+
+# Whitelist what ships, rather than relying on exclusions. Caught 2026-08-18
+# while inspecting the artifacts before a first publish: the default sdist swept
+# in `.claude/settings.local.json` — which holds home-directory absolute paths and
+# a log of locally approved shell commands — plus 27 files of internal review
+# workspace under `.superpowers/`. Both are gitignored, so neither was ever in the
+# repository, but hatchling packages from the working tree. A PyPI upload cannot
+# be withdrawn, so this list is deliberately narrow: the package, its tests, and
+# the two files a reader needs.
+[tool.hatch.build.targets.sdist]
+only-include = ["src/whyline", "tests", "README.md", "LICENSE"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+addopts = "-q"
+
+[dependency-groups]
+dev = ["pytest>=8.0"]

whyline-0.1.0/src/whyline/__init__.py

@@ -0,0 +1 @@
+__version__ = "0.1.0"

whyline-0.1.0/src/whyline/__main__.py

@@ -0,0 +1,3 @@
+from whyline.cli import entry
+
+entry()

whyline-0.1.0/src/whyline/agentsmd.py

@@ -0,0 +1,37 @@
+"""The canonical shared instruction that asks agents to record reasoning."""
+
+from __future__ import annotations
+
+from pathlib import Path
+
+BEGIN = "<!-- whyline:begin -->"
+END = "<!-- whyline:end -->"
+
+INSTRUCTION = f"""{BEGIN}
+## Recording decisions
+
+After completing any non-trivial change, record the reasoning:
+
+    whyline note "<one-line decision>" \\
+      --because "<why this choice>" \\
+      --rejected "<option>: <why not>" \\
+      --file <path>
+
+Record only genuine choices a future reader would wonder about. Skip typos,
+formatting and renames. `--rejected` is repeatable. Do not ask permission.
+Store shared project instructions here, but record evolving decision history
+through whyline rather than appending it to AGENTS.md.
+{END}
+"""
+
+
+def install(path: Path) -> str:
+    if path.exists():
+        existing = path.read_text(encoding="utf-8")
+        if BEGIN in existing and END in existing:
+            return "already-present"
+        separator = "" if existing.endswith("\n") else "\n"
+        path.write_text(existing + separator + "\n" + INSTRUCTION, encoding="utf-8")
+        return "installed"
+    path.write_text(INSTRUCTION, encoding="utf-8")
+    return "installed"