The most useful knowledge usually comes from experience. People should understand what stays private, what they may choose to share and how information is reviewed before it is used by others.
Identity, Technician and Advisor have different jobs. UnderTorque keeps those boundaries because the safest architecture is often the one people can understand.
Handles the person's account, authentication and canonical organisation relationships. It does not become the product database.
Owns Technician product data, sharing rules, roles and its own session. Private technical knowledge stays inside the Technician boundary.
Owns Advisor knowledge, publication state, local roles and its own session. It does not read the Technician database directly.
Technical learning should not require customer names, addresses, phone numbers or other unnecessary personal details. Advisor is not a CRM, DMS or job-card system.
The public site must follow the actual accepted state of each product. A design decision or staging branch is not the same thing as a production capability.
Blocked or unaccepted Identity, logout or Advisor capability is not marketed as live.
No fake customer counts, savings, certifications, partnerships or testimonials.
Knowledge governance may expose evidence and review health, but it should not fabricate a confidence score.
We can talk through ownership, organisation knowledge, Advisor governance and the product boundaries before sharing feedback.