Scope and responsibility
This policy covers original guides and trust pages published under the KODE Ń VIBE Editorial Team byline. Interactive roadmaps, questionnaires and prototype community features may also be reviewed against these principles, but their interfaces can contain tool-generated or demonstration content with different update cycles.
The organisational byline does not invent a named expert. It identifies the team function responsible for the page. Readers should judge guidance by its reasoning, sources, review date and stated limitations.
Our source standard
When a statement can be checked, we prefer the source closest to the fact:
- Kenyan regulators, public institutions and official legal text for local rules and public processes.
- Standards bodies and maintainers' documentation for technical behaviour.
- Original research or datasets with a stated method, date and licence.
- Reputable secondary explanations when primary material needs context.
We link sources where they help readers verify or act. A source does not transfer automatically to a different version, county, employer or personal situation, so pages should describe the relevant boundary.
Writing for Kenyan context
Local examples should clarify the work, not flatten Kenya into a single experience. We avoid assuming a reader's county, income, device, education, language, network access or professional connections. When access constraints matter, we describe alternatives without presenting them as universally available.
Official processes and product integrations can change. Guidance involving personal data points to the Office of the Data Protection Commissioner; security references can point to National KE-CIRT/CC; and vendor-specific integrations should lead to the vendor's current documentation.
Claims we avoid
- Guaranteed jobs, salaries, clients, admissions, certifications or investment outcomes.
- A universal period in which someone will become “job-ready.”
- Unverified rankings of schools, bootcamps, employers, tools or communities.
- Fees, application dates, programme availability or product rules without a current primary source.
- Legal, medical, financial or security advice presented as personalised professional guidance.
- Partnership, endorsement or affiliation inferred only from a link or logo.
Publication and review process
Define the reader's decision
A page should answer a real question with a clear scope, not merely target a search phrase.
Check primary material
Factual claims are compared with current official documentation where practical.
Review safety and assumptions
We check for hidden data collection, misleading outcomes, inaccessible instructions and unsupported local generalisations.
Date the review
Every editorial page shows when it was last reviewed. The date means the page was assessed then; it does not guarantee that every external page remains unchanged.
Corrections and material updates
Report factual errors, broken primary-source links, accessibility barriers or misleading wording by emailing kodenvibe@gmail.com. Include the page URL, the exact passage, why it is wrong and a primary source when available.
Include only the information needed to explain the correction. Never send passwords, identity documents, account details or confidential employer information.
Material corrections should update the visible review date. Minor typography or layout fixes may not change it.
External links and commercial context
External links are provided for verification or further learning. They do not by themselves mean KODE Ń VIBE endorses the provider, programme, price or claim. Readers should check terms, costs, privacy practices and eligibility with the responsible organisation.
If a future page has a material sponsorship, affiliate relationship or supplied content, that relationship should be disclosed beside the relevant content—not hidden in this policy.