keep-the-why
The why layer of repo-native project memory: the reasoning behind a codebase as Markdown in the repo, versioned by Git, for coding agents and humans, so nothing rejected is proposed twice. No database, no daemon, no account.
Runssource: GitHubhomepageJavaScriptMITcommit 8268a33c00ba
JavaScript, MIT licensed. The project labels itself: agent skills, ai agents, architecture decision records, coding agents, context engineering, developer tools, documentation and git.
keep-the-why runs. An Argusic agent installed it in 2 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
keep-the-why-lint 0.20.0.0 and keep-the-why-dashboard 0.7.3 are installed and functional. The linter validates this project's context/ (0 errors, 0 warnings, schema 0.20.0). The dashboard serves its UI at localhost:8765 (HTTP 200), exports static pages, and both packages' test suites pass completely (116+61+65 = 242 tests).
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
- Install time
- 2 minutes
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- ktw-lint . returned 0 errors, 0 warnings; ktw-dashboard --json produced valid state with 130 entries; ktw-dashboard server responded HTTP 200; pytest lint/tests/ returned 116 passed; pytest dashboard/tests/ returned 61 passed; pytest tools/evals/tests/ returned 65 passed. Export generated index.html, state.json, badge-entries.svg.
- Model tokens used
- 232,871
- Exact commit tested
- 8268a33c00ba
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
=== Dashboard version === ktw-dashboard 0.7.3 === Lint version === ktw-lint 0.20.0.0 === Build time calc === Started around 2026-10-29 11:00:17 Good. The total time spent is about 2 minutes. Let me calculate more precisely and compile the fina… Here is the final summary: tokens used 232,871 Good. The total time spent is about 2 minutes. Let me calculate more precisely and compile the fina… Here is the final summary:
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 2 minutes.
- Nothing broke on the way: zero errors between clone and running.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 128 agent-skills projects Argusic has installed and timed, keep-the-why was the 48th fastest to reach a running state, and 96 of 128 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 2 minutes after the clone.
- Following its own README: the documented path worked with nothing to fix.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
agent-skillsai-agentsarchitecture-decision-recordscoding-agentscontext-engineeringdeveloper-toolsdocumentationgitknowledge-managementllm-agentsproject-memoryrepo-local-memoryrepo-native
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/keep-the-why)Questions
- Does keep-the-why run?
- Yes. keep-the-why runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test keep-the-why?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 8268a33c00ba. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test keep-the-why?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does keep-the-why take to install?
- 2 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does keep-the-why need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing keep-the-why?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does keep-the-why compare with the alternatives?
- Of the 128 agent-skills projects Argusic has installed and timed, keep-the-why was the 48th fastest to reach a running state, and 96 of 128 reached one at all.
- Where is the evidence for keep-the-why?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.