Knowledge Structure · Process Knowledge & Content Knowledge

Process Knowledge & Content Knowledge

Combine knowledge of how work gets done with the information that grounds decisions and answers.

Content knowledge describes facts and reference information. Process knowledge describes checks, decisions and actions. Keeping their roles distinct helps AI applications use current information within an agreed operating procedure.

Why It Matters

Connect what to know with how to proceed

A correct fact is not always enough to complete a business interaction. A team may also need to verify identity, check conditions or escalate an exception. If a procedure is retrieved only in fragments, its prerequisites can be missed. This distinction is a practical knowledge-design approach, not a claim that all RAG systems ignore procedures.

How It Works

The approach

Technica AI structures procedures and supporting content separately, then links them where needed. Research on cognitive architectures for language agents also distinguishes forms of memory used for facts and action. The business design remains specific to each application.

Process Knowledge is knowledge of procedures, with a sequence of checks, decisions, branches and handoffs. Content Knowledge is knowledge of content, such as FAQs, manuals, pricing and regulations. Each step in a procedure references the content knowledge it needs. Procedures do not need to be rewritten when content is updated.PROCESS KNOWLEDGEHow to proceed (steps, decisions, branches)CONTENT KNOWLEDGEWhat things are (the supporting content)01  Verify identity02  Check contract details03  Branch on conditions04  Process or hand offFAQManuals, product materialsPrice lists, regulationsreferencesLink procedures to maintained content
How Process Knowledge and Content Knowledge relate (conceptual diagram)
  1. Structure the procedure: Define steps, checks, branches, exceptions and handoff conditions.
  2. Organize reference content: Keep FAQs, manuals and policies retrievable with source information.
  3. Link the two: Connect steps to the content they require, reducing duplicated facts within procedures.
  4. Capture experience: Use interviews and permitted records to identify undocumented practices for assessment.
Benefits

Business value

  • More consistent handling

    Explicit checks and branches help teams evaluate whether required steps are covered.

  • Maintain content separately

    Update linked reference information without duplicating every change across procedures; rule changes may still require procedure updates.

  • Support authorized action

    Use the procedure to guide AI actions and handoffs within configured integrations and permissions.

Considerations

Application considerations

  • Agree the operating scope, exception handling and action permissions before deployment. Test the procedure against representative cases.
  • For AIKNOW Answer, proposed knowledge updates undergo review and testing before release. Update controls vary across products and deployments; they should match the impact of the change.
Related Products

Related products

  • AIKNOW Answer

    Combines process and content knowledge for configured customer-service automation.

  • AISECI

    A knowledge-creation framework with a target architecture for capturing and sharing experience; capability scope is agreed for each project.

References

References

  • Sumers, T. R. et al. (2024). Cognitive Architectures for Language Agents. Transactions on Machine Learning Research. arXiv:2309.02427. https://arxiv.org/abs/2309.02427
Structuring Knowledge Process Knowledge & Content Knowledge
All technologies
Let’s Talk

Explore the right approach
for your business.

Tell us about your information sources, intended use and deployment requirements.
We can assess suitable technologies and a practical evaluation scope.