For requirement analysts

Every requirement traced to its source, and kept current both ways.

Your work is finding the rule, writing it so nobody can misread it, and showing later where it came from. KiwiPow turns your documents into citable sections, writes specs from them, and tells you when either side moves.

Lock the founding price From clause to verdict

Sound familiar?

"Where does this rule come from?" has no answer once the story is written.
Every behaviour drawn from a document cites the section and the document version it was read from. An uncited behaviour is visibly the planner's own default, so reviewers know which rules to challenge.
The policy is amended, and nobody notices which requirements it touched.
Re-importing a document keeps the ids of unchanged sections. Every spec citing a section that changed or disappeared is flagged, with the old text beside the new.
The shipped product overtakes the business description, until an auditor or a new hire reads the wrong one.
When a feature is accepted, the planner lists the document sections the spec now contradicts or supersedes, each with the behaviour that overtook it.
Sales, development and test use the same word for different things.
Each domain keeps an information model of its concepts, read by the planner before it writes, and changed only when a feature is accepted.

Your part in the loop

The spec is yours to shape, review and keep true

  1. Bring in the sources

    Word, PDF, Excel, Markdown, JSON and JSON Schema become trees of sections with stable ids. Tables stay tables, each sheet becomes a section.

  2. Shape the spec

    One provable sentence per behaviour, edge cases written out, open questions named. Shape rules are checked as it is written.

  3. Review in rounds

    Comment on any part, strike behaviours and answer questions, then submit the round as one. Revise with the planner or by hand in the same shape.

  4. Handle what the code teaches

    Departures from the spec land in the feedback queue. Accept one and the behaviour changes in a new revision, keeping its id.

  5. Close the circle

    At acceptance, act on the list of document sections the product has overtaken. KiwiPow changes no document itself.

What you get

Search by words and meaning

Full text and meaning combined in one ranking, scoped to the document stores the product selects.

One source, many products

A document store is selected by every product it serves, never copied, so one law serves every product it governs.

No overlap between specs

A behaviour another spec already defines is cited, not repeated, and two drafts claiming the same behaviour are named and resolved.

Comments that stay honest

Each comment is answered with what changed or a reason to disagree. A comment on text that has since changed is shown against the text it was left on.

Need to know, also for the AI

Classified documents are absent to anyone not cleared for them, and the planner reads as the user it works for.

The same sources for every agent

Search, section reads and document maps are offered over MCP, so any AI agent your team uses reads the same documents under the same access rules.

Plan your next feature from your own documents

Import a document, write the ask in your own words, and read the citation on every behaviour the planner proposes.

Lock the founding price What your product owner sees