Revision history for

what-is-knowns-really

Every commit that touched posts/what-is-knowns-really.en.mdx in the content repo.

Diff

Comparing27333a1 · Update what-is-knowns-really96d09ea · docs(content): explain technical terms
+55
33 unchanged lines
 
Yes.
 
If your task is restructuring folders, renaming things, grouping files, splitting a module, or cleaning up a clear piece of code, an agent can read the repo and do it. It can use `rg`, inspect imports, read related files, and make the change.
+ If your task is restructuring folders, renaming things, grouping files, splitting a module, or cleaning up a clear piece of code, an agent can read the <TermNote id="repository">repo</TermNote> and do it. It can use `rg`, inspect imports, read related files, and make the change.
 
For tasks where the source of truth already lives inside the codebase, I do not think Knowns needs to get in the way.
 
Not every piece of work needs a formal task. Not every refactor needs a doc. Not every bug fix needs memory.
+ Not every piece of work needs a formal task. Not every refactor needs a doc. Not every bug fix needs <TermNote id="memory">memory</TermNote>.
 
If one short prompt plus a few related files is enough, keep it lightweight.
 
11 unchanged lines
- why the folder structure was designed this way
- which convention is current and which one is legacy
- past decisions: no service layer, no Zustand, this API must remain backward compatible
- acceptance criteria that do not live in the code
+ - <TermNote id="acceptance-criteria">acceptance criteria</TermNote> that do not live in the code
- tasks that stretch across multiple sessions
- multiple people or multiple agents working together
- lessons that should be saved after the task is done
16 unchanged lines
 
That is not how it works.
 
Knowns is not magic. It does not think for you. It is a local-first CLI tool that helps you organize tasks, docs, memory, templates, and workflows in a way an agent can retrieve.
+ Knowns is not magic. It does not think for you. It is a <TermNote explanation="Local-first means the tool centers files and data you keep on your own machine, instead of making a remote service the only source of truth.">local-first</TermNote> CLI tool that helps you organize tasks, docs, memory, templates, and workflows in a way an agent can retrieve.
 
In other words, Knowns is an implementation of a way of thinking.
 
143 unchanged lines
knowns task create "Add OAuth login for users"
```
 
That task can have a description, acceptance criteria, notes, and links to docs or specs.
+ That task can have a description, acceptance criteria, notes, and links to docs or <TermNote id="spec">specs</TermNote>.
 
<Image
src="https://res.cloudinary.com/dkxhoyenc/image/upload/v1780565830/task-in-knowns_x0yeig.png"
185 unchanged lines

Revisions

3 revisions — click any two to compare
FromTo
  1. docs(content): explain technical terms

  2. Update what-is-knowns-really

  3. Create what-is-knowns-really