Work enters
Tickets record incidents, requests, troubleshooting context, and future links to approved knowledge.
Operational knowledge
SOTE Knowledge BaseKnowledge Base
Find approved technical knowledge, understand where it came from, and learn how SOTE turns troubleshooting into reusable institutional knowledge.Approved SOTE procedures, troubleshooting, and operational knowledge.
Ticket / MissionTroubleshoot + EvidenceKnowledge ArticleReview + MergeFuture technician benefits
One knowledge system, different jobs.
The Command Portal is the readable front door. The SOTE Framework repository remains the controlled source for operational Markdown, review history, and accepted changes.
Knowledge changes
Branches and pull requests make proposed documentation changes visible and reviewable before acceptance.
Technicians read
Approved articles become easy to discover and use from the Command Portal.
SOTE stays consistent
Names, vocabulary, zones, characters, mission language, and public-safe rules remain governed by the Codex.
Current operational Knowledge Articles
These articles are currently in validation. Open an article to read the public-safe technician procedure, see its current status, and use it for classroom review and learning.
Loading Knowledge Base…
Reading the current public-safe catalog.
No articles match that search yet.
Contribute
Add to the Knowledge Base
Turn a solved problem into reusable knowledge. Classroom participants can use the guided training session; experienced contributors can go directly to the contribution workflow.
Contribute Knowledge
Already know the workflow? Open the contribution guide and prepare your Knowledge Article for review.
Contribute Knowledge →Training Session
New to GitHub or the SOTE knowledge workflow? Use the CIT-205 training session for onboarding, the assignment, article template, peer review, revision, and version-history practice.
Open Training Session →Knowledge article standard
Operational articles use a consistent structure so technicians know what they are allowed to do, what success looks like, what evidence to preserve, and when to stop.
Purpose & scope
What the article teaches, where it applies, and what authorization is required.
Stop & escalate
Explicit boundaries for safety, destructive actions, uncertainty, and production impact.
Procedure & results
Execution-order steps plus expected and alternate states.
Evidence
Outputs, screenshots, measurements, logs, or notes that make the work defensible.
Troubleshooting
Safe recovery guidance without inviting improvisation beyond authorization.
Version history
Related missions, runbooks, knowledge, and a traceable history of accepted changes.