Knowledge that writes, reviews, and publishes itself.

She stands up the structure and workflow that make knowledge run itself — the bases, the taxonomy that organises them, publishing and review flows, quality checks, and the feedback loop that keeps content fresh. The articles themselves stay in your authors' hands; she can bulk-import legacy content as drafts for your team to review and publish.

No. Anything she stages or imports lands as a draft, and publishing is a deliberate act your knowledge managers own. Where you've asked for review, articles route through approval before they ever go live — Phyllis wires the workflow; your people pull the trigger.

Yes. Phyllis reads your instance to see what publishing and review capability already exists and reuses it, rather than bolting on a duplicate. The outcome is articles that move cleanly from draft to review to published with the right people notified along the way.

Correct. Phyllis discovers, proposes a plan, and only builds on your explicit approval, staging every change in a reviewable package. Bulk-imported articles are held as drafts — never published — and clean-up fixes run only when you say so.

Every claim is cited to what she actually found in your instance — the bases that publish versus the ones sitting dormant, empty categories, duplicates, and stale content. She reads your live setup rather than assuming out-of-box defaults, because on migrated instances knowledge drifts and ownership goes stale.