For AI agents: the complete documentation index is available at https://docs.flezise.com/llms.txt, the full documentation bundle is available at https://docs.flezise.com/llms-full.txt, and this page is available as Markdown at https://docs.flezise.com/knowledge-base/as-is-wiki.md.
Docs

As-is wiki

The as-is wiki is a set of baseline artifacts generated from a connected repository. Each page reverse-engineers one aspect of the existing codebase so the project starts with documented context rather than a blank slate. Once approved, as-is pages join the knowledge base alongside authored artifacts.

What gets generated

A full baseline run produces the following artifact sequence, in order.

  1. Product brief: a high-level summary of what the system does.
  2. PRD: a product requirements document derived from the extracted feature set.
  3. Epics: one epic per extracted feature, parented to the PRD.
  4. High-level design: an architectural overview of the system.
  5. Interface spec: the public interfaces and integration points found in the code.
  6. Coding standards: the conventions the existing codebase follows.
  7. Operations plan: deployment and operational context.
  8. Detailed designs: one per module, parented to the high-level design, generated in topological order.
  9. Tech-debt work items: findings raised directly as work items.

Draft and review

Every generated artifact starts as a draft and moves to in_review automatically when generation passes validation. A person then reviews and approves it through the standard artifact approval flow. The run is gated on an approved work item; no consent, no run.

Regenerating a single page

When an as-is artifact is stale, a staleness badge appears on its row in the artifact list. A Regenerate button on the same row re-queues that artifact for regeneration.

Regenerating all stale pages at once

When one or more as-is artifacts are stale, a Regenerate stale (N) button appears above the artifact tree. Pressing it re-queues only the flagged pages; up-to-date artifacts are skipped.

Staleness

An as-is artifact becomes stale when source files it was generated from have changed since the last scan. The artifact row shows a "STALE since <date>" banner with a count of the changed source files. Regenerating the artifact clears its staleness.

Next steps