---
name: company-wiki-page
description: Creates or refreshes a navigable company wiki page from authoritative policies, procedures, and operational references, with named owners, version dates, links, and explicit knowledge gaps. Use for internal documentation, SOP pages, knowledge-base maintenance, or policy publishing drafts.
license: Apache-2.0
metadata:
  adlass.categories: "admin-office/knowledge-wiki"
  adlass.industries: ""
  adlass.tags: "wiki,knowledge-base,procedure,ownership,documentation"
  adlass.adaptation: "reference-doc"
  adlass.source: "original"
  adlass.version: "1"
---

# Company wiki page

## Purpose

Make one operational topic usable by a colleague who did not attend its creation. The page states what the topic is, who owns it, how the procedure works, where exceptions go, and when the content must be reviewed.

## Scope

Rewrite or create one internal wiki page from the named authoritative sources. Preserve required terminology, link targets, owner information, version dates, procedures, prerequisites, and escalation routes.

**Excluded:** changing the live wiki, creating undocumented policy, deciding ownership, or treating an unverified draft as authoritative.

## Data basis

- Authoritative policy, SOP, runbook, or product reference documents.
- Existing wiki page and page metadata table with `owner`, `review_date`, `version`, and `status`.
- Glossary, link register, escalation matrix, and page taxonomy.
- Change log or release notes showing what changed since the previous page.

## Result

A publish-ready wiki draft plus a source map and maintenance register.

## Quality criteria

- The page has a title, audience, scope, owner, version date, review date, and source list.
- Each procedural action has an actor, prerequisite, input, expected result, and exception path.
- Policy statements cite the source document and section; links are checked against the link register.
- Conflicting instructions appear as an open decision with both citations.
- The page contains no orphan heading, placeholder, or unexplained acronym.

## Instructions

Prefer the latest approved source when versions conflict, but record the superseded wording in the change log when it affects behavior. Keep normative requirements distinct from tips and examples. Use the page taxonomy and glossary exactly. Never infer an owner or review date; write `unassigned` or `not specified` with a citation. Put unresolved contradictions in the maintenance register rather than silently selecting one.

## Adapt before use

- Add the wiki style guide and authoritative-source hierarchy.
- Define metadata fields, page taxonomy, owners, and review cadence.
- Provide link-validation and glossary conventions.
- Specify how deprecated procedures are labeled.