Glossary
What became of a feedback: the change, and the commit that made it.
To move a feedback to feedback/archive/ once it has an answer.
The component catalog in knowledge/catalog/.
One TYPO3 core worktree below .checkouts/, this repository's
own, created by bin/cli checkouts:update.
A targeted scenario in scenarios/contracts/, which names
one task shape.
What a change rested on, and what would show it wrong: one file
in decisions/.
One report about this server, written by a session working somewhere else. Countable here: one report, one file, one subject.
feedback/, where feedback arrives and waits.
Written by typo3_feedback_record, read by bin/cli feedback.
An open scenario in scenarios/forward/ that names no
subsystem, skill or expected finding.
One statement in knowledge/hints/, reached by
bin/cli hints:probe.
Two senses, told apart by the preposition. A statement holds on a version or for a scope: it is true there. A test holds a rule and the rule is held by it: the test fails when the rule breaks.
The TYPO3 a caller works in. The server reads its own facts from it rather than bundles them.
To work out what should become of one open feedback, on evidence.
Everything below knowledge/: what the tools answer from.
The verb a feedback arrives by, and one of the six tool verbs.
What must be true from now on, and what holds it there: one
file in requirements/.
What a tool hands back: the text and the same answer as data.
src/Result/ holds what several tools build one from — the shared
schemas, the renderers, the unanswered case.
One recorded execution of a forward review, in scenarios/runs/.
One prompt and what has to come out of it, in scenarios/.
One canonical task workflow under skills/, installed into
somebody else's project.
This repository as the Composer root package, where a session can record feedback.
One entry in the order of the work.
One typo3_<subject>_<verb> this server offers its callers: the
MCP primitive of that name, one class in src/Tool/, listed in
TYPO3\DevCompanion\Tools.
One of lookup, guide, list, scope, describe,
record: what tells a caller the shape of the answer.
How a recorded run came out: covered, partial, gap.
- answer
-
What became of a feedback: the change, and the commit that made it.
- archive
-
To move a feedback to
feedback/archive/once it has an answer. - catalog
-
The component catalog in
knowledge/catalog/. - checkout
-
One TYPO3 core worktree below
.checkouts/, this repository's own, created bybin/cli checkouts:update. - contract case
-
A targeted scenario in
scenarios/contracts/, which names one task shape. - decision
-
What a change rested on, and what would show it wrong: one file in
decisions/. - a feedback
-
One report about this server, written by a session working somewhere else. Countable here: one report, one file, one subject.
- the feedback channel
-
feedback/, where feedback arrives and waits. Written bytypo3_feedback_record, read bybin/cli feedback. - forward review
-
An open scenario in
scenarios/forward/that names no subsystem, skill or expected finding. - hint
-
One statement in
knowledge/hints/, reached bybin/cli hints:probe. - hold
-
Two senses, told apart by the preposition. A statement holds on a version or for a scope: it is true there. A test holds a rule and the rule is held by it: the test fails when the rule breaks.
- installation
-
The TYPO3 a caller works in. The server reads its own facts from it rather than bundles them.
- judge
-
To work out what should become of one open feedback, on evidence.
- knowledge
-
Everything below
knowledge/: what the tools answer from. - record
-
The verb a feedback arrives by, and one of the six tool verbs.
- requirement
-
What must be true from now on, and what holds it there: one file in
requirements/. - result
-
What a tool hands back: the text and the same answer as data.
src/Result/holds what several tools build one from — the shared schemas, the renderers, the unanswered case. - run
-
One recorded execution of a forward review, in
scenarios/runs/. - scenario
-
One prompt and what has to come out of it, in
scenarios/. - skill
-
One canonical task workflow under
skills/, installed into somebody else's project. - standalone checkout
-
This repository as the Composer root package, where a session can record feedback.
- todo
-
One entry in the order of the work.
- tool
-
One
typo3_<subject>_<verb>this server offers its callers: the MCP primitive of that name, one class insrc/Tool/, listed inTYPO3\DevCompanion\Tools. - tool verb
-
One of
lookup,guide,list,scope,describe,record: what tells a caller the shape of the answer. - verdict
-
How a recorded run came out:
covered,partial,gap.