A product description, a project decision, and a research procedure can all look like similar pieces of text. Their reasons for changing differ: a price changes, a project changes direction, or a method repeatedly omits a check.
Putting everything in “long-term memory” makes each correction a search for scattered copies. One role remembers an old price while a skill contains another version of a writing rule. More content can make maintenance less certain.
A practical distinction is where the next change should be made. Teloa gives facts, decisions, and methods their own places for maintenance, then combines them for execution. Users should be able to understand which work a change affects without searching all the text behind every employee.
Three problems lead to three places for correction
| Content | Maintenance location | Effect to check when changing it |
|---|---|---|
| Knowledge | Factual source and text version | Which material later work should receive |
| Memory | Original decision or experience entry | Which person, project, or role it still applies to |
| Skill | Independent method definition and version | Which roles and tasks explicitly adopt that version |
The three categories are not mutually exclusive in meaning. Experience may refer to a fact, and a skill may require checking a particular document. The distinction is about maintenance: where a change belongs, which work it affects, and who can judge whether it still applies.
Working together in one quotation explanation
Suppose you are preparing a quotation explanation for a client evaluating a pilot. Service material supplies prices, support scope, and validity periods. The confirmed project decision “the first version covers only the pilot scope” constrains this explanation. A quotation skill asks for applicable conditions, unresolved items, and evidence. Knowledge supplies what can be stated, memory carries forward a choice already made in this relationship, and the skill organizes both into a usable explanation.
This is more than summarizing three inputs in sequence. The employee uses the skill's checks to examine the material and judge whether a condition affects this pilot. An annual-plan discount, for example, does not establish the price for this pilot. Its conditions need explaining, or the unconfirmed price needs to remain open. The combination aims to retain business judgment in the first draft, beyond producing a comprehensive summary.
Current role execution prepares the materials and skills actually adopted. Related project work also prepares background and applicable memory according to its settings. The three remain independently maintainable and meet in a particular run. Changing pilot scope does not require rewriting a general quotation method. Changing a price does not require copying the same figure into every employee's memory.
Update facts at their source
Suppose the price of a service has changed. The appropriate correction is to update the source document so that later work can find the new version. The original report retains the older version it used, making the difference explainable.
Adding “use the new price from now on” only to memory creates competing facts in the knowledge library and memory. A new employee using the document may still make the mistake. When the price changes again, it is unclear what else needs updating.
Knowledge therefore needs a source, content, version, and permitted scope of use. The presence of a document does not mean it was used in this turn. Diagnosing an error also requires checking what was actually sent and cited. Correcting the authoritative source and checking how it was used are both necessary.
One choice should not become a rule for all work
A customer may have wanted implementation effects first because they were evaluating deployment at the time. Their priorities may differ when discussing renewal. Experience needs context and sources so that its continuing relevance can be judged.
Memory reduces repeated explanation; it should leave room for people and businesses to change. A changed decision can be corrected or withdrawn. History still explains the earlier choice, while later inputs check what is currently valid.
Employee experience, project decisions, and personal habits belong to different contexts. They may work together within a task, but calling them all memory does not make them shared across businesses by default.
Stable methods need their own revisions
If several reports miss a check of reporting periods, the problem may be in the procedure rather than an individual fact. Recording “check periods and applicable conditions before comparing” as a research skill makes the method reusable in suitable roles and tasks.
A skill preserves a method, not all the material and permissions needed for this task. An employee using a quotation-analysis procedure still needs the quotations, available tools, and appropriate authorization. A method mentioning email does not mean a sending tool is connected.
Independent revision makes the effect of an improvement clearer. Updating a general source-checking skill can serve several roles, while an employee’s particular responsibilities remain in that role. There is no need to copy the whole team and maintain every document again to change one step.
Saving a new skill version is also separate from changing what existing employees use. A method can be prepared and compared before entering actual work. Earlier runs still show which version they used.
Check whether the correction actually reached the next task
A correction needs to be followed through actual input. Updating material while still selecting an old version differs from supplying a new version that is then misinterpreted. The first calls for fixing the usage path; the second calls for reviewing content and method.
The classification is not meant to give users more terminology to remember. It should reduce maintenance: prices return to their factual source, decisions change within their scope, and general procedures improve independently. The product handles composition while users can understand the impact.
When the price changes again, update the factual source. When the project changes direction, revise its decision. When a missing step becomes apparent, improve the method. Clear maintenance responsibilities give corrections a specific place to act.